我们的客户使用我们软件的 vb6 版本。
我们正在将它们升级为用 C# 编写的 .NET 应用程序...
使用 .net 2.0 的体积是否比 .net 3.5 少?
我对体积更小的定义是:更小的尺寸、更短的安装时间等。
无论如何,他们中的大多数可能已经有了 2.0。
我只是问,因为我想在 3.5 中利用 LINQ。
我们的客户使用我们软件的 vb6 版本。
我们正在将它们升级为用 C# 编写的 .NET 应用程序...
使用 .net 2.0 的体积是否比 .net 3.5 少?
我对体积更小的定义是:更小的尺寸、更短的安装时间等。
无论如何,他们中的大多数可能已经有了 2.0。
我只是问,因为我想在 3.5 中利用 LINQ。
For taking advantage of LINQ, you need 3.5 (unless you want to use LINQBridge with 2.0).
For a smaller installer, .Net 3.5 Sp1 has a new feature called "Client Profile".
The .NET Framework Client Profile setup contains just those assemblies and files in the .NET Framework that are typically used for client application scenarios. For example: it includes Windows Forms, WPF, and WCF. It does not include ASP.NET and those libraries and components used primarily for server scenarios. We expect this setup package to be about 26MB in size, and it can be downloaded and installed much quicker than the full .NET Framework setup package.
安装 .NET 3.5 只是为了节省几 Mb 真的比使用 LINQ 和其他 .NET 3.5 功能大幅提高生产力更重要吗?
为什么要在技术上落后?
.Net 3.5 运行时约为 50Mb。2.0 运行时约为 23Mb。
但是,如果您控制部署或安装,那真的不应该成为问题。对于“客户”与“客户”而言尤其如此,客户一词涉及持续的个人关系。如果有的话,给他们寄一张CD。那么任何低于 700Mb 的东西都是一样的。
Check out LINQBridge: http://www.albahari.com/nutshell/linqbridge.aspx
Adding LINQ support to .net 2 (.net 3.5 still uses CLR 2.0).
.NET 3.5 是 .NET 2.0 + 更多的库和扩展,所以是的,安装更大。然而,在我看来,额外的体积非常值得,因为它给了你额外的东西。
If it's a VB6 app, you should check which Windows versions the app is currently used on, and select the .Net version accordingly. AFAIK 3.5 does not run on W2K.
如果您想利用 LINQ,请选择 3.5!我发现自己使用它时没有更多的“大容量”,但除非你想使用 LINQ,否则两者都可以。
Keep in mind that certain OSes (Windows 2000 Server) won't let you install .NET 3.0 or 3.5, so you may have to stick with 2.0 for that reason.
我建议你直接使用 Visual Studio 2008 和 .net 3.5 sp1,2.0 是 3.5 的基础,你可以轻松地开始使用 2.0,然后开始使用 3.5 的功能。
此外,3.5 SP1 还对 2.0 框架进行了一些调整,这很不错。
I suggest you to go directly to 3.5 because you will be less far away (in the future ... in 3-5 years) to change to other version of framework. If in 5 year .Net is at version 5, the jump will be smaller to do. So, VB6 to 3.5 is what I suggest you.
The size of the framework is not very high, less than 60 megs... not a big deal now I think.
Also note, depending were you install the .NET framework it might be irrelevant how much extra bulk there is. The .NET Framework installs are relatively small in modern terms.
As for LINQ, it will save you a lot of time and effort, and offers a quick way to get at data. However it also depends on the clients the application will be distributed out to.
I'd say at that, go with 3.5 unless there is another major roadblock on the clients for whatever reason.
As others have pointed out, the .NET 3.5 install is longer and larger than .NET 2.0. Keep in mind that .NET 3.0 and .NET 3.5 are both extensions on top of the .NET 2.0 CLR.
I would still say upgrade from VB6 directly to .NET 3.5 (actually .NET 3.5 SP1) and VS2008, as long as your client operating systems support that version of the Framework (otherwise you will need to choose the lowest common Framework version, which very well may be .NET 2.0). You will save yourself a lot of time/effort in the long run.