So I've just recently decided to start migrating a number of our module over to DNN4.0 and ASP.net 2.0.  I followed the tutorial that Shaun has on ASP.net about doing the custom module development.  Everything went fine, however, the project item templates don't show up in Visual Studio.  I've tried this on two different machines and I get the same result.  Any ideas?

---

Tony Valenti
Tony.Valenti@PowerDNN.com
+001-402-650-6072

PowerDNN.com - World Leader in DotNetNuke Hosting and DNN Hosting
DNN Hosting Australia - DNN Hosting Europe - DNN Hosting US

I've not encountered that, so just to Clarify:

• Right-Click your Current Project = http://localhost/dotnetnuke/ (or whatever) in the Solution Explorer Window.
• Click on = Add New Item…

You should see “DotNetNuke Module” and “DotNetNuke Skin” under My Templates.  The actual path to this I believe should be:

C:\Documents and Settings\Vogel\My Documents\Visual Studio 2005\Templates\ProjectTemplates\Visual Web Developer\VisualBasic

Check there.

If you’re still having trouble you still have a couple of options:

1. Unzip the template to C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\ItemTemplatesCache\Web\VisualBasic\1033\DotNetNuke Module.zip\ folder.  Reinstall VS 2005.  The “DotNetNuke Module” will appear as a main template (visual studio installed templates).
2. Alternately, if you use the code here you won’t need the template.  (Actually it is Shaun’s template converted over).
   

 

---

    - Doug Vogel     

FWIW I made the same mistake initially. So you have some company.

There are, however, C# templates for DNN modules. I've been successful so far doing C# modules, after I discovered how to modify the web.config to separate different app_code subdirectories out by language. Apparently it won't let you put more than one source language in a folder. Which doesn't entirely make sense to me, because if it's all being compiled to MSIL, why should it matter if one file is VB and another C#?

Anyway, there ya have it.