Well it is... but what is a module? a unit of functionality within a bigger framework... DNN

Also, my advice for the seperated solution is simply convenient based - as described in my tutorial

as for the copy local = false, in the past I've had the same problems that people here have, I've solved them with 2 things:

1. BuildSupport projects - solves partially the problem outlined on your link
2. Copy local = false - which prevents duplicate assemblies from beeing copied to the run directoy (where the rule applies - where they ARE duplicate) - I've had to implement this especially with larger module solutions

Thanks, that is the reason. You can use either 'imports' in each code-behind class or use the pages/namespace section in web-config to declare namespaces for all code-behind classes once (so you will declare those that you need every-time).

Thank you, now my understanding is clarified.

Wolfgang

Some questions regarding the conversion of the user controls (ascx-Files) to the web-application format:

The conversion adds a designer file to mycontrol.ascx, namely mycontrol.ascx.designer.vb. All the declarations in there are logical to me, but why do these declarations not exist in the web-site format?

Furthermore, if i pack my module to a zip-File for distribution, how does the dnn-manifest differ in the two setups:
a) Web-Site: include mycontrol.ascx, mycontrol.ascx.vb, all the App_Code-files (mymodule.dataprovider.vb...)
b) Web-Application: include mymodule.dll, mymodule.sqldataprovider.dll, mycontrol.ascx, mycontrol.ascx.vb(?), mycontrol.ascx.designer.vb(?), or are the latter two vb-Files included in the dll?