The only thing I ever find myself doing is getting a working instance of DNN installed. This will change only slighty for a dev environment. For example, you will want to make sure it has its own database instance, and it is running in debug mode (web.config).

Once that is done, I would suggest writing your modules using the WAP way, and not WSP. This means, building your modules similar to a library project, and not similar to a web site project.

The easiest way to get your first module created is to take a simple Core module like the Links module, and install the source version of it. Then, begin changing everything that you need to make it your own Links module (namespaces, project names, sql script references, etc.). From that point forward, you will have a working clean slate to begin all of your module development with.

---

Will
StrohlSiteDesign.com | My Blog | DotNetNuke® Skins by SSD | Orlando DNN User Group
Google Toolbar Button for DotNetNuke® | Suggested DotNetNuke® Upgrade Path(s)