Hi,

I would like to know if and how I can create modules in VS2005 without using the starter kit?

Just like the documentation shows for VS 2003, the problem I am having is the module code is not included in the source install of 4.x . Is there anyway to get the module source as a hole or all they all separate? The instructions in the Wrox Pro DNN 4.0 book for VS 2003 mention opening the DotNetNuke.DesktopModules.sln file but this doesn't come with the 4.x source install.

Should I just use the starter kit for dev of modules? To me it appears the Starter Kit creates a whole new dnn web application and then you can start creating modules for that web application.  If I do, then how do I load my custom module to a DNN source install? Do I have to create a PA for that or can I just Xcopy the files over?

I am so very confused about this.

Thanks.

Thanks , Michael Washington's  tutorials are a great start.

I have gone through these http://www.adefwebserver.com/DotNetNukeHELP/DNN_ShowMeThePages/ and

http://www.adefwebserver.com/DotNetNukeHELP/DNN_Things4Sale/  and http://www.adefwebserver.com/DotNetNukeHELP/DNN_Module4/.

I am still however not sure if I can just xcopy the files I create and build with any of these methods from a development dnn to a production dnn?

 If I can xcopy then do I am assuming that I just follow the same instructions to load the module into the production dnn as given in these examples. Is that correct?

Thank You.

You did the tutorials, great. I want to know what questions you encounter from this point on. There are more tutorials to follow and I want to cover these issues.

As far as XCopy. I wan to add to what Shaun Walker wrote. There are 2 ways to XCopy:

• Upload a new module (in a .zip file and a module manifest that has the module version incremented). I recommend this because it will also allow you to run upgrade SQL scripts.
• FTP the changed files - if you have a change in a class (for example surveyoptions.vb) you can just FTP the file to your DNN site and ASP.NET will detect the change and use the new file. Real easy to do. This is the joy of the new ASP.NET compilation model. You don't have to compile and change the entire assembly (the .dll) for a module. You can change just a single code file. The problem is you don't have versioning so it's hard to "roll-back" if you need to.

For normal practices you want to stick to the DotNetNuke API and deploy changes using modules because it has so much to offer:

• Testing - When you test using code packaged as a module you know you have all the elements like pictures and other files are packaged in the .zip file so you don't lose track of them
• Versioning - This allows you to determine what changed and helps you roll back if needed
• SQL Upgrade Scripts - Each module will run the needed sql upgrade scripts that you were able to test on your test server so you know it works,