Debugging a Web Application in Visual Studio 2008

When a colleague of mine debugs a web app in his visual studio instance, his output window passes through all the assemblies that are compiled (at least I believe this is what he does), but mine does not. I see the text "Ready" flashing intermittently in the status bar, which I believe is similar to what is being dumped in my colleagues' output window. Does anyone know which switch I need to flip to get this to work on my instance? Both of our output windows are set to "show output from:" Debug. The reason I am asking all of this is because this particularly smelly app that I was asked to help on takes something like two or three minutes to "expand" before I actually see an instance of explorer for this site and I was thinkingthat this output can help me figure out why it takes so long to spin.

0


source to share


3 answers


I realized that if I right-clicked in the console area of ​​the Output window when Show Out: Debug is selected so that there are 6 different outputs available, some of them were not selected on my machine, but they were selected by my colleagues, I now get the result that I was looking for. As for another issue I'm currently researching, it looks like a lot of HttpCompileExceptions and NullReferenceExceptions are thrown when "spinning" ... I wonder if this is normal behavior or not.



0


source


You want to make sure that you are using the Verbose (or whatever Minimal) parameter to output the assembly. Then just make sure the Output window is open and set the Build dropdown menu.



Tools-> Options-> Projects and Solutions-> Build and Run-> Deploying MSBuild Project Build Output

0


source


Another thing I noticed when "Building" a website (as opposed to a web application), the build process takes a long time compared to a web application. I think the slow build speed is just a byproduct of how the website is compiled, not the code itself.

Also, usually these DLLs you see blinking in the prepared box are debug assemblies / symbol files / etc being loaded into the debugger and everything related to processes ...

0


source







All Articles