amironline
New Member
For all the benefits of using debugging tools which let you stepthrough the code, view local/global states and contexts, etc., I still find sometimes the easiest way to figure out what's wrong is to sprinkle debug statements through the code and see where something goes wrong first.Now i'm fiddling with ASP.NET, rather than executing the application, it starts up a web server which i can then access over localhost, and Console.WriteLine() no longer writes stuff to the VS output console when i go to the page. Is there any way to print stuff there? The alternative is write to a log file (i.e. what you do on a real web server anyway) but i'd rather not if i can avoid it. My Googlefu has not brought me any enlightenment.