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.
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.