Do you want to have it done during the build phase, using MSBuild, or just the steps required to get a module packaged and uploadable?

If it's the latter case - Check out http://www.dotnetnuke.com/Community/F... I have the minimum steps to get a functional, uploadable module. It should be easily adaptable to an existing module.

If you are looking for the former case - I don't have a good write up for that. :) Get the source for the Gallery module and check the Buildfiles folder. It will have a .targets file which is how it packages the module. I have based the ones I use off of that. I haven't gone through and cleaned mine up and really read up on the commands, so I've not got the info, ATM, to write a 'minimum' MSBuild post. Working on it though. ;)

Hi Baartezu and many thanks for the link. I develop in a DotnetNuke Source environment using VS2008. Within the DeskTopModules I include a folder for the Module I am going to develop.

In that Folder I place my ascx and ascx.vb for the Settings module and function module, plus any  .resx files. I add a DNN file so I can add the module to DNN in my test environment and then instantiate it on a page for testing. If there are any SQL routines they are included in a SQL Provider in App_Code. This is fine and dandy and I can debug the modules in VS2008 with no problems at all. Great so far.

Now then, it is at this stage when testing is complete, that I now want to package this together as a DLL in VS2008, (let's say to send to Snowcovered for example), from my development Folder in DeskTopModules, plus any SQL stuff in App_Code with NONE of the  .ascx.vb files in sight in the PA.zip file. I was actually hoping, in my naivete that I could look up a simple step-by-step process for achieving this. The closest we have come is your description in the link you provided.

(Actually I sympathise with the poster that you were replying to, Baartezu, on that thread, because that is exactly my position. I have been working with DNN for 3-4 years but so far all my modules are still in source on the server. I have many years of programming so I have no problems there. But the simplest of jobs, or what should be the simplest, seems to be a very well kept secret.

WAP is Web Application Project, where modules are standalone ASCX and DLL files, that can easily be packaged without source code (as I stated earlier using the Extensions page and the Package option in DNN)

WSP Web Site Project model modules are built into DNN and use the APP_CODE folders, those can't be packaged and precompiled without quite a bit of work.

I recommend using WAP for your module development.

Here's an old blog post I made about using NANT to package, though it doesn't directly apply to DNN5 due to a few changes. I am working on a new template for visual studio that will use NANT and work for DNN5.

http://weblogs.asp.net/christoc/archi...