Our solutions are almost identical.  I updated my sample solution to demonstrate yours as well.  The main difference is that in yours when working on a module you only have that project open.  I added a solution file to by download that demonstrating what you are recommending.  This way you can just open your module or you can open the DNN solution and the module.

Since are solutions are practically identical your solution runs into the same issues as mine when referencing ascx controls from the main project

The other concern I have with both of our solutions is writing to the main bin folder.  This could cause issues in VS2003.  I am hoping that this has been correct in 2005 but time will tell I guess.

Download my updated sample and let me know if this is accurate.

Thanks for the input

http://www.corderman.com/DNN1.zip

Bert

Hi, also trying my first steps with the discussed proposals, I wonder why you (and I) have to add those 'imports' statements. I am rather new to VB.net, but as far as I understand, using any class or module-method somewhere down in a namespace hierarchy needs to have declared that hierarchy by the imports statement.

So, when you install the DNN-Starterkit and the sample widget module, there is the ProcessModuleLoadException-Statement in the Page_Load event of the controls, but no 'imports DotNetNuke.Services.Exceptions'.

When you convert that widget-module to WAP, this part does not compile, unless you add the imports statement (ProcessModuleLoadException is a public method of the public module Exceptions).

Why?

Not that I am not able to add those statements (there are more of them), I just would like to understand it. What is the difference to the Standard-DNN-Installation in the WebSite Project to the WAP so I do have to delcare imports...?

Does anybody have an idea?

Thank you, Wolfgang