Recently Added Articles

• In order to get past the initial screen, you have to supply a namespace and a path to the DNN website. However, once you’ve done that, change your project reference to the DotNetNuke Library project. Then, add the CodeEndeavors module project as a reference from the DNN website.
• If your DNN Website references the CodeEndeavors module project and the module project is referencing the website, you can run into problems later that won’t let you compile your projects.
• I have consistently had trouble with the namespaces that are written throughout the project.
• First, go to your project properties tab and make sure that your project is named exactly how you want it. (Namespace and Assembly).
• Do a find and replace throughout the entire project to make sure that your namespaces are correct. I have found that in the .ascx and .vb files that ‘YourCompany’ keeps sneaking in to the names.
• Check the namespaces in the .js files also. the very first line Type.RegisterNamespace(‘namespace’) –> usually only has the Root Namespace which may not be what you’re using. Then, the class objects that are created within the javascript file will need to be changed as well.
• For example, if you are using MyCompany.Modules.Ajax as your namespace. Then, on the ViewMyPage.ascx.js file you should have Type.RegisterNamespace(‘MyCompany.Modules.Ajax’) and the next line should read: MyCompany.Module.Ajax.ViewMyPage = function(). You’ll need to make sure that you’ve made all the changes in the js file. There are probably about 5 or 6 in each javascript file.
• Another thing I’ve noticed is that the .dll file is not directly copied into the website directory. This is taken are of if you have made a project reference to the module from your DNN website however.
• And finally, in the .dnn manifest file, take out the reference to the assembly because it is not created in the zip file when the build happens. If you don’t remove this, then you’ll receive an error when you try to install the module. So, I just do it first and make sure the install goes as planned.
• If you get installed and the first screen you see says that the type cant be loaded, then check your bin directory and make sure a copy of the dll is there. If not, copy it over (and make the project reference! :-) and then reload the page.

Most of these errors could be corrected by making some modifications to the templates, but so far its just been easier to make these corrections as I go.

Hope that helps some of you out there!