How can a newly added global.asax file make a mess of my WCF service
-
08-10-2019 - |
문제
I have a silverlight app that uses WCF both by polling Duplex and "normal" async calls. everything was working fine, until I added a global.asax file.
After an hour of googling, I came across this rather dated blog by Jean-Dirk Stuart that suggested commenting out the stubbed Session_start event.
Sure enough that corrected the problem, but it raises a concern. Why would this seemly benign member of the global.asax file break the wcf calls.
해결책
Yeah, this is a little known but annoying issue. The problem comes down to session state being enabled once you add a global.asax file to your web project. Once session state is enabled, the server will only execute the calls sequentially. Here are two articles with some more in-depth information:
This behaviour only occurs when using the browser networking stack, so your options are:
- Disable session state in your web project, or
- Use the client networking stack
Hope this helps...
Chris
다른 팁
There are some types of binding which support accessing asp.net session data, I really dont see how it would affect unless WCF tries to hook into the session_start event just like a http module does. You could also use reflector to disassemble the code where you where getting the exception.