VS2005: edit-and-continue when running within IIS

[Oenone]

I am developing an assembly that can be used either by a Windows Forms
application or from within an ASP.NET web site.

When running within the Forms app, I can break into the code while it is
running and use edit-and-continue to modify the sourcecode and then
immediately execute the modifications.

When running within the web site, the source-code is all read-only when I
break into it. The little padlock icon appears in the tab for each of my
source files, and when I try to make a change the IDE beeps and displays
"Cannot currently modify this text in the editor. It is read-only."

Does anyone know why edit-and-continue doesn't seem to work in this
configuration? I have tried using both IIS and also the ASP.NET Development
Server, but in each case all my source was read-only...

Many thanks,

--

(O)enone

[Carlos J. Quintero [VB MVP]]

Hi,

The same happens when you are debugging a DLL which is an add-in: you can
not use Edit and Continue. I guess that when an assembly is used by other
process (a second VS instance, IIS, etc.) you can not use E&C.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"Oenone" <oe****@nowhere.com> escribió en el mensaje
news:nw***************@newsfe6-gui.ntli.net...

I am developing an assembly that can be used either by a Windows Forms
application or from within an ASP.NET web site.

When running within the Forms app, I can break into the code while it is
running and use edit-and-continue to modify the sourcecode and then
immediately execute the modifications.

When running within the web site, the source-code is all read-only when I
break into it. The little padlock icon appears in the tab for each of my
source files, and when I try to make a change the IDE beeps and displays
"Cannot currently modify this text in the editor. It is read-only."

Does anyone know why edit-and-continue doesn't seem to work in this
configuration? I have tried using both IIS and also the ASP.NET
Development Server, but in each case all my source was read-only...

Many thanks,

--

(O)enone

[dave.ploger]

It's too bad that Edit and Continue won't work with ASP apps. But is
there still a way to edit source files while running the debugger?
This was possible with VS2003.

Thanks, Dave.
Carlos J. Quintero [VB MVP] wrote:

Hi,

The same happens when you are debugging a DLL which is an add-in: you can
not use Edit and Continue. I guess that when an assembly is used by other
process (a second VS instance, IIS, etc.) you can not use E&C.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

"Oenone" <oe****@nowhere.com> escribió en el mensaje
news:nw***************@newsfe6-gui.ntli.net...

I am developing an assembly that can be used either by a Windows Forms
application or from within an ASP.NET web site.

When running within the Forms app, I can break into the code while it is
running and use edit-and-continue to modify the sourcecode and then
immediately execute the modifications.

When running within the web site, the source-code is all read-only whenI
break into it. The little padlock icon appears in the tab for each of my
source files, and when I try to make a change the IDE beeps and displays
"Cannot currently modify this text in the editor. It is read-only."

Does anyone know why edit-and-continue doesn't seem to work in this
configuration? I have tried using both IIS and also the ASP.NET
Development Server, but in each case all my source was read-only...

Many thanks,

--

(O)enone