简体   繁体   English

.NET 3.5 SP1作为一项要求(或者我应该尝试3.5 w / o SP1)?

[英].NET 3.5 SP1 as a requirement (or should I try for 3.5 w/o SP1)?

We're creating a WPF custom control targeted at .NET 3.5. 我们正在创建一个针对.NET 3.5的WPF自定义控件。 It is very compelling to use StringFormat property in bindings, but this was only added in SP1. 在绑定中使用StringFormat属性非常引人注目,但这仅在SP1中添加。

So the question is: how many potential users will we be cutting off by changing the requirement from .NET 3.5 to .NET 3.5 SP1? 所以问题是:通过将需求从.NET 3.5更改为.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 so distant future)? 或者可以安全地假设每个拥有.NET 3.5的用户已经拥有SP1(或将在不久的将来拥有它)?

Your opinions are highly appreciated. 非常感谢您的意见。 Thanks. 谢谢。

For large corporations, SP1 might still be slow to deploy to desktops - simply that it is a fair amount of testing etc, and unless you've got a good reason to do it, you'd be tempted not to. 对于大型企业来说,SP1可能仍然很慢部署到桌面 - 只是它是相当多的测试等,除非你有充分的理由去做,你会被诱惑不去。

And for individuals - it can be a big download unless you've got a fat pipe (which not everyone does). 对于个人而言 - 除非你有一个胖管(不是每个人都这样做),否则它可能是一个很大的下载。

For example, at my work we've deployed to the web-servers (since they need it), but not to user desktops. 例如,在我的工作中,我们已经部署到Web服务器(因为他们需要它),但不是部署到用户桌面。 If I had a need to push SP1 I would, but I don't see much point until then. 如果我需要推SP1那么,但直到那时我才意见到。

You might also want to see if your code would run on Client Profile? 您可能还想查看您的代码是否可以在客户端配置文件上运行? This is then only a <30MB install away... although I've never actually seen anyone use Client Profile in anger (if you're going to have to do a deployment, heck: push the big one...). 这只是一个<30MB的安装...虽然我从来没有真正看到任何人愤怒地使用客户端配置文件(如果你将不得不进行部署,那么:推动大的......)。

So it really depends: who are the users of this app? 所以它真的取决于:谁是这个应用程序的用户? Can you strong-arm them to upgrade? 你可以强力武装升级吗? Or at least "encourage" them ;-p 或者至少“鼓励”他们;-p

How are you deploying your WPF application? 你是如何部署WPF应用程序的? If by installer then can you not just add SP1 as a prerequisite and let the installer sort the rest out? 如果安装程序那么您是否可以不仅仅添加SP1作为先决条件并让安装程序对其余部分进行排序?

You should be able to bundle SP1 with your installer (if you're sending out traditional media), or allow it to be downloaded. 您应该能够将SP1与安装程序捆绑在一起(如果您要发送传统媒体),或允许下载它。

.net 3.5 sp1 will be on Windows Updates for everyone with .net installed, so unless it's a big company with very slow deployment strategies I would say it shouldn't be a problem. 对于安装了.net的每个人来说,.net 3.5 sp1将在Windows更新中,所以除非它是一个部署策略非常慢的大公司,否则我认为应该不是问题。

Also, in such a comapny with those deployment policies I wouldn't expect to find .net 3.5 at all. 此外,在这样的comapny与那些部署策略,我不希望找到.net 3.5。

I personally started selling a WPF application almost the moment .net 3.0 was released, everyone is always talking about the big download but I've never got a complaint about it from a real potential user, only from other developers or IT people in forums. 我个人开始销售WPF应用程序几乎就是.net 3.0发布时,每个人都在谈论大的下载,但我从来没有从真正的潜在用户那里得到关于它的抱怨,只有来自其他开发人员或论坛中的IT人员。 (if your target audience has a lot of people still using dial-up then you have different problems, and probably no .net 3.5 either) (如果您的目标受众有很多人仍然使用拨号,那么您有不同的问题,也可能没有.net 3.5)

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM