Rescinding earlier comments...

I'm not going to put any more effort into trying to solve the "framework compatibility" problem that was discussed, because after talking with some people over at MS (thanks RobH and Scott Louveau) I've decided to stand by my original statement. The only responsible thing that control developers should do is have a build for each version of the Framework. I don't want my 1.1-compiled app trying to run on 1.0, and you shouldn't either. You want to give your users the best experience possible, and by only providing one version, you are not doing so. I will blog about a few possible solutions that MS suggests within the next day or so, but I agree with them and their recommendations.

2 Comments

  • If you target 1.1 and not 1.0, it's of course not that clever to build against 1.0. If you want to target 1.0, you can't target 1.1 anyway and can't include 1.1 features. If you still want to offer 1.1 customers a true 1.1 experience then you have to opt for 2 codebases. (and when you patch, you have 4, and after you patch, you have 6 etc). :)





    It's a matter of choice. For the projects currently in development, all targeting 1.0, it's an option to keep it on 1.0 and go for 1.1 in next projects.

  • So what is MS's recommended "drop-off" point going to be? Five versions back, six, seven? Will there need to be a version for every Framework rev?





    If .NET continues on for a while we will be trading DLL/COM hell for Assembly hell.





    adam...

Comments have been disabled for this content.