I have now been developing modules for DNN for about 6 months.  I dont know anything incredibly complex, but I know my way around.

What has been getting on my nerves is compilation time.  Right now, if I make a small change to a code-behind in a module, it takes ~35-45 seconds to first load up on the site.  I feel like its compiling or pre-compiling the whole framework each and every time.  That seems quite excessive, and it is really slowing my development down.  Does anyone know the correct practices and procedures for developing and debugging modules in DNN?

I dont think I was quite clear on my post.  I have looked through that website quite a bit and I have followed how it sets up websites and programs modules, but lately I am running into issues with compilation time.  I just tested it, and it took over a minute for my website to pop up after compilation again, making testing my code a pure nuisance.   Is there any way to set up the enviornment so that I do not have to reprocess the site each and every time?

The way I have it set up right now is I have my modules in separate projects, which are linked to the website.

Take a look at some of Scott Gu's VS2005 build tips. One is to change the default build style to build the page, and not the whole web site.

I like to work in Visual Studio,  and use the Build Page command to get things compiled. And then run my site through IIS. I tend to get better responce times then running cassini.