Debug.WriteLine
-
OK, can someone here confirm for me that MS screwed up here? VS2008 allows you to use Debug.WriteLine to send data to debug stream where I can pick it up via a tool like DebugView. VS2010 DOES NOT seem to allow this at all. I can see the debug data in the immediate window in the IDE but nothing appears to make it out past there... If I run the EXE file I created in VS2010 as an administrator (right click and use the run as admin option) I can see the output written to the DebugView window but can't obviously catch any errors in the IDE and use that like normal. VS2008 allows me to see the data in both areas without having to run as an admin at all. If I start the process outside of VS2010 and see the debug in the debugview window then attach to the process using the IDE, the IDE horns in on the debug stream and stops it from going to debugview also. UGH! I really don't get this 'progress'. BTW - I put this post here because I was really NOT sure where to put it... this is not a C# vs. VB thing.... Maybe an IDE thing but we don't have an area just for that :)
-
OK, can someone here confirm for me that MS screwed up here? VS2008 allows you to use Debug.WriteLine to send data to debug stream where I can pick it up via a tool like DebugView. VS2010 DOES NOT seem to allow this at all. I can see the debug data in the immediate window in the IDE but nothing appears to make it out past there... If I run the EXE file I created in VS2010 as an administrator (right click and use the run as admin option) I can see the output written to the DebugView window but can't obviously catch any errors in the IDE and use that like normal. VS2008 allows me to see the data in both areas without having to run as an admin at all. If I start the process outside of VS2010 and see the debug in the debugview window then attach to the process using the IDE, the IDE horns in on the debug stream and stops it from going to debugview also. UGH! I really don't get this 'progress'. BTW - I put this post here because I was really NOT sure where to put it... this is not a C# vs. VB thing.... Maybe an IDE thing but we don't have an area just for that :)
Sorry, I can't help you out as I don't use Debug.WriteLine at all. However a little rant like this normally appears in Da Lounge to maximize reaction. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
Sorry, I can't help you out as I don't use Debug.WriteLine at all. However a little rant like this normally appears in Da Lounge to maximize reaction. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
Luc Pattyn wrote:
However a little rant like this normally appears in Da Lounge to maximize reaction
:laugh: :laugh:
Regards, Sathesh. The best way to express one's gratitude to the Divine is to feel simply Happy..
-
OK, can someone here confirm for me that MS screwed up here? VS2008 allows you to use Debug.WriteLine to send data to debug stream where I can pick it up via a tool like DebugView. VS2010 DOES NOT seem to allow this at all. I can see the debug data in the immediate window in the IDE but nothing appears to make it out past there... If I run the EXE file I created in VS2010 as an administrator (right click and use the run as admin option) I can see the output written to the DebugView window but can't obviously catch any errors in the IDE and use that like normal. VS2008 allows me to see the data in both areas without having to run as an admin at all. If I start the process outside of VS2010 and see the debug in the debugview window then attach to the process using the IDE, the IDE horns in on the debug stream and stops it from going to debugview also. UGH! I really don't get this 'progress'. BTW - I put this post here because I was really NOT sure where to put it... this is not a C# vs. VB thing.... Maybe an IDE thing but we don't have an area just for that :)
-
Yes, I know how to use the statements themselves. I have been using them for years now. The oddness seems to be specific to VS2010 and how it allows, or rather does NOT allow the output from these statements to leave the VS environment. In previous versions of VS I used to be able to fire up a unified debug collection tool like windebug and gather all my debug statements in one log file This was helpful when trying to gather coordinated debug between several different processes together in one area. Now it appears as if the IDE gets in the way and blocks that ability. You can see the output from Debug.WriteLine in the IDE area but it never makes it out into the standard debug stream like it used to so collecting it together from several instances of VS at once is not possible. This also means that now I have to write my debug statements to provide a date and time component in them where collecting them in the windebug tool used to do that for me, and once again, used to do it from several instances at once.