.NET开源和运行平台的选择运行平台、开源、NET

2023-09-03 07:37:20 作者:上瘾

我们已被要求寻找到一个大项目完全开源的解决方案,他们希望这个项目尽可能接近100%开源的可能,主要是因为它是一个社区项目,可能会有很少的钱可用除了主机的运行的未来。使用OS软件节省了许可证费用,服务器将在内部由现有的IT系统的团队进行管理。

We have been asked to look into a fully open source solution for a big project, they want the project be as near to 100% Open Source as possible, mainly because as it's a community project there may be very little money available in the future except for the running of a host. Using OS software saves on licence costs as the server will be managed in house by the existing IT systems team.

供应商之一被提出.NET作为系统的组成,这是很好的我明白,.NET应用程序可以很恰当地在开源许可证,如GPL等。

One of the suppliers is proposing .net as the makeup of system, which is fine I understand that .net applications can quite rightly be released under open source licences such as the GPL etc.

不过因为我不是一个.NET开发人员,我有点困惑,当涉及到什么权力.NET。它必须是一个Windows服务器,这当然会导致更高的服务器成本和领带,以微软产品,或者是它可以运行在开源的服务器,如Linux等。

However as I'm not a .net developer, I'm a little confused when it comes to what powers the .net. Does it HAVE to be a windows server, which of course leads to higher server costs and a tie in to MS products, or is it possible to run .net applications on open source servers such as Linux etc.

请不要把它变成一个ms和Linux的论证和利益,或使用一个或另一个。我们只是想确保,当涉及到使用.NET和刚刚开源如何能成为我们完全知情。我希望能有我的眼睛睁开了。

Please don't turn this into a MS Vs Linux argument and the benefits or using one or the other. We are just wanting to make sure we are fully informed when it comes to using .net and just how open source it can be. I'm hoping to have my eyes opened.

推荐答案

至于其他人已经,有单声道,但由于它的不成熟,它不仅是复杂的多层面,它是风​​险的额外级别。此外,供应商提供一个.NET解决方案是极不可能为想支持他们的阿帕奇+单应用程序。

As others have already, there is Mono, but given it's immaturity, it is not only an extra level of complexity, it is an extra level of risk. Furthermore, the supplier offering a .NET solution is highly unlikely to want to support their application on Apaches + Mono.

所以,要么选择用于OSS(阿帕奇+ PHP / Perl的/ Python的/红宝石等)或选择IIS + .NET。是绝对没有错的选择.NET解决方案,如果它是适合这份工作的最佳应用,但不要试图鞋的基本设计为一个平台的应用程序到另一个。

So either opt for OSS (Apache + PHP/Perl/Python/Ruby etc) or choose IIS + .NET. There is absolutely nothing wrong with choosing the .NET solution, if it's the best application for the job, but don't try to shoe an application essentially designed for one platform onto another.