Debugging Problem in VS 2005
-
My config: VS 2005 Pro with SP1 C# 2005 .NET Framework 2.0 SP2 Vista Ultimate SP1 all current patches applied P4 3.0ghz w/ 1.5GB RAM and (1) 300GB disk w/ 27.5GB free (system/boot disk), (1) 400GB disk w/ 74GB free Problem: no matter how simple an app I create, debugging does not work - i.e. I can set a breakpoint that I know is crossed but the app does not fall into the debugger. These are .NET web apps. I created one with a single form and created several breakpoints, one in Page_Load against a simple string which I programmatically set a value for and one in an asp:validator that I know is hit and passed. VS even asks to set the app for debugging, and IE is set to show scripts, etc. Can someone help me to understand what I'm missing and why I can't debug anything simple or complex? You can probably imagine this is making me crazy and I'm having to write data to textboxes just to see what's happening when something goes wrong. Some things I just can't test for at all because of this. Thanks in advance!
-
My config: VS 2005 Pro with SP1 C# 2005 .NET Framework 2.0 SP2 Vista Ultimate SP1 all current patches applied P4 3.0ghz w/ 1.5GB RAM and (1) 300GB disk w/ 27.5GB free (system/boot disk), (1) 400GB disk w/ 74GB free Problem: no matter how simple an app I create, debugging does not work - i.e. I can set a breakpoint that I know is crossed but the app does not fall into the debugger. These are .NET web apps. I created one with a single form and created several breakpoints, one in Page_Load against a simple string which I programmatically set a value for and one in an asp:validator that I know is hit and passed. VS even asks to set the app for debugging, and IE is set to show scripts, etc. Can someone help me to understand what I'm missing and why I can't debug anything simple or complex? You can probably imagine this is making me crazy and I'm having to write data to textboxes just to see what's happening when something goes wrong. Some things I just can't test for at all because of this. Thanks in advance!
Hi Mike.. <%@ Page Language="VB" MasterPageFile="~/........"**
AutoEventWireup="true"
**CodeFile=".....aspx.vb" Inherits="......" title="....." %> Change autoeventwireup to TRUE and try.... Regards Rajeesh MP
-
Hi Mike.. <%@ Page Language="VB" MasterPageFile="~/........"**
AutoEventWireup="true"
**CodeFile=".....aspx.vb" Inherits="......" title="....." %> Change autoeventwireup to TRUE and try.... Regards Rajeesh MP
Unfortunately, all pages have AutoEventWireup="true", here's a sample of a simple app page:
]]>
Pick a Team NamePick a name for your team
Name: ErrorMessage="You must enter a team name." ControlToValidate="txtTeam" Display="dynamic" /> ErrorMessage="That name is already taken. Please pick another." ControlToValidate="txtTeam" Display="dynamic" OnServerValidate="custval\_txtTeam\_ServerValidate" />Thanks for trying - it seems to be something deeper. When I press f5, everything executes, just no stopping at breakpoints. The Build is set to Debug as the active, DEBUG and TRACE constants are defined, it's set to full debug mode, any CPU and platform and the ASP.NET debugger is checked..... Strangest thing.....
-
My config: VS 2005 Pro with SP1 C# 2005 .NET Framework 2.0 SP2 Vista Ultimate SP1 all current patches applied P4 3.0ghz w/ 1.5GB RAM and (1) 300GB disk w/ 27.5GB free (system/boot disk), (1) 400GB disk w/ 74GB free Problem: no matter how simple an app I create, debugging does not work - i.e. I can set a breakpoint that I know is crossed but the app does not fall into the debugger. These are .NET web apps. I created one with a single form and created several breakpoints, one in Page_Load against a simple string which I programmatically set a value for and one in an asp:validator that I know is hit and passed. VS even asks to set the app for debugging, and IE is set to show scripts, etc. Can someone help me to understand what I'm missing and why I can't debug anything simple or complex? You can probably imagine this is making me crazy and I'm having to write data to textboxes just to see what's happening when something goes wrong. Some things I just can't test for at all because of this. Thanks in advance!
-
i had same problem, it solved by when i start dotnet framework by right click and run as administrator on VS sort cut or on programs. you may try this.
Anshuman Singh
-
i had same problem, it solved by when i start dotnet framework by right click and run as administrator on VS sort cut or on programs. you may try this.
Anshuman Singh
hi Anshuman.. thatz a good one..Thanks for the information Regards Rajeesh MP