|
|
|
|
|
|
|
|
Saturday, July 31, 2010
|
|
|
|
|
|
|
|
|
|
|
|
|
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 . . .
Everything You Never Wanted to Know About the Config File This is the "pre-" first installment in a series that will cover the parts of the web.config file to give you an idea of how to manipulate and customize your DotNetNuke portal. The web.config fi...
Find this article and more in the category
Read This Article . . .
Simple Intro to the DNN UserInfo Class New DNN developers often wonder how to expose information about logged in users to a custom DotNetNuke module. So, I threw together a very simple example to show how easy it is to begin using the bu...
Find this article and more in the DotNetNuke category
Read This Article . . .
Generate a Module Data Access Layer With CodeSmith With the introduction of some of the newer DNN tools, building a custom module is becoming more and more easy. With the right tools, you can have a custom module built in no time flat. This will outl...
Find this article and more in the DotNetNuke category
Read This Article . . .
How to Install DotNetNuke 5.0 Cambrian and Video This video tutorial covers installing using the Custom installation option, with SQL Express and also an external SQL Database. Find out more about which package to download and how to kick off the ...
Find this article and more in the category
Read This Article . . .
How To Customize the Privacy and Terms Links on Your DotNetNuke Portal Straight out of the box, DotNetNuke already has a lot of things covered. But, what do you do when you are ready to begin customizing your site. Sometimes, it’s not so easy to figure out how to make t...
Find this article and more in the 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 . . .
Getting Aquainted with the DNN Classes So, you've decided to start checking out DotNetNuke development and you're wondering where to start, right? Well, it's easy to start taking a quick tour of the DotNetNuke classes now with the help o...
Find this article and more in the category
Read This Article . . .
I Need to Modify the What to Install DNN? What in the World is a Web.Config File Anyway?? If you're wondering what in the world a web.config file is, then wonder know more. . .in about 5 minutes, you'll know more than you do now and be well on your way to moving forward.
Find this article and more in the Web.Config category
Read This Article . . .
How to Install and Configure ActiveDirectory Provider for DotNetNuke 5.0 The directions for installing and configuring extensions in DotNetNuke 5.0 are very similiar, but slightly different than from previous versions. Here's how to install the ActiveDirectory authentica...
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|