I have an advanced scenario that is producing an exception that I suspect is a simple configuration setting but I don't know what it is. I have an Indigo service (actually one of a whole bunch) that has been working with IIS6/Windows XP and Nov CTP. Our dev team moved to the Dec CTP and we have verified that there are zero changes in our code or config andit works on XP/IIS 6.0. Meanwhile bonehead Sam has overwritten his "work" system with Dec Vista and IIS 7. Everything like VS2005 and WinFX is working but I am getting this exception from Indigo on running:
System.ServiceModel.ProtocolException
{"The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8)."}
Do I need to change some setting in IIS 7.0 to get it work It seems like a mismatch between text/html and application/soap+xml both using charset=utf-8. IIS7 is set to “utf-8“ for “Requests“, Response Headers and Responses under Globalization. We are using wsHttpBinding.
Advanced Indigo Service Question on Dec Vista
Shuvro Mazumder
Solved!
The Real Solution: Bless my readers! One hit it, in that the VD I created for the service was not an Application. Of course, being a (former) CLR Guy I should have known this, “When a VD is not created as an application, the runtime will (by default) not probe any of the VD’s bin directories, and instead just look in the GAC/bin of the website.” DOH!!
Skar
Findings so far...
Solution So Far: The first aspect of getting things correct, as somone emailed me is making sure that the .svc file extension was configured as a file type. That got me to the point where I could browse to the .svc file on my local machine and it is not finding the built assembly even though it is indeed BUILT and in the virtual directory's bin directory. Running it still produces the same error however.
Solution Part 2: That just won't stand with me so I tore open the offending DLL with Reflector and sure enough the type is there inside the right DLL and namespace and public. There has to be something about how IIS7 is dealing with this.