ASP.NET 3.5 BasicsIf you are new to ASP or ASP.NET programming with version 3.5, this is the forum to begin asking questions. Please also see the Visual Web Developer 2008 forum.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the ASP.NET 3.5 Basics section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
I know this is a bare bones basic question, but is there a good writeup or walkthrough for debugging ASP.NET? I have worked for a while in Visual Studio (Web services and windows applications) as well as M$ofts SQL Server and, unfortunately, I am used to being able to walk through the code to find and solve problems. There appears to be no way to put a breakpoint in the markup code and most of the time, for reasons I don't yet understand, the breakpoints I put in the code behind are for elements/symbols that are not loaded. I know there has to be a better way, I just want to find it.
Dennis Keith
Linear Mode
