将 C# 程序迁移到其他语言
我目前负责开发用 Microsoft .NET C# 创建的程序的第二个版本。 我没有进行任何实际的编程，但我正在为程序员编写规范。 我想将其从 .NET 代码库中删除，但自从 Joel 在他的 博客 永远不要重写代码，而且他确实提供了很好的推理，我倾向于仔细思考。
所以我的问题是，
（1）有没有简单的过渡方法？ （.NET C# 等语言）
(2) 你会把它从 .NET 中删除吗？
(3) 如果是的话，您会使用什么语言？
我想将其从 .NET 中删除的原因是，就我对 .NET 的理解而言，它必须安装在客户端上。 当有更好的方法时，我不想给我的客户带来不便。
I am currently in charge of the development of the second version of program that was created in Microsoft .NET C#. I'm not doing any actual programming, but I am writing the specification for the programmer. I'd like to take it off the .NET codebase, but since Joel said on his blog never to rewrite code, and he does provide good reasoning, I'm inclined to think carefully.
So my question is,
(1) Are there any easy ways to transition? (Languages like .NET C#)
(2) Would you take it off .NET?
(3) If so, what language would you use?
The reason I want to take it off of .NET is as far as my understanding of .NET, it has to be installed on the client. I'd prefer not to inconvenience my customers when there's a better way.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（15）
这听起来很粗鲁，我冒着被否决的风险，但请原谅我，我会说实话......你是说，“[你]负责开发第二个版本的程序，该程序是在Microsoft .NET C# ...不进行任何实际编程...[希望]将其从 .NET 代码库中删除”。 你听到自己的声音了吗？ 显然，您没有任何知识或经验来做出该决定，问题 1 和 3 进一步证明了这一点。没有“简单的语言”——这意味着什么？ 强大的语言“容易”吗？ 弱语言“容易”吗？ 如何能够轻松过渡到不同的事物？ 即使您有一些东西可以自动翻译代码，运行时、平台和库的差异也使得移植任何重要的应用程序都绝非易事。 这需要工作和知识。 对于拥有大量时间的人来说也许很容易，但对于大多数有截止日期和现实需要面对的人来说却并非如此。
This is going to sound rude and I risk being downvoted, but forgive me, I'm going to be honest ... you are saying, "[you are] in charge of the development of the second version of program that was created in Microsoft .NET C# ... not doing any actual programming ... [would] like to take it off the .NET codebase". Are you hearing yourself? You clearly don't have any knowledge or experience to make that decision, further evidenced by questions 1 and 3. There are no "easy languages" - what does that even mean? Is a powerful language "easy"? Is a weak language "easy"? How could there be an easy transition to anything different? Even if you have something to automatically translate the code, differences in the runtimes and platforms and libraries make porting any non-trivial application far from easy. It takes work and knowledge. Perhaps easy for someone with a lot of time, but not for most people with deadlines and reality to face.
除非您要放弃 C# 作为从 C# 到另一种语言的某种企业范围转变的一部分，或者除非存在 C#/.NET 无法满足的某种有效技术要求，我不会离开现有的代码库。
您陈述了客户需要 .NET 的原因。 您的程序是客户端/服务器，还是 Web 应用程序？ 如果它是基于网络的，那么你就错了，客户端不需要.NET，只需要浏览器。
如果程序是客户端/服务器并且已经用 C# 编写，那么您迁移到的任何语言也可能需要某种形式的运行时安装。 从 XP 开始，.NET 随 Windows 的每个新安装和服务包一起提供。
当然，除非您试图针对 OSX 和 Linux 用户，在这种情况下，我会考虑在做出放弃代码库的任何决定之前认真检查这些市场的价值。 Java 可能会更好地帮助您——但是您可以使用 Mono 平台做很多事情，因此即使您的目标平台是这些平台，您也可以保存 C# 代码。
编辑：
不幸的是，你不走运。 最接近 C# 的语言是 Java，但两者之间的差异非常显着，您需要进行完全重写； 端口根本无法工作。 您的 C# 代码不太可能不使用委托和事件——它们无处不在——并且 Java 中没有类似的构造。 WinForms GUI 框架（我猜是 WinForms）与 Swing 非常不同，以至于没有一个构造可以轻松移植； 并且里面到处都是事件和代表。
您正在考虑至少与最初的工作一样多的切换平台的工作，甚至可能更多。 另外，转向 Java 违反了您想要从 C# 切换的原因：Java 需要在客户端安装运行时。
正如我之前提到的，在做出决定之前，请仔细考虑一下您可能从切换平台中获得的真正好处。
Unless you are moving away from C# as part of some sort of enterprise-wide shift from C# to another language, or unless there is some sort of valid technical requirement that C#/.NET can't satisfy, I would not move from the existing code base.
You state your reason as that the client needs .NET. Is your program client/server, or is it a web application? If it's web based, then you are incorrect, the client does not need .NET, only a browser.
If the program is client/server and is already written in C#, then any language you move to is also likely to require some form of runtime installation. .NET comes with every new install and service pack of Windows from XP on.
Unless of course you're trying to target OSX and Linux users, in which case I would consider a serious examination into the value of those markets before you make any decisions to abandon your codebase. Java might help you better there -- but you can do a hell of a lot with the Mono platform, so you might be able to save your C# code even if you target those platforms.
Edit:
Unfortunately, you are out of luck. The closest language to C# is Java, but the differences between the two are significant enough that you'll need to do a complete rewrite; a port simply will not work. It's highly unlikely that the C# code you have does not use delegates and events -- they're omnipresent -- and there is no similar construct in Java. The WinForms GUI framework (I'm guessing WinForms) is so different from Swing that none of the constructs will easily port; and it's littered with events and delegates.
You are looking at at least as much effort to switch platforms as there was for the initial effort, possibly more. Plus going to Java violates the reason you want to switch from C#: Java requires a runtime installed on the client.
As I mentioned before, look long and hard at the real benefits you might get from switching platforms before you make this decision.
我真的无法理解为什么您想要放弃 C# 和 .NET，唯一的原因是您不想要求客户安装 .NET 框架而给他们带来“不便”。
其一，.NET 如今已包含在 Windows 中。 在 XP（当前服务包）中，您可以获得 .NET 2.0。 在 Vista 中，您将获得 .NET 3.0。 假设您实际上没有使用任何 .NET 3.5 功能，并且不需要 C# 3.0 中的任何功能，那么“给客户带来不便”的说法就毫无意义。 他们不需要下载任何东西或安装任何额外的东西......它已经在那里了。
如果您确实需要 .NET 3.5 和/或 C# 3.0，那么为您的客户创建一个预打包的安装程序来为他们处理这一切就非常容易了。 对客户来说并没有任何真正的“不便”，因为他们无论如何都必须安装您的程序。 一次安装可以在一个无缝、透明的安装过程中处理您的程序及其所有依赖项。 如果您希望客户更轻松，您可以选择使用 .NET、C# 和 Visual Studio 进行一次单击部署。 这将为您的客户创建一个简单的网站，让他们轻松快速地下载和安装您的应用程序，并在将来发布更新时进行更新。 这种类型的部署还负责确保所有依赖项都下载并安装到客户端系统，这只需要完成一次（所有后续更新只需要下载和安装更改的程序集的最新版本。）
正如其他人提到的、C# 和 .NET 可以提供很多东西。 Microsoft 创建了一个广泛的 .NET 平台开发生态系统，提供大量资源、工具、文档和社区帮助。 C# 是一种非常干净、现代、具有前瞻性的语言，它提供了大量工具来帮助您和您的开发人员尽可能快速、简单且高效地解决问题。 转向 C++ 不仅意味着您会失去这些有用的进步，而且还会继承手动内存管理的噩梦。 迁移到 Java 意味着您会失去这些有用的进步，但通常也不会真正获得有用的东西。 您可以迁移到其他 .NET 语言，但是您并没有解决您提到的唯一问题：您的客户端对 .NET 框架的依赖。
如果您已经有了一个用 C# 开发的系统，我会说不要改变任何东西。 您将失去很多，并且不会真正获得任何对您的客户产生重大影响的东西。 从长远来看，任何变化都很可能会对您的公司和开发人员产生更重大的影响。 您将花费重写或转换代码的成本，培训开发人员使用新语言和可能的新开发平台的成本，查找和修复当前代码库中很可能已经修复的错误的成本，以及这样的例子不胜枚举...
在您认为 .NET 对您的客户来说太不方便之前，您需要了解有关 .NET 所提供的功能的更多信息。 在决定进行如此剧烈且昂贵的改变之前，您需要确保这确实会给您的客户带来不便。
I can't really fathom why you would want to move off of C# and .NET for the sole reason that you don't want to "inconvenience" your customer by requiring they install the .NET framework.
For one, .NET is included with Windows these days. In XP (current service packs), you get .NET 2.0. In Vista, you get .NET 3.0. Assuming you don't actually use any .NET 3.5 capabilities, and don't need any features from C# 3.0, then the "inconvenience the customer" argument is pretty moot. They won't need to download anything or install anything extra...its already there.
In the event that you actually DO need .NET 3.5 and/or C# 3.0, then it is beyond easy to create a pre-packaged installer for your customer(s) that takes care of it all for them. There isn't any real "inconvenience" to the customer, because they have to install your program anyway. A single install can take care of both your program and all of its dependencies in a single, seamless, transparent installation process. If you want an even easier time for your customers, you have the option of click-once deployment with .NET, C#, and Visual Studio. This will create a simple site for your customers that will easily and quickly allow them to download and install your application, as well as update it when future updates are published. This type of deployment also takes care of ensuring any dependencies are downloaded and installed to the clients system, which only needs to be done once (all subsequent updates only require the latest version of changed assemblies to be downloaded and installed.)
As others have mentioned, C# and .NET have a lot to offer. Microsoft has creates an extensive ecosystem for development on the .NET platform, with a tremendous amount of resources, tooling, documentation, and community help. C# is a very clean, modern, forward-looking language that offers a lot of tools to help you and your developers solve problems as quickly, simply, and efficiently as possible. Moving to C++ means not only do you lose these useful advancements, but you inherit the nightmare of manual memory management. Moving to Java means you lose these useful advancements, but generally don't really gain useful either. You could move to other .NET languages, but then you aren't solving the sole problem you mentioned: your clients dependency on the .NET framework.
If you already have a system in place that is developed with C#, I would say don't change a thing. You will be loosing a lot, and won't really gain anything that is going to significantly impact your customers. In the long run, any change is most likely going to have a much more significant impact on your company and your developers. You will have cost involved in rewriting or converting code, cost involved to train your developers on a new language and possibly a new development platform, cost involved to find and fix bugs that have quite probably already been fixed in your current code base, and the list goes on...
You need to learn more about what .NET has to offer before you decide that it is too inconvenient for your customers. And you need to make sure that it really IS an inconvenience for your customers before deciding to make such a drastic and expensive change.
您认为其他语言比 C# 更好的原因是什么？ .NET 出了什么问题？ 如果你有正当理由阻碍你公司的使命，那么你应该考虑重写它。
然而，我确实认为这样做有任何意义。 C# 非常简单明了，最新版本的运行时相当稳定。 我仍然不会用它构建操作系统，但对于最终用户应用程序，它是我的首选语言。
用 C++ 重写它只会成为内存/资源管理的噩梦，而转换到 Java 则是一种横向移动，没有多大意义。
如果您详细说明该应用程序是什么、客户端、服务器等、它的用途等，我们也许可以更具体。
但请记住，坦斯塔夫。
编辑：
我不会太担心需要在客户端上安装运行时。 假设您的所有用户都是 Windows 用户，Vista 和 Win7 都默认安装了最新版本的运行时。 随着越来越多的应用程序构建在运行时上，越来越多的用户已经将其用于其他应用程序，并且您始终可以使用您的应用程序重新发布运行时。
What are the reasons you think something else would be better than C#? What's wrong with .NET? If you have valid reasons that are obstructing your companies mission, then you should consider re-writing it.
However, I do see any point in doing it just to do it. C# is pretty simple and straightforward, and recent versions of the runtime see fairly stable. I still wouldn't build an OS in it, but for end-user applications it's my go-to language.
Rewriting it in C++ is just going to be a memory/resource management nightmare, and transitioning to Java is a sideways move that doesn't make a whole lot of sense.
If you give details of what the app is, client, server, etc, what it does, etc, we may be able to be more specific.
But remember, TANSTAAFL.
Edit:
I wouldn't worry too much about requiring the runtime to be installed on the client. Assuming all your users are Windows users, both Vista and Win7 both have very recent versions of the runtime already installed by default. As more and more apps are built on the runtime, more and more users will already have it for some other app, and you can always just redist the runtime with your app.
(1) 有没有简单的过渡方法？ （像 .NET C# 这样的语言）
不
(2) 你会把它从 .NET 中删除吗？
没有一个非常令人信服的理由（不会给你带来不便）客户不是吗！）
(3) 如果是这样，有没有简单的语言？
Java 将是最接近 C# 的类比，你会失去更多的东西。你仍然会给你的客户带来不便
我想将其从.NET中删除的原因是，据我对.NET的理解，它必须安装在客户端上。 当有更好的方法时，我不想给我的客户带来不便。
正如其他人提到的，这并不是您所认为的不便，如果这是您的唯一原因，您很可能只是在浪费时间、资源和金钱。 简而言之，如果它是付费的并且有效，请不要再关注它。
(1) Are there any easy ways to transition? (Languages like .NET C#)
NO
(2) Would you take it off .NET?
Not without a Very compelling reason (not inconveniencing your customers isn't it!)
(3) If so, are there any easy languages?
Java would be the closest analogue to C# and you would lose more than you gain plus you still have to inconvenience your customers
The reason I want to take it off of .NET is as far as my understanding of .NET, it has to be installed on the client. I'd prefer not to inconvenience my customers when there's a better way.
As others have mentioned this is not the inconvenience you seem to think it is and if its your only reason you are most likely just wasting time, resources and money. In short if its paid for and it works keep your mitts off it.
不会有从 C# 到 .NET 以外的内容的自动转换。
您可以轻松地将其转换为 Boo 或 VB.NET 或其他一些 .NET 语言，但例如，如果您要转换为 C++（非 CLI），则库（.NET 框架）将不可用。
这会是最头疼的事情。
There will be no automatic translation from C# to something off .NET.
You could easily translate it to Boo or VB.NET or some other .NET language, but the libraries (the .NET framework) will not be available if you were to translate to C++ (non-CLI), for example.
This would cause the biggest headache.
从 C# 唯一简单的转换是将其转换为另一种 .NET 语言。 除此之外，您无论如何都会考虑重写应用程序，因为所有语法和库都会发生变化。
我可以问为什么你想放弃 C# 吗？ 本着您提供的 Joel on Software 链接的精神，我希望您能看到坚持使用当前正在运行的代码库（无论其价值）的好处。 是否有非常令人信服的理由让该项目放弃 .NET？
The only easy transition from C# would be to translate it to another .NET language. Other than that you are looking at rewriting the application anyways as all the syntax and libraries will change.
May I ask why you want to move away from C#? In the spirit of the Joel on Software link you provided I would hope that you would see the benefit of sticking with the codebase that is currently working (for what it's worth). Is there a terribly compelling reason to move off of .NET for this project?
从 C# 迁移到 Java 可能是最简单的，因为它们是非常相似的语言。 但是，您仍然需要检查所有代码并修改很多内容才能使其成为有效代码。 如果您使用 C# 的一些最新功能（例如 LINQ），则会更加困难，因为 Java 没有类似的功能。
您有什么充分的理由将其从 .NET 中删除吗？ 如果没有，就不要。 但如果您确实想在某个时候将其从 .NET 中删除，那么越早越好（在代码增长太多之前）。
Moving from C# to Java would probably be easiest as they are quite similar languages. However, you'll still have to go through all the code and modify a lot of stuff to make it valid code. It will be more difficult if you're using some of the latest features of C#, like LINQ, as Java has no similar functionality.
Do you have any good reason for taking it off .NET? If not, don't. But if you do want to take it off .NET sometime, sooner is better (before the code grows too much).
我不明白为什么一家公司会决定从 .NET 等稳定的代码库迁移到另一个。 如果您考虑其他平台，例如从操作系统应用程序迁移到 Web 应用程序，那么 Ruby on Rails 可能会不错（它的 MVC 平台很强大）。 但到另一个操作系统应用程序呢？ 事情会变得艰难。
I don't understand why a company would decide to move from a stable code base such as .NET to another. If your thinking of other platforms, such as moving from an OS app to a web app, Ruby on Rails might fair well (its MVC platform is strong). But to another OS app? The going will get tough.
(1) 有没有简单的方法可以过渡？ （像 .NET C# 这样的语言）
如果您所说的“简单”是指相似，那么在语法上 Java 是相似的，但将 .NET 框架类与 Java 库相匹配并非易事。
(2) 你会把它从.NET 中删除吗？
否。
（3）如果有，有没有简单的语言？
请参阅对 (1)
几个问题的回答，以帮助我进一步了解您为什么要这样做；
这对您的客户有何不便？ （仅安装 .NET 框架？）
如果您谈论的是客户端应用程序，那么您还需要在客户端上安装您的应用程序，我不明白这会带来更多不便。
从 你的其他类似问题你建议你想用 C++ 重写，这将如何改变不便程度？
您想要瞄准非 Windows 用户群吗？
(1) Are there any easy ways to transition? (Languages like .NET C#)
If by easy you mean similar, then in syntax Java is similar but matching .NET framework classes to Java Library would be non trivial.
(2) Would you take it off .NET?
No.
(3) If so, are there any easy languages?
See Answer to (1)
A few questions to help me understand further why you would want to do this;
How is this an inconvenience to your customer? (just the .NET framework install?)
If you are talking about a client app then you need to install your app on the client as well, I dont understand this being more of an inconvenience.
From your other similar question you suggested you want to rewrite in C++, How would this change the inconvenience level?
Are you wanting to target a non-Windows user base?
在某些情况下，从 C# 迁移到 C++ 可能是有意义的，这样您就可以获得非托管代码的强大功能（即性能）。 但很可能这不值得付出努力。
In some cases, it might make sense to move from C# to C++, so you gain the power of unmanaged code (i.e. performance). But chances are it isn't worth the effort.
正如许多问题的答案一样，这取决于情况。 在下面的回答中，我假设您正在谈论 Windows 窗体应用程序，因为当然，如果您正在谈论基于 Web 的产品，所有这些都不是问题。
听起来您（几乎）已经决定“摆脱”.NET。 我强烈建议您仔细考虑该决定。 尤其是要看看原因。 您已经说过原因是您不希望 .NET 运行时依赖项引起问题。 正如一些人提出的那样，对此的反驳是，没有运行时标准的 Windows 平台正在变得稀缺。 尽管如此，对于一个不依赖 50Mb 下载的精简程序来说，还是有一些令人满意的地方。
但最终，您所说的理由是否有效取决于：
毕竟，如果事实证明 99% 的客户都在现代平台上，那么正如其他人指出的那样，这就不再是问题了。
如果在分析上述内容后证明您的推理是有效的，那么您应该将重写产品的成本与重写导致的客户满意度/产品销售的预测改进进行比较。 为了证明重写的合理性，后者必须是绝对惊人的。 当然，我这么说是在不了解所有事情的情况下，包括：
就通用编程语言/平台而言，现在几乎找不到比 C#/.NET 更好的了，因此假设经过所有尽职调查后，您仍然想“移动”，那么您会被迫选择不需要运行时的东西 - 唯一可以想到的选择是 C/C++ 或 Delphi。
As is the answer to many questions, it depends. In my answer below, I've assumed that you're talking about a Windows Forms application, since, of course, all of this would be a non-issue if you were talking about a web-based product.
It sounds like you've (almost) made the decision to "take it off" .NET. I would suggest strongly that you think very carefully about that decision. In particular, look at the reasons. You've stated that the reason is that you don't want the .NET runtime dependency to cause issues. The rebuttle to this, as presented by a few people is that Windows platforms without the runtime standard are becoming scarce. Never-the-less, there's something satisfying about a lean-and-mean program that doesn't have a dependency on a 50Mb download.
Ultimately though, whether or not what you've stated as the reason is valid depends on:
After all, if it turns out that 99% of your clients are on a modern platform, then as others have pointed out, this becomes a non-issue.
If it turns out, after analysing the above that your reasoning is valid, then you should compare the cost of rewriting the product to the forecast improvement in customer satisfaction/product sales as a result of the rewrite. To justify a rewrite, the latter would have to be absolutely phenomenal. Of course, I say that, not knowing all kinds of things, including:
As far as a general programming language/platform is concerned, you pretty much can't get any better than C#/.NET these days, so assuming that after all the due-diligence, you still want to "move" then you'd be forced to choose something that doesn't require a runtime - the only conceivable option would be C/C++ or Delphi.
答案很简单：将您的应用程序移至网络。
所以客户端只需要浏览器。
Answer is easy: move your application to web.
So client will need only browser.
到目前为止，大多数回复都回答了 C# 与“其他东西”的具体问题，但我将回答您需要问的问题：
很快，什么不该做：指定实现细节，例如使用什么语言。
该怎么做：编写用户故事或用例来指定您想要什么以及为什么。 例如：
作为用户，我希望能够通过从互联网下载单个文件来安装和运行该软件，这样我就不会因为必须查找和安装其他软件而感到不便。
您可能需要用指标来支持这一点：
作为产品经理，我希望能够查看给定时间段内的软件下载数量以及同一时间段内的软件激活数量，以便我可以确定我们有多少潜在客户成功安装和运行该软件。
告诉您的团队您想要什么以及为什么，他们将为您提供。
Most responses so far answer the specific question of C# vs "something else", but I'll answer the question you need to ask:
Quickly, what not to do: specify implementation details, such as what language to use.
What to do: Write User Stories or Use Cases that specify what you want and why. For example:
As a User, I want to be able to install and run the software by downloading a single file from the internet, so that I am not inconvenienced by having to find and install other software.
And you might want to back this up with metrics:
As the Product Manager, I want to be able to view the number of software downloads for a given time period and the number of software activations in that same period, so that I can determine how many of our potential customers successfully manage to install and run the software.
Tell your team what you want and why, and they will deliver it for you.
.NET 框架是 Windows Update 的一部分，因此可能每个客户端的计算机上都有它。 或者他们正在运行 Linux / Mac OS，但我不认为是这种情况，因为您的产品版本 1 已经在 .NET 中运行。
和。 几乎所有其他主流语言都需要安装单独的运行时（java、PHP 等）......
所以我没有看到过渡的有效理由。
The .NET framework is part of Windows Update, so probably every client has it on his or her machine. Or they're running Linux / Mac OS, but i don;t think that's the case because the version 1 of your product was already running in .NET.
And. almost every other mainstream language needs a separate runtime installed (java, PHP, etc.)....
So I don't see a valid reason for transitioning.