I\'m trying to debug a large ASP.NET application.
I set a breakpoint on the first line in Page_Load in Default.aspx.cs.
When I start the application, my
Sounds silly, but put a breakpoint earlier in the process: maybe the process doesn't reach the breakpoint.
Always look for Solution Configurations to be Set As "Debug" for debugging. It may change to Release configuration after publishing.
I had this problem recently (WinXP, VS2003), and tried many of the solutions above with no success. Then, I realized that there were multiple versions of the .Net runtime installed. So, I brought up IIS 5.1, located the proper virtual folder, went into properties and then the ASP.NET tab, and changed the ASP.NET version from 4.? to 1.1, and it appeared that this solved the problem. It could be that the solution is this, PLUS one or more of the things above.
Also, all of the above make up a "kitchen sink" of different things to try. This is like throwing a bunch of spaghetti noodles against the wall, hoping that some of them will stick. And, some of these "solutions" may cause other problems in your program. For example, the suggestion of setting AutoEventWireup="true" may cause some of your events to fire twice!!! (see http://support.microsoft.com/kb/814745).