PV功能和VB6移植到C＃ [英] PV Function and Porting VB6 to C#

问题描述

我的工作移植一些经典的VB6代码到C＃和对面的光伏函数的用法绊倒了。

I'm working on porting some classic VB6 code to C# and just stumbled across a usage of the PV function.

我觉得不妥包括对Microsoft.VisualBasic程序集的引用。这是不是就是常见的做，或者我应该探索更多的选项。弹出了我的心下一想法正在探索在此反射功能的光伏

I feels wrong including a reference to the Microsoft.VisualBasic Assembly. Is this something that is commonly done, or should I explore further options. The next idea that pops into my mind is exploring this PV function in Reflector.

推荐答案

使用 Microsoft.VisualBasic程序从C＃和VB.NET已根据这充分讨论问题。该Microsoft.VisualBasic命名空间是完全支持以及将长达四周，.NET是各地。没有理由，以避免它。

The use of Microsoft.VisualBasic from C# and VB.NET has been discussed thoroughly under this question. The Microsoft.VisualBasic namespace is fully supported, and will be around as long as .Net is around. There's no reason to avoid it.

编辑：它告诉，在打字的时候，其他的答案对这个问题是一个的不正确的重新实现的功能，从代码画廊一人带不支持库。来吧家伙，它会采取一个真正的大事微软从VB下降的金融功能。

It's telling that at the time of typing, the other answers for this question are an incorrect reimplementation of the function, and a one-man-band unsupported library from Code Galleries. Come on guys, it would take a real major event for Microsoft to drop the financial functions from VB.

这是对于 Microsoft.VisualBasic.Compatibility ，这完全是由VB6升级向导使用修改的已经被标记在.NET 4中废弃的（我的预言应验了），并且不应该被用于新的发展。会有除去这个引用一些优势​​，但我个人很可能试图实现完全的工作端口第一referencing.Net 3.5。

It's a different story for Microsoft.VisualBasic.Compatibility, which is exclusively for use by the VB6 upgrade wizard, EDIT has now been marked obsolete in .Net 4 (my prediction came true), and should not be used for new development. There would be some advantages in removing references to this, but personally I'd probably try to achieve a fully working port first referencing.Net 3.5.

这篇关于PV功能和VB6移植到C＃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！