Darth Reed

Now that I have a place to put my quasi-technical babble over at MSDN, the space is reserved for me to spew my political bile and enjoy all things sci-fi. Heh.

Friday, October 15, 2004

Has .NET Framework 1.1 SP1 eaten any of your apps, yet?

It's been a while since .NET Framework 1.1 SP1 was released, but being as test-first as the Executives That Be will permit, we finally got it on the testing schedule (because the IT monkeys were pestering us for permission to run Windows Update again)... and discovered that it broke exception propagation from web services to client code. We opened a ticket with Micro$oft (SRX041013603588 is still open) to figure out why it behaves this way.

The really spiffy part is that you can get web services to behave exactly the same way pre-SP1 by enabling custom errors in the web.config. The symptoms are: the error message is truncated to a fixed number of characters along with the omission of the class name and the omission of the stack trace (if you have a debug assembly underneath). If you're counting on the class name to handle specific exceptions differently in your proxy class, then .NET Framework 1.1 SP1 will hose your code. I've got screen caps and working code of examples, if anybody cares.

Grrr. Maybe Iliad had the right idea. Invade Redmond. Fix the offending Microsoft code myself. It's what would be best for all mankind. Heh.