This may seem like a dumb question, but we are still a little sketchy on how to get the module to show up in our development websites. I've gotten the template to work (and build) in both a DNN Source install and in a Solution that is using the DNN install.

What I don't understand in either case is how to get the module to show up in the DNN instance. Do I have to create a zip file, or can I copy the files over, the define the module? Any help would be appreciated

Thanks.

Rick

I have something like that... it's called BlankModule.Deployment, and is actually an MSBuild Web Deployment Project which builds all the projects in your solution, deploys their dlls to dnn bin, selects the appropriate files (dlls, controls, dnn file, images, etc...) and optionally packages them up and deploys them to some repository. It does all this at build time automatically.

It only misses the .dnn file generation and sql script generation.

It's all part of my BlankModule development solution (and described in my tutorials) if you are interested.

There actually is a Package Builder included in the DotNetNuke core.  The current version has some limitations, but it is our intention to "improve" it so that you can select what needs to be in the manifest (dnn) and what needs to be in the zip.