I used to have lots of hassle around reserving portions of the HTTP namespace so that ( e.g. ) WCF services can listen on them. I remember writing about it here in the past.
In more recent times, I avoid all that stuff altogether and just use a simple netsh command and this is a reminder to myself of how to do that because I forget every time so here’s the link for “next time”;
Just a quick plug – tomorrow evening I’m doing a session on ADO.NET Data Services (“Astoria”) at the SQL Server User’s Group at Microsoft, Reading.
See here for details;
it’d be great to see you there.
I had a quick look at the binary XML encoding for SOAP messages with Silverlight 3’s updated WCF library.
One thing that struck me in all this is that it looks like (i.e. as far as I can tell so far with reflector) that the WCF stack has gained binary XML encoding but hasn’t gained MTOM XML encoding.
Until now, Silverlight just had the basicHttpBinding (plus a polling duplex variant) and the Basic Http Binding is about as interoperable thing as you can get so I was a bit surprised that the next step looks to be binary XML (proprietary) and not MTOM XML (standarised).
Regardless…I had a quick experiment with it and built a service which I configured up with a custom binding as in;
and then I just pointed Visual Studio at the service and did an “Add Service Reference” and all was good.
I had a quick look with Fiddler to try and make sure that it’s doing what I think it’s doing and that’s pretty much that 🙂
Mike Taulty 