My goal is to develop compiled modules in C#.  The modules will ultimately be deployed to a production server via zip/.dnn file packages.   I would like to know the best way to set up VS2005 and how to configure my build processes for efficient development. 

My main concern is the procedure of registering the module with dnn so that I can test and preview it before deployment.  During development, it seems like I will need to edit code, compile, register the module in DNN, load it on a page and then preview/test it.  Does this mean that any slight change to the module code will require me to repeat this entire process?  I prefer to develop with very short iterations, and therefore edit/compile/test many, many times a day.   Having to register the modules with DNN  each time will be painful.  There must be some way to automate this!  Can the module installation be scripted?

I'm sure I'm not alone in this...  Anyone have any suggestions, links, etc?

Thanks. Along those lines, I came up with a solution based on a template by this guy: http://www.bertcord.com/Home/tabid/54/Default.aspx. 

I use a post-build event to copy the deployment files to the development DNN installation.  I do need to recreate the module from the manifest whenever I add a new control, though....

md C:\DNNDevInstall\DesktopModules\BasicAccounting.Presentation.CustomerModule
copy $(ProjectDir)*.dnn C:\DNNDevInstall\DesktopModules\BasicAccounting.Presentation.CustomerModule
copy $(ProjectDir)*.ascx C:\DNNDevInstall\DesktopModules\BasicAccounting.Presentation.CustomerModule
copy $(TargetDir)*.dll C:\DNNDevInstall\Bin
copy $(TargetDir)*.*pdb C:\DNNDevInstall\Bin
copy $(TargetDir)*.xml C:\DNNDevInstall\Bin