Armand Niculescu, BEng, MSM, is a 34 year old Art Director at Media Division. and he enjoys working with visual arts for film, web and print.

2 responses to “NET Framework version penetration?”

  1. Paul

    Interesting that you feel that version checking for the .NET framework might be an issue for you. It would be if you were writing a desktop app, or component, to be installed on a client’s PC, but if you’re writing web apps then you target the version of the .NET framework you have installed, and if it is to be installed on a clients server then it wouldn’t generally be considered an issue if they required a newer version of the .NET framework to be installed, especially as Microsoft have – to their credit – made it simply to have multiple versions of the framework on the same computer.

    Or maybe I’ve completely misunderstood the point you were making.

  2. Armand Niculescu

    Yes, I had desktop apps in mind. Sorry if I haven’t been clear about it.

    Consider this: you’re writing a .NET application, not something earth-shattering, but maybe a useful utility. The installer weights let’s say 5Mb. It doesn’t make a lot of sense to include the whole .NET framework with it to make a 50 Mb installer, but you don’t want to make the user download the framework unless absolutely necessary – ideally it should just work on his computer.

    With Flash, you can make an informed decision: if Flash plugin v.X is supported by 90% of the browsers while Flash v.Y is supported only by 40% it makes sense to target version X.

    But for .NET, the decision is not simple, especially for small free/shareware tools. Obviously, the safest decision would be to target .NET 1.1, but what if 80% of windows users already have .NET 2?