A bit overwhelmed by DNN module development. Some things I have researched indicate that if you change code files or .ascx files that you would have to uninstall the module on the site and then reinstall it (albeit my recollection is that it was for earlier DNN version). I am asking this question because I saw some video today from Scot Wilkinson (sic?) wherein it appeared he just simply refreshed the site page and all was fine. Now I am not sure if he was doing just-in-time compilation or if he re-built the module project in VS.

So, my question is if I am developing modules using VS2012 and using the Chris Hammond's (sic?) template, when I "rebuild" the module do I have to then go into Host>Extensions and unload/reload the module?

Sorry if this doesn't make sense. I'm almost of the mind to just use the Module Creator, but I don't like that it places all my code files in /App_Code. I'll probably ask another question about that (I am not entirely sure for a low volume site whether pre-compiled .dll's will be better off than just-in-time compilation to justify the extra work).

Provided your development is happening inside a working dnn install - and your compile is setup to put the dlls into the /bin/ folder - there is no reason at all why you would need to uninstall/reinstall the module on that dnn installation.

For small sites - I really find the wsp process to be much simpler though - yes you need to put controls and objects into /app_code/  - but there is no need to compile anything - you can change a line of code - refresh the page and see the results - whats more you can debug at the same time too - getting all but realtime testing workflows.