Heh, and all this time I thought i was going crazy...
There's a long list of fixes there...
http://support.microsoft.com/kb/945757
Printable View
Heh, and all this time I thought i was going crazy...
There's a long list of fixes there...
http://support.microsoft.com/kb/945757
personal favorite...
924895 (http://support.microsoft.com/kb/924895/)FIX: An application that is based on the .NET Framework 2.0 may crash unexpectedly
and here all along i thought it was just my coding style :)
considering how big the framework is, its not surprising to see a service pack come down the line... Just think of the number of fixes in your average Windows service pack.
Also .NET 2.0 is the still the most recent core CLR framework for both 3.0 and 3.5, so its good at least they are keeping it patched up.
The only real issue I have, is not knowing if the end user has SP1 or not, which could affect the way your code runs on their system.
dunno if there is a way to do it, but i know you can add custom install actions to setup projects, the problem i ran into was it tried to install the file while the main program installation was taking place. sure you could fit it in there tho...
The one relevant to me was all the way at the bottom of the list, but the weird thing is, it's going to take a long time anyways unless you precompile.
Funny, this just came up recently someone was adding a custom prerequisite to the bootstrapper and I was lending my knowledge on that subject.
My experience with doing this was because I wanted to make .NET 2.0 SP1 a custom prerequisite. I got it to work in the end pretty well. I could upload the bootstrapper package for you guys if you want it. It's pretty large so I don't know where I'd upload it to though.