I am using VS 2008 ASP.NET 3.5. I use some LINQ library for for my data access (my own data saved in a seperate tables). I develop modules in a seperate web application project using C#. I add a reference in DNN solution to my WAP and I copy ascx files to DNN solution. Everytime after I compile my WAP project, I need to wait for at least 5 minutes then the DNN solution can be started (both in development debug and in production server without debug). Yes the 5 minutes really kills me!!!

My development computer: VISTA 64 bit, 8G memory, 3.0GHZ core duo CPU, IIS 7.0. Server: 32G memory.

1. I tried to isolate LINQ to see if it is a linq problem. I add the user controls (acxs) in a seperate non-DNN project, it only takes less than 3 seconds to lauch (some code to access the same database from the same computer).

2. I am wondering if it is caused by hybrid C# and VB.NET code. My modules are sepratedly compiled to a DLL. I really doubt it could be a problem but I really do not want to use VB.NET. I will have to, if someone can confirm me it is the reason.

3. IIS 7.0? No I do not think so. It works greately for other applications.

BTW, without my C# LINQ modules, the DNN project can be started less than 30 seconds which is acceptable.

Thank you!

Hooligannes thank you very much. Remove reference then manual copy dll does help on the debug greatly!!! if no code is changed in DNN. If rebuild the whole solution, or there is code change in DNN, the debug launch time, according to page trace, is still about 180 seconds. is the 180 seconds (3 minutes) a normal time for launch a debug window?

The best way to develop a WAP project is to have it use its own solution, right now you can do that by just opening it separately. Without the DNN solution.

An alternative in the current solution is to change the configuration of the project so it doesn't build the DNN project(s).  You shouldn't be touching them anyway.

---