|
|
|
|
|
|
|
|
Wednesday, September 08, 2010
|
|
|
|
|
|
|
|
|
|
|
|
|
Creating new DotNetNuke HTTP Alias Records Setting up DotNetNuke to handle serving requests for Portal Alias records is a breeze. You can use these records to direct your site to handle requests for multiple domain names to one website with ...
Find this article and more in the category
Read This Article . . .
Upgrading to DotNetNuke Cambrian 5.0 from DotNeNuke 4.x If you're looking to try out the new DNN Cambrian package, you can upgrade previous DotNetNuke installations with the following steps. Remember, as of right now, the DNN 5.0 Cambrian package availabl...
Find this article and more in the category
Read This Article . . .
DotNetNuke 5 Cambrian Extropy Skin Features and Limitations The new DotNetNuke Extropy skin looks very cool from a distance...leaps and bounds above the old default blue skin. But, it's got some limitations you should know about upfront.
Find this article and more in the category
Read This Article . . .
Using DNN to take Advantage of GoDaddy Domain Names Let's face it, GoDaddy is cheap. Pay for the hosting services and the domain names are $1.99, not a bad deal. And even without hosting services, you can pick up domain names for as low as $6.99. Put ...
Find this article and more in the category
Read This Article . . .
Setting Up Multiple Websites You can create multiple distinct, (mainly) independent websites with one instance of a DNN installation on your web account. In lamens terms, this means that you can purchase ONE web hosting accoun...
Find this article and more in the category
Read This Article . . .
How to Utilize AjaxToolKit with DotNetNuke Portals Integrating the AjaxToolkit into DotNetNuke modules is super easy. But, can be frustrating if you're not sure how. Find out how to Ajax enable your modules in less than 5 minutes now!
The ...
Find this article and more in the Module Development category
Read This Article . . .
More Ways to Install DotNetNuke Modules with the URL Method While DotNetNuke has a built in mechanism for installing modules, there is another method you can use as well. This is a great alternative to use especially when you are trying to install larger mod...
Find this article and more in the category
Read This Article . . .
Installing Active Directory Authentication Package on DotNetNuke DotNetNuke has abstracted the authentication providers away from the core giving site owners the ability to add new authentication systems. You can see in the picture below that by default, the DotNe...
Find this article and more in the category
Read This Article . . .
Installing DotNetNuke on the root of GoDaddy - 8 Simple Steps If you have are having a hard time getting DotNetNuke installed on the root of your hosting account, read this article to find out how. This article was originally written for a the specific purpose ...
Find this article and more in the Hosting Provider category
Read This Article . . .
SERIES: Anatomy of a DNN Web.Config File-connectionStrings The section holds all the necessary information for database communication from your website. At minimum, there will be at least one connection string for any DotNetNuke website...
Find this article and more in the category
Read This Article . . .
|
|
|
|
|
|
|
|
|
Article List
|
Quick Check for Troubleshooting the CodeEndeavor Ajax Templates
|
| 3/12/2009 1:06:55 AM - By Briana Tarrance |
Category: | | Comments 0
|
| |
|
I haven’t just installed the the template and created a module out of the box yet. *EDIT: I have noticed that the troubles I've had compiling straight out of the box have all resulted from trying to use a namespace with more than one "." (ie. Company.Modules.MyAjaxModule). I also noticed that this happens when I use blank namespace on the project properties page. ** However, I have come across a few things that I know to check and fix and I’m up and running in no time at all. If you are having some troubles with the initial compilation and install of the CodeEndeavor templates, maybe this can help. . .
- 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! |
| |
Related Articles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|