1/29/2008

.NET experiments

The first time I tried the .NET Framework was for a "throwable" GUI project ; I then decided to test the brand new MS Visual Studio 2005 beta 1. The development went pretty smoothly, and I was quite nicely surprised.

Then came MSVS 2005 beta 2, I decided to continue the development with this shiny new toy, hoping that it would fix a few quirks with the GUI Designer - I mainly remember that I had to spend much time to change my code, as some of the API changed between beta 1 & beta 2...

The same reproduced for the final MSVS 2005... I thought it funny to change an API this late in a product life...

I'm now working on another project with .NET Framework 2.0, just started a few weeks ago. Last week, I checked in my changes before leaving the office - everything running smoothly ; the following morning, I run my project to freshen my memories, and... crash...

Huh.

After many rollbacks, head scratchings, reboots, rebuilds, came an idea... what if... what if the message I saw the night before was not so iniquitous - you know the Windows Update message, that tells you not to worry, that your computer will shut down as soon as the updates are installed...

One uninstall of .NET Framework 2.0 SP1 later, everything was up and running smoothly again...

A few hours after that I figured a workaround for the brand new bug (or feature?) in SP1 that reads 'Unable to cast object of type 'System.Reflection.Module' to type 'System.Reflection.Emit.ModuleBuilder'. in the inner code of mscorlib's System.Reflection.Emit.AssemblyBuilderData.GetInMemoryAssemblyModule()

I'm not sure I'm only enjoying toying with .NET...

No comments: