November 3, 2003
@ 04:04 AM

I just spent two hours trying to figure out why a chunk of code was throwing exceptions when compiled and run from my command line application but similar code worked fine when running in Visual Studio. The problem turned out to be a bug in the .NET Framework's XslTransform class which existed in v1.0 of the .NET Framework but not v1.1. Since I was using Visual Studio.NET 2003 [which uses v1.1 of the .NET Framework] to run my test app but compiling my actual application with the compiler for v1.0 of the .NET Framework I wasn't actually doing an apples-for-apples comparison when running both apps.

I'm tempted to uninstall v1.0 of the .NET Framework from my machine so I don't end up with facing this problem again. What a waste of time.

 


 

Monday, 03 November 2003 14:49:10 (GMT Standard Time, UTC+00:00)
Shouldn't MS ship a new service pack for v1.0 or is using v1.0 considered 'run at your own risk' situation?
Fernando Tubio
Monday, 03 November 2003 15:29:02 (GMT Standard Time, UTC+00:00)
I had a similar experience:
http://hoppersoft.com/Andy/PermaLink.aspx/e0dbddd9-2654-4fda-bf11-33bb380879dc

(sorry - it's a bit too long for a comment)
Comments are closed.