Message from discussion
VS2005 - "Edit and Continue" changes are not allowed while deb
Thread-Topic: VS2005 - "Edit and Continue" changes are not allowed while deb
thread-index: AcXvyn81Yw6C7+qBQlKAEX0Z2va8qw==
X-WBNR-Posting-Host: 211.27.107.242
From: "=?Utf-8?B?U3RyZWFtbGluZQ==?=" <streaml...@nospam.nospam>
References: <8E46723C-C70E-402C-98F2-C50501A5D6BA@microsoft.com> <$30ysR17FHA.1236@TK2MSFTNGXA02.phx.gbl>
Subject: RE: VS2005 - "Edit and Continue" changes are not allowed while deb
Date: Tue, 22 Nov 2005 17:09:04 -0800
Lines: 171
Message-ID: <57005D95-8D8D-4C88-AF1C-7DC3250A250D@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.vsnet.debugging
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: g2news1.google.com!news3.google.com!news.glorb.com!logbridge.uoregon.edu!canoe.uoregon.edu!newshub.sdsu.edu!msrtrans!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
Here are the steps.
Initial setup:
Microsoft Windows XP Professional Version 2002 SP2
Microsoft Visual Studio 2005 Standard Edition Version 8.0
Microsoft .NET Framework 2.0
Microsoft Visual C# 2005
File->New->Web Site
ASP.NET Web Site
OK
File->Add->New Project
Class Library
OK
Add the following code to Class1.cs:
public Class1()
{
string foo = "bar";
}
Add the following code to Default.aspx.cs Page_Load:
ClassLibrary1.Class1 obj = new ClassLibrary1.Class1();
Set a breakpoint on that line.
Start debugging.
The following message appears:
Debugging Not Enabled
The page cannot be run in debug mode because debugging is not enabled in the
Web.config file.
What would you like to do?
[checked] Add a new Web.config file with debugging enabled.
! Debugging should be disabled in the Web.config file before
deploying the Web site to a production environment.
[unchecked] Run without debugging. (Equivalent to Ctrl+F5)
I clicked OK (add Web.config).
Web site started running under the ASP.NET Development Server - Port 1129.
(Note that in my real situation I am running under IIS.)
Break point hit.
Step into obj's constructor.
Step to foo assignment.
Attempt to change string.
I get the following error:
Edit and Continue
Changes are not allowed when the debugger has been attached to an already
running process or the code being debugged is optimized.
Note that the default Build properties of ClassLibary1 do not specify
optimized code.
Microsoft Windows XP Professional Version 2002 SP2
Microsoft Visual Studio 2005 Standard Edition Version 8.0
Microsoft .NET Framework 2.0
Microsoft Visual C# 2005
File->New->Web Site
ASP.NET Web Site
OK
File->Add->New Project
Class Library
OK
Add the following code to Class1.cs:
public Class1()
{
string foo = "bar";
}
Add the following code to Default.aspx.cs Page_Load:
ClassLibrary1.Class1 obj = new ClassLibrary1.Class1();
Set a breakpoint on that line.
Start debugging.
The following message appears:
Debugging Not Enabled
The page cannot be run in debug mode because debugging is not enabled in the
Web.config file.
What would you like to do?
[checked] Add a new Web.config file with debugging enabled.
! Debugging should be disabled in the Web.config file before
deploying the Web site to a production environment.
[unchecked] Run without debugging. (Equivalent to Ctrl+F5)
I clicked OK (add Web.config).
Web site started running under the ASP.NET Development Server - Port 1129.
(Note that in my real situation I am running under IIS.)
Break point hit.
Step into obj's constructor.
Step to foo assignment.
Attempt to change string.
I get the following error:
Edit and Continue
Changes are not allowed when the debugger has been attached to an already
running process or the code being debugged is optimized.
Note that the default Build properties of ClassLibary1 do not specify
optimized code.
""Jeffrey Tan[MSFT]"" wrote:
> Hi streamline,
>
> Thanks for your post.
>
> Have you tried to create a new project in VS2005 without upgrading? Does
> this problem still arise? If so, I suggest you provide some detailed steps
> to help me reproduce out this issue. Thanks
>
> Best regards,
> Jeffrey Tan
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
>