Why are the code-behind pages for an ASP.NET web application locked at run time? I have older projects (probably defined as "web sites" instead of "web apps") where I can edit the code behind, refresh the browser, and see my changes. With the web app, I have to continually close and reopen the browser if I want to see my changes live. Is there a setting or something I'm missing to allow me to edit at run time, and without restarting the debugging session?
+3
A:
When using IIS as your development server, Edit and continue is not currently available for Visual Studio for ASP.NET.
See this blog entry, however, that shows it is possible for the Visual Studio 2005 Web Application Project Project type. It requires using the Visual Studio Development Server (Cassini) during development instead of your local IIS (see the properties box on the project).
johnc
2008-11-20 21:46:31
+6
A:
You can enable Edit and Continue in the project properties. Right click the project in the solution explorer, select the Web tab and check Enable Edit and Continue.
Now you can edit your sources, but you have to pause the debugger to do so.
Rune Grimstad
2008-11-20 21:50:04
I have that enabled, but whenever I make a change, it says it can't continue until I restart the debugger.
gfrizzle
2008-11-20 21:55:55
Does it say anything else? It works properly here.
Rune Grimstad
2008-11-20 22:04:28
I see where I'm getting hung up. You're right, if I pause I can make changes, but if I try to edit a LINQ statement, I get "Unable to apply this change while debugging. Statement containing a query expression was changed. You must revert the change or stop the debugging session. Oh well...
gfrizzle
2008-11-21 14:09:20
That is true. Methods with a LINQ query cannot be edited this way.
Rune Grimstad
2008-11-21 14:19:30
+1
A:
No, in web applications, the codebehinds are pre-compiled into dlls, so any change in the dlls will recycle the App pool, and stop your debugging session,
If you press ctrl-F5 instead of just F5 to start (or host you site in IIS), you start without the debugger, and don't need to restart the browser all the time...
Unless you really really need to debug a problem you can't figure out, You should start the web app without debugger, makes it snappier to start up. Every minute spent debugging is a minute not spent writing a unit test. IMHO you should write unit tests, they last longer.
AndreasKnudsen
2008-11-20 21:51:50
The only downside is that you can't see your changes incrementally. I prefer to make a few changes, refresh the page to make sure I'm on track, code some more, etc. You're right though, skipping the debugger does make the process snappier.
gfrizzle
2008-11-20 22:03:47