3 ms·

They're right to worry. It's a headache. Having a new version of the framework every year is also a headache (for desktop development anyway). I'm not sure w

They're right to worry. It's a headache. Having a new version of the framework every year is also a headache (for desktop development anyway). I'm not sure what else they can do, though. .NET is their development platform. They've got to keep turning out new stuff. Where else is it going to go?

jmatt 18y ago
I've never had any problems with getting installers to install the proper version of Microsoft's .NET framework. As for getting the right version of .NET on the customer's box their installer works (in VS2008) and InstallShield works with no problems. I've done product installs and enterprise installs with no problems from .NET framework versioning. I had problems upgrading code from 1.0 to 1.1 and from 1.1 to 2.0 but no problems upgrading to new .NET frameworks since then. I've also had no problems with VS2008 targeting different .NET frameworks. I agree historically it was a problem but M$ has addressed it recently and things seem to work. [EDIT: Reformatted and reworded things a bit]
- mattchew 18y ago
  If your customers have to download a big new framework before trying out your app, that is one more hurdle you've got to get past in order to sell. Customers who are not computer sophisticated may be scared away and others will consider it too much hassle (frex, if they are on dial-up).
  - jmatt 18y ago
    Ya that is a valid point. I've yet to work on a product which targets dial-up or older machines. The product I work on right now is for engineers who design and manufacture things. 97% of them have .NET 2.0+ with XP or Vista. The remaining 3% are Windows 2k. Almost everyone has .NET 2.0 installed but occasionally there is some squirrelly box in a manufacturing plant with no internet connection. For those customers they just use a CD with the application and framework on it. If you are targeting customers using Windows 98 or Windows 2k then you are also limited to .NET 1.1 or 2.0. .NET 3.0 and 3.5+ are XP or Vista only. And as I mentioned before most people in the windows world (at least engineers) are using XP.

jmatt 18y ago

I've never had any problems with getting installers to install the proper version of Microsoft's .NET framework. As for getting the right version of .NET on the customer's box their installer works (in VS2008) and InstallShield works with no problems. I've done product installs and enterprise installs with no problems from .NET framework versioning. I had problems upgrading code from 1.0 to 1.1 and from 1.1 to 2.0 but no problems upgrading to new .NET frameworks since then. I've also had no problems with VS2008 targeting different .NET frameworks. I agree historically it was a problem but M$ has addressed it recently and things seem to work. [EDIT: Reformatted and reworded things a bit]

mattchew 18y ago
If your customers have to download a big new framework before trying out your app, that is one more hurdle you've got to get past in order to sell. Customers who are not computer sophisticated may be scared away and others will consider it too much hassle (frex, if they are on dial-up).
- jmatt 18y ago
  Ya that is a valid point. I've yet to work on a product which targets dial-up or older machines. The product I work on right now is for engineers who design and manufacture things. 97% of them have .NET 2.0+ with XP or Vista. The remaining 3% are Windows 2k. Almost everyone has .NET 2.0 installed but occasionally there is some squirrelly box in a manufacturing plant with no internet connection. For those customers they just use a CD with the application and framework on it. If you are targeting customers using Windows 98 or Windows 2k then you are also limited to .NET 1.1 or 2.0. .NET 3.0 and 3.5+ are XP or Vista only. And as I mentioned before most people in the windows world (at least engineers) are using XP.