.NET 3.5 SP1 as a requirement (or should I try installing 3.5 without SP1)?

We are creating a custom WPF control targeting .NET 3.5. It is very difficult to use the StringFormat property in bindings, but this was only added in SP1.

So the question is: how many potential users will we cut off by changing the requirement from .NET 3.5 to .NET 3.5 SP1? Or is it safe to assume that more or less every user who has .NET 3.5 already has SP1 (or will have it in the not too distant future)?

Your feedback is much appreciated. Thanks.

+3
source share
3 answers

SP1 - , .., , .

- , ( ).

, - ( ), . SP1, , .

, ? 30 ... , - ( , , ...).

: ? ? , , "" ; -p

+3

WPF? SP1 ?

SP1 ( ) .

+1

.net 3.5 sp1 Windows Updates .net, , , , .

, .net 3.5 .

I personally started selling the WPF application almost at the same moment. 3.0 was released, everyone always talks about a big load, but I never had a complaint about it from a real potential user, only from other developers or IT specialists in the forums. (if your target audience has a lot of people who are still using dial-up, then you have different problems and maybe not .net 3.5)

0
source

Source: https://habr.com/ru/post/1702905/


All Articles