I have not worked alot with ASP.Net 2 and do not know why compiling the project takes so long. While i am develoing a simple DotNetNuke 4 module, some times for a little change in the User Control or the code, it compiles all other contents. How can i make it to comile only my new module? not the whole web site? it is really wasting my time.....

Thank you

I recommend you to take one of these project modules (e.g. Feedback) and compare these settings with yours.  It's true when the library changes you must completely complile the site but normally you must do this once per release. The rest checks if the dlls are up-to-date. One of my module compilation runs takes me ~ 20 secs. 

Every time you change any resource stored in the BIN folder - asp.net effectively forces an application restart.
This is a fact of live for any ASP.NET based site.

Whenever you compile your module - its dll is being changed in the BIN folder - so you get an application restart.

When asp.net 2.0 was developed MS set about coming up with a new development methodology that removed this issue.

The key to this methodology is Partial Compilation - and in DNN terms
- the use of DYNAMIC modules - INSTEAD of Compiled modules during development.

Since a dynamic module does not create a COMPILED DLL - there is nothing in the development cycle to trigger an application restart.

>>>>

The downside of course is that you dont have a DLL for distribution purposes.

SO what we do these days is - do all our development testing in a dynamic module -
then at release create a compiled version of the module and make a DLL.

It is a little bit of a messy step - BUT does avoid a lot of frustration in the DEV phase.

It should be noted too that- if you are not releasing a module to the public
 - then there is not real valid reason to bother with a DLL.

Just copy your files onto your live server and away you go - no DLL needed.

Westa