为什么我们需要德尔福棱镜
什么情况需要使用Delphi Prism代替Visual studio？ 我是一名 Delphi 程序员，喜欢 Object Pascal，但是 Delphi Prism 有什么是其他人没有的呢？
What is the need to use Delphi Prism instead of Visual studio?
I am a Delphi programmer and like Object Pascal but what is it that Delphi Prism has that others do not have?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
“Delphi Prism 而不是 Visual Studio”是什么意思？！ Delphi Prism 是 .NET 平台中的 pascal 风格。 Visual Studio 是一个 IDE。 Delphi Prism 使用 Visual Studio 作为其 IDE。因此，当您在 Delphi Prism 中编码或调试 Prism 代码时，您是在 Visual Studio 中进行的，就像使用 C# 或 VB.NET 一样。
.NET 应该支持多种编程语言，并为所有针对它的语言提供通用类型和库。 Delphi Prism 只是另一种 .NET 语言。它可以访问 .NET 为语言提供的所有内容。它还具有一些独特的语言功能（请参阅 PRUZ 帖子）。
因此，当您想要在 .NET 平台的 Pascal 中进行编码，或者您确实需要在 .NET 应用程序中使用它的任何独特语言功能时，您可以使用 Delphi Prism。
当然，与第三方语言提供商相比，微软自己的语言（C#、VB.NET、F#）在 .NET 方面几乎没有优势：
编写有关 MS 语言的文章，或使用 C# 或 VB.NET 示例代码编写有关 .NET 的文章（最近 Delphi
Prism添加了一个工具来自动
将 C# 代码片段转换为 Delphi
棱镜代码）。
首先可供微软自己使用
首先是语言，然后是其他语言
语言，所以如果你真的需要
新的 .NET 功能，您可能需要
等待几个月才能将其放入您的
最喜欢的语言。
.NET 紧凑型表单设计器
仅提供 C# 版本
和VB.NET。
What do you mean by "Delphi Prism instead of Visual Studio"?! Delphi Prism is a pascal-flavor in .NET platform. Visual Studio is an IDE. Delphi Prism uses Visual Studio as its IDE. So when you code in Delphi Prism or debug your prism codes, you are doing it in Visual Studio, just as doing with C# or VB.NET.
.NET is supposed to support multiple programming languages and providing common types and libraries to all languages targeting it. Delphi Prism is just another .NET language. It has access to all the stuff that .NET provides to languages. It also has some distinct language features (refer to PRUZ post).
So you can use Delphi Prism when you want to code in Pascal for .NET platform, or if you really need any of its distinct language features in your .NET applications.
Of course Microsoft's own languages (C#, VB.NET, F#) have little edge in .NET over third-party language providers:
written about MS languages, or written about .NET with C# or VB.NET sample codes (recently Delphi
Prism added a tool to automatically
convert C# code snippet to Delphi
Prism code).
available first to Microsoft's own
languages first, and then to other
languages, so if you need a really
new .NET feature, you might have to
wait a few months to have it in your
favorite language.
form designer for .NET compact
edition are only provided for C#
and VB.NET.
与任何其他编程语言一样，我们不需要 Delphi Prism。但 Prism 是具有 Pascal/Delphi 背景的软件开发人员开始为 DotNET 进行开发的一个选择。这重要吗？对于某些人来说，是的。对于其他人来说，并非如此。
我拥有 20 多年的 Pascal 经验，并且熟悉自第一个版本以来的每个 Delphi 版本。但8年前，我也学习了C#，只是因为Delphi作为开发DotNET应用程序的工具太弱了。不幸的是，无论 Embarcadero/Borland 做出多少尝试，他们对 Prism 的开发也将落后于 Microsoft 不断发布的通用 DotNET 产品。
Prism 的优势在于它是 Visual Studio 的附加组件。您可以使用 Prism 为 Mono 平台编写应用程序，该平台在 Apple 的 Mac 计算机上使用。它还可以与 C# 和 VB.NET 应用程序一起工作，您可以创建混合项目，在其中使用 Delphi、C# 和 VB.NET 创建单个产品。 （不过，由多个程序集组成。）Prism 允许您创建可以在常规 WIN32 环境中使用的 Pascal 代码，也可以在 DotNET 中使用。该代码不能太特定于平台，但一般来说，您可以通过这种方式获得一些非常好的结果。
Delphi Prism 并不是由 Borland/Embarcadero 完全开发的！它始于 RemObjects，他为类似 Delphi 的代码创建了一个替代编译器，但具有一些您赢得的附加功能在常规 Delphi 代码中找不到。 RemObjects 开始将 Delphi for DotNET 从市场上推出，因为 RemObjects 提供了更好的产品，并且他们更关注 DotNET 问题。因此，两人开始共同创建 Prism。
与任何编程语言一样，Prism 具有一些您在其他地方找不到的功能。这些功能是否实用始终取决于您是否能找到它们的实际用途。在我个人看来，如果您已经拥有 Visual Studio 并且您只是为 Windows 平台创建应用程序，那么您实际上并不需要 Prism。如果您有额外的 Delphi 经验，您可能会喜欢 Prism 的某些项目。如果您需要将 Delphi/WIN32 应用程序移植到 DotNET，那么 Prism 可能会有所帮助。但我不知道有什么优势可以使 Prism 成为必要条件。
Like any other programming language, we don't need Delphi Prism. But Prism is an option for software developers with a Pascal/Delphi background to start developing for DotNET. Is this important? For some, yes. For others, not really.
I have over 20 years of experience with Pascal and am familiar with every Delphi version since the first one. But 8 years ago, I also learned C# simply because Delphi was too weak as a tool for developing DotNET applications. And unfortunately, no matter how much Embarcadero/Borland tries, their development of Prism will also be behind the generic DotNET products that Microsoft keeps publishing.
The advantage of Prism is that it's an add-on for Visual Studio. And you can use Prism to write applications for the Mono platform, which is used on Apple's Mac computers. It can also work together with C# and VB.NET applications and you can create mixed projects where you use Delphi, C# and VB.NET to create a single product. (Made of multiple assemblies, though.) Prism allows you to create Pascal code that you can use in your regular WIN32 environment but also in DotNET. This code can't be too platform-specific but in general you can get some very good results this way.
Delphi Prism isn't fully developed by Borland/Embarcadero, though! It started with RemObjects, who created an alternative compiler for Delphi-like code, but with some additional features that you won't find in regular Delphi code. RemObjects started to just push out Delphi for DotNET from the market, since RemObjects provided a nicer product and they had focused more on the DotNET issues. So the two started to work together to create Prism.
Like any programming language, Prism has some features that you won't find elsewhere. If those features are practical always depends on if you can find some practical usage for them. In my personal opinion, if you already have Visual Studio and you're only creating applications for the Windows platform then you won't really need Prism. If you have additional Delphi experience, you might like Prism for some projects. If you need to port a Delphi/WIN32 application to DotNET then Prism might help with that. But I don't know of any advantage that would make Prism a requirement.
我个人认为 Delphi Prism 对于（真正的）Delphi 生态系统来说弊大于利。
我不能否认 RemObject 的产品有很多有趣的东西并且在技术上做得很好，但作为一个（真正的）Delphi 程序员和爱好者，我发现它们危险地分散了注意力，并向新来者和 .Net 程序员提供了一些模糊不清的信息。
(MS) .Net 程序员永远不会转向 D. Prism，只有那些希望在离开船舶时平稳过渡的 Delphi 程序员才会转向。
由于 D.Prism 和（真正的）Delphi 之间没有联系，因此将其命名为 Delphi 是一个糟糕的举动。它们共享一些基本的 pascal 语法，但仅此而已。他们甚至不分享他们的改进，也不能完全集成使用。
Personally I think Delphi Prism do more bad than good for the (real) Delphi ecosystem.
I can not deny that the RemObject's product has many interesting things and technically well done, but as a (real) Delphi programmer and enthusiast I see that thay are dangerously distracting the attention and giving some ambiguos non clear message to new comers and .Net programmers.
A (MS) .Net programmer will never move to D. Prism, only Delphi programmers who wants a smooth transition while leaving the boat.
Since there is no tie between D. Prism and (real) Delphi it was a bad move to name it Delphi. They share some basic pascal syntaxis but that's all. They even do not share their improvments, nor they can be used fully integrated.
我购买了适用于 Delphi 和 C++ 的 Rad Studio，但我大部分时间都花在 Prism 上。至于说第三方网络产品落后于微软产品的说法，我认为这只是无知的说法。 Prism 并不缺少 C octothorpe 或 Visual Basic 所拥有的任何东西。网络系统最好是用Hejilsburgs最好的语言object pascal来编程的，而Rem Objects一直在改进网络的最佳语言。 Rem Objects 的那些人行动迅速，让事情发生。所有的更新都来自他们，内河码头只是起立致敬。顺便说一句，C# 到 Prism 转换器确实有效。我在 msdn 上获取代码并将其粘贴到 Prism 中，无需担心。
I bought Rad Studio for Delphi and C++ but I spend most of my time with Prism. As for the old saw that third party products for net are behind the Microsoft products, I say that is just ignorance talking in this case. Prism is not lacking anything that C octothorpe or Visual Basic has. The net system is best programmed by Hejilsburgs' best language, object pascal, and Rem Objects has been improving the best language for net all the time. Those guys at Rem Objects move fast and make things happen. All the updates come from them, Embarcadero just stands and salutes. By the way, the C# to Prism convertor really works. I grab code at msdn and paste it into Prism with no worries.
您可以查看旧问题您会使用Delphi Prism，其中有很多关于Delphi prism的意见Delphi 开发人员和其他人。
You can view old question Will you use Delphi Prism, about many opining about Delphi prism from Delphi developers and others.