If you have been using Visual Studio 2013 for a while, you will notice that it behaves differently from previous versions of Visual Studio when it comes to debugging web applications. Visual Studio 2013 will launch a new instance of IIS Express every time we debug our code and shuts it down at the end of the debugging session.
While this may seem a nice thing to have since a clean instance is started every time, but that wasn't the main purpose of this behaviour and obviously, it will create some problems when dealing with solutions that contains multi-tier projects i.e. a WCF/WF web host where Add or Update Service Reference is required.
In such environment, we usually run the WCF web host in Debug mode while we add service reference from the other projects. In this case, we are no longer able to perform such feat. We can however, workaround it by launching an instance of the host without debugging but after a while, we may encounter situations where this behaviour will become more of an inconvenience.
After some searching, I learned that this was actually caused by the new Edit and Continue feature in x64 environment. Disabling this feature will return Visual Studio 2013 to the previous behaviour of not shutting down IIS Express after debugging.
To disable the feature, simply Right-Click on your Web Host project and select Properties. On the Web tab, un-check the Enable Edit and Continue checkbox.
After disabling the feature, the IIS Express instance will be retained across the debugging sessions.
Home » Windows Communication Foundation » New IIS Express Behavior in VS 2013?
New IIS Express Behavior in VS 2013?
16:39
Jurnalis Jalanan
Labels:
.NET,
ASP.NET MVC,
ASP.NET Web Forms,
Developer Community,
Layered Architecture,
N-tier,
WCF,
Windows Communication Foundation
Popular Post
-
S6 / 4.235 cc / 268 PS / 283 ft/lb (384 Nm) @ 4.000 / 0 - 62 mph (100 km/h): 10,4 s / Vmax: 123 mph (198 km/h) (click images for a larger ...
-
The world is a wonderful, jacked-up place. I'd like to share what I see with you. This may be direct. This may be a life lesson learned ...
-
With thanks to citizen contributor "Iain" for drawing our attention to one aspect of some disturbing developments. "Iain"...
-
V8 / 4.395 cc / 555 PS / 502 lb/ft (680 Nm) @ 1.500 - 5.650 / biturbo / 0 - 62 mph (100 km/h): 3,9 s / Vmax: 193 mph (310 km/h) (click image...
-
If you think about it, one of the few marques in Europe that has the dynamics, the name and history to truly compete against the dominant pr...
-
As Ferrari engineers ramp up their efforts to complete the development of their new Enzo-replacing hypercar that is currently known by its i...
-
Which string concatenation method has the best performance? - I'm sure at some point in time, a developer will ask (or be asked) this q...
-
S4 / 1.390 cc / 180 PS - Engine of the year / 184 lb/ft (250 Nm) @ 2.000 - 4.500 / twincharger system (kompressor + turbo) / XDS front diff...
-
Photo: Diane Edwardson, June 8, 2012, 5:21 PM. All day today, Baby #3 has been branching, flapping its wings and hopping over its siblin...
-
V12 / 5.576 cc / 385 PS / 406 ft/lb (550 Nm) @ 4.000 / 0 - 62 mph (100 km/h): 6,6 s / Vmax: 155 mph (250 km/h) (click images for a larger ...
No comments:
Post a Comment