Menu
My VS.NET 2008 solution is taking longer and longer to compile (ASP.NET 3.5 + ASP.NET MVC 2 + C#) and I am wondering if there is a way to know what project takes the longer to compile and why? I disabled the compilation of a few projects and it helped reduce the build time but I want it faster.
522
When you start debugging in Visual Studio by selecting Debug > Start Debugging, or pressing F5, the Diagnostic Tools window appears by default. To open it manually, select Debug > Windows > Show Diagnostic Tools. The Diagnostic Tools window shows information about events, process memory, and CPU usage.
Open the Performance Profiler by choosing Debug > Performance Profiler (or Alt + F2). The tool shows each async operation in a list view. You can see information such as the start time, end time, and total time for an async operation.
A profiler is a tool that monitors the execution of another application. A common language runtime (CLR) profiler is a dynamic link library (DLL) that consists of functions that receive messages from, and send messages to, the CLR by using the profiling API. The profiler DLL is loaded by the CLR at run time.
Tools -> Options... -> Projects and Solutions -> Build And Run
Then change MSBuild project build output verbosity
When on normal (defaul is minimal) it gives timings for each project, so this could be used to pin point what is causing the slow down. (Assuming you use the Output window)
Or adjust to a higher level to see more detail of what is going on during a compile.
117
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
