About DNN recently, there are some tips worth recording (tips), SQL garbled characters, and source code modification of the articles module.

Recently, there are some tips worth recording (tips) about DNN. In order to take care of foreign friends who use DNN, I still post some English keywords, hoping not to arouse some people's dislike.

You only need to save the garbled characters in the DNN module as UTF-8. The problem that the Chinese characters in the SQL script I previously asked become question marks is confirmed by m2land as a bug in DNN. It will convert the SQL script and then execute it, double-byte Chinese characters are naturally question marks. We hope that the next DNN version will be corrected. According to land, he has reported the bug to the DNN team.

In addition, I will summarize some issues in the articles module. (Download from http://www.efficionconsulting.com /)

I am using version 3.2.6. The first thing to solve is that comments in comments will become question marks. This is a small case after I have experienced the above garbled events. Replace the varchar of the SQL table creation script with nvarchar (varchar replace nvarchar ). Unicode encoding is used to solve the problem.

Similarly, in the Article Title List, there will be "read more... "and" More articles "should be modified in the localized resource file (resx file in App_LocalResources. But the author may have forgotten it. This function is not provided. We can add it by ourselves, or modify text in the ascx file. We recommend that you add it by yourself and then use the resource file. If you change the text directly, you need to save it as UTF-8 encoding in. Otherwise it will be garbled.

Then it took me more than a day. Here is a description from a foreigner, which is the same as what I encountered.
I posted it directly to avoid repetitive work. You should compile your English.

I need your help if you coshould give me.

I have a problem when I use your article Articles 3.2.6-Source & PA.
I'm using dotnetnuke 4x version and Visual Studio 2005.
When I install your PA I have no problem and everything is OK.
When I try to install the sources, the process I use to do that is:

1. Install Articles PA in dotnetnuke import module.
2. Copying all files ascx. vb and vb project files to directory partition topmodules/Articles overwriting the existent

Ones.
3. Inside my solution, I open the existent project (vbproj file) that I have copied to topics modules/Articles.
4. I include and point to correct dll's in my articles project and the project build with no errors.
5. Remove the dll bin reference to exceptionconsultingarticles on my website and add a project articles

Reference.

The problem is:

I got errors when I build all the solution, and the compiler saies me that controls (variables) are already

Declared. If I delete the control declarations in articles project, logically, the project won't build no matter

What.

Is this mode the right way to install sources in my dotnetnuke project?

I have also tried to copy the source files directly to topics modules/Articles (bellow dotnetnuke website), but I got the following error: 'namespace/ArticlesListBase. ascx. vb is not defined '. seems that, the compiler doesn' t let me to create instance of this class because couldn't found it in the namespace: |.

Is there a problem with my visual studio?

Is the version of dotnetnuke?

I 'd be very gglad if you cocould help me in this situation

Best regards,

Ricardo Moura.

====
I cut the articles module of the source code version that can be used normally to the dll in the bin directory to another location. When compiled with vs2005, the system prompts "Error 4 cocould not load type 'efficionconsulting. Articles. setts'. C: \ dnn \ topics topmodules \ Articles \ Settings. ascx 1
.

I did not get an answer when I searched for information, asked people, or even sent emails to the author. However, we found that many people have encountered similar problems.

Later, I put all the vb source code in the articles directory under the app_code directory, and changed some of the class names automatically prompted by vs2005 that have been updated in the new version to vs recommended.
For example, to change "Services. Search. SearchItemInfoCollection" to "DotNetNuke. Services. Search. SearchItemInfoCollection ",
System. Configuration. ConfigurationManager. Modify ettings to the latest version. There seems to be another one. I don't remember. Anyway, you just need to watch the vs prompt.

OK, all records. That's all.
In fact, at the beginning, we looked at the vs error prompt. It seems that the namespaces and classes are not defined or identified. The problem solved later proves this feeling. Therefore, in the future, we must carefully read the vs prompt. Consider whether to solve the problem by yourself or search for it. This saves a lot of time.