.NET conversion

This post comes after a LOOOOOOOONG silence. The reason is quite simple, I moved to a new job and currently I spend most of the time trying to figure out what did the previous programmer do. In some cases it's more like "why hadn't anybody shot him down while he was young."

But I did manage to do a small and annoying task, that's what this post about:)

Conversion of .NET1.1 to .NET 2.0

After converting 2 solutions from the .NET 1.1 to .NET 2.0 I've discovered a few nice things:

The 1st one is no matter how hard you try to avoid it, at the end you'll have to convert the solution project by project. Even if M$ claims it's not needed.

2nd because of new checks in the compilation the amount of warnings grows. In addition there are warnings about the conversion itself; why convert when you can annoy the programmer with a silly message like "you should x.x.y() instead of x.y()."

3rd issue is the moving of some code files. This thing is relevant for web applications and maybe for things I didn't need. I'm doing programs for actual users, not for the sake of M$'s revenues. The splitting of the forms to 2 files results in form.aspx and form.aspx.cs, just like before with one exception. The cs is now located next to the aspx, it goes to the App_Code only on "publish" with the compile at runtime. It would be OK if the need to re-copy the old app wasn't needed every now and then during the conversion. The result for me was a meaningless error message complaining on dupes. Luckily enough I managed to delete it after a few hours of chasing my tail trying to figure it out.

Hopefully I'll be able to write the post on dynamic javascript soon, it'll happen as soon as I get the thing to work...