留在vb6，还是转到csharp？ [英] stay in vb6, or move to csharp?

问题描述

大家好..


我在一家公司工作，主要通过串口处理硬件设备

通讯端口。到目前为止，大部分软件都是用普通的旧版本编写的。


该公司计划将其应用程序迁移到Windows。

应用程序本身相当小，它们通常只是从设备中提取二进制数据
数据将它们存储在数据库或文件中并将它们显示在
$ b中$ b报告格式。该应用程序正在向外销售，而不是为公司本身开发的b $ b，因此易于分发非常重要（我们

已安装shield express x）。

解决方案

hi

转到c＃。这是我的建议。

问候

ansil


" Elhanan maayan"写道：

大家好。

我在一家公司工作，主要通过串口通讯端口处理硬件设备。到目前为止，大部分软件都是用普通的旧版本编写的。

该公司正计划将其应用程序迁移到Windows。
应用程序本身相当小，它们通常只是从设备中提取二进制数据，将它们存储在数据库或文件中，并以报告格式显示。该应用程序正在向外销售，而不是为公司本身开发，因此易于分发非常重要（我们已经安装了shield express x）。

您是否使用C＃，J＃，S＃，VB.NET，Eiffel.NET，COBOL.NET或其他任何.NET

您可能选择的编译器，它都使用相同的公共语言运行库。

您的语言选择归结为个人偏好和

潜在的，特定语言的任何小优势语法可能

在您的特定环境中为您提供支持。例如，VB.NET稍微有点b / b
更容易做后期绑定; Eiffel在CLR的顶部

上克服了多重继承。依此类推。


显然我们这个特定新闻组的人更喜欢C＃，原因是

好​​，坏，无动于衷。


由于您的遗留代码是用C语言编写的，在我看来，移植到
C＃会是最简单的路线和最浅的学习曲线。对于你的场景，有一些关于VB.NET真的没什么吸引人的东西。


--BOB


" Elhanan maayan" < EM ***** @ msn.com>在消息中写道

news：e7 ************** @ TK2MSFTNGP15.phx.gbl ...

hi all ..

我在一家公司工作，主要通过串口
通讯端口处理硬件设备。到目前为止，大部分软件都是用普通的旧版本编写的。

该公司正计划将其应用程序迁移到Windows。
应用程序本身相当小，它们通常只是从设备中提取二进制数据，将它们存储在数据库或文件中，并以报告格式显示。该应用程序正在向外销售，并且不是为公司本身开发的，因此易于分发非常重要（我们已经安装了shield express x）。

在每个人都告诉你.NET和C＃很好之后我必须带来一些

的缺点。


如果您使用的是.NET，则必须使用您的应用程序将

的.NET框架（~20mb）发布。

此外，每个人都可以简单地反编译（不仅仅是反汇编！）你的程序。

使用混淆器工具会混淆一些标识符，但实际上并不是
摆脱这个问题。

另外，如果你打算让你的程序在另一个操作系统下运行你不能使用.NET（至少如果你使用的是GUI）。


这3个是我可以用.NET看到的大缺点，但有更多的优势，例如一个大类库，完全

互操作性，saf安全，减少调试。


-

cody


免费软件工具，游戏和幽默
http://www.deutronium.de.vu || http://www.deutronium.tk

" Elhanan maayan" < EM ***** @ msn.com> schrieb im Newsbeitrag

新闻：e7 ************** @ TK2MSFTNGP15.phx.gbl ...

hi all ..

我在一家公司工作，主要通过
串口通讯端口处理硬件设备。到目前为止，大部分软件都是用普通的旧版本编写的。

该公司正计划将其应用程序迁移到Windows。
应用程序本身相当小，它们通常只是从设备中提取二进制数据，将它们存储在数据库或文件中，并以报告格式显示。该应用程序正在向外销售，而b $ b不是为公司本身开发的，因此易于分发非常重要（我们已经安装了shield express x）。

hi all..

i work in a company that deals with mainly with hardware devices via serial
comm port. up untill most of the software was writeen in plain old dos c.

that company is planning to move it''s applications to windows. the
applications themselves are rather small, they usually just extract binary
data from devices store them in a database or a file and present them in a
report format. the application are being distributed sold outwards, and not
developed for the company itself, so ease of distribution is important (we
have install shield express x).

解决方案

hi
move to c# .That is my advise.
regards
ansil

"Elhanan maayan" wrote:

hi all..

i work in a company that deals with mainly with hardware devices via serial
comm port. up untill most of the software was writeen in plain old dos c.

that company is planning to move it''s applications to windows. the
applications themselves are rather small, they usually just extract binary
data from devices store them in a database or a file and present them in a
report format. the application are being distributed sold outwards, and not
developed for the company itself, so ease of distribution is important (we
have install shield express x).

Whether you use C#, J#, S#, VB.NET, Eiffel.NET, COBOL.NET, or whatever .NET
compiler you might choose, it all uses the same common language runtime.
Your language choice boils down to a matter of personal preference and
potentially, whatever minor advantages a particular language syntax might
afford you in your particular environment. For example, VB.NET is slightly
easier to do late binding with; Eiffel kludges multiple inheritance on top
of the CLR, and so forth.

Obviously those of us on this particular newsgroup prefer C#, for reasons
good, bad and indifferent.

Since your legacy code is written in C, it would seem to me that porting to
C# would be your easiest route and your shallowest learning curve. There is
really nothing compelling about VB.NET that I can see for your scenario.

--Bob

"Elhanan maayan" <em*****@msn.com> wrote in message
news:e7**************@TK2MSFTNGP15.phx.gbl...

hi all..

i work in a company that deals with mainly with hardware devices via
serial
comm port. up untill most of the software was writeen in plain old dos c.

that company is planning to move it''s applications to windows. the
applications themselves are rather small, they usually just extract binary
data from devices store them in a database or a file and present them in a
report format. the application are being distributed sold outwards, and
not
developed for the company itself, so ease of distribution is important (we
have install shield express x).

After everybody told you that .NET and C# are good I have to come with some
drawbacks.

If you are using .NET, you have to ship the .NET framework (~20mb) along
with your apps.
Also, everybody can simply decompile (not just disassemble!) your programs.
Using obfuscator tools will obfuscate some identifiers but does not really
get rid of this problem.
Additionally, if you plan to make your programs run under another OS you
cannot use .NET (at least if you are using a GUI).

These 3 are the big disadvantages that I can see with .NET, but there are
much more advantages for example a big class library, fully
interoperability, safety, security and less debugging.

--
cody

Freeware Tools, Games and Humour
http://www.deutronium.de.vu || http://www.deutronium.tk
"Elhanan maayan" <em*****@msn.com> schrieb im Newsbeitrag
news:e7**************@TK2MSFTNGP15.phx.gbl...

hi all..

i work in a company that deals with mainly with hardware devices via serial comm port. up untill most of the software was writeen in plain old dos c.

that company is planning to move it''s applications to windows. the
applications themselves are rather small, they usually just extract binary
data from devices store them in a database or a file and present them in a
report format. the application are being distributed sold outwards, and not developed for the company itself, so ease of distribution is important (we
have install shield express x).

这篇关于留在vb6，还是转到csharp？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！