Hello.
Im having a hard time and been banging my head in the wall.
I want to learn how to develop new modules and have a new WAP project setup that generates one small (17kb) dll in the DNN bin folder. 

The problem is that every time I compile my WAP project the startup time in the webbrowser takes 20 seconds.
20 sec is a long time and it's really frustrating when trial and error testing.
The module works fine when it's loaded. No error. 

The problem as I understand is that the module dll is moved to the bin folder.
Net2 framework then updates all the dll in the bin folder, the first time the site is loaded and this takes time.

Im running DNN 4.9 & Vs2008.
I have a new DNN installation and a new module created with the "Starter kit template".
We tried the same setup on another computer and have the same 20 sec startup time after the module been compiled.

I wonder if there a way around the 20 sec delay?

Is everyone developing in DNN having this problem or is it just me?
What is your statup time of a new module project ?

Best regards,
Henrik

Sorry. I chould have spec my computer.

I have a dell Xps laptop with dualcore T7200 2Ghz Cpu, 2Gb Ram, Xp Pro, ISS 5.1.
It a pretty fast computer.

It feels like 20 sec is realy slow and the module development workflow is a pain.
Is this normal?

// Henrik

Thanks Declan - I guess your the project is also a WAP where the changes is in the dll ?
Ok. So I'm not the only one with a slow workflow :)
 
If this is the way it is, it feels like a big problem?
If I'm going to develop a new module for a customer and every build takes 20-27 sec just to start, it will take a long time to finish and validate.
It also alot of time wasted in the project where the programmer sitting and waiting. 

Is there no way to develop new modules that is more effective?
It feels like I missed something?