Microsoft.Scripting.Core.dll 在哪里?

发布于 2024-09-24 02:00:00 字数 851 浏览 1 评论 0原文

我在安装了 Visual Studio 2010 的计算机上的 Windows Vista x64 上安装了 IronPython 2.6.1。我希望在 IronPython 目录中找到这些 DLL:

Microsoft.Scripting.Core.dll
Microsoft.Scripting.ExtensionAttribute.dll

...,但它们不在那里。

这是 IronPython 2.6.0 和 2.6.1 之间的差异还是我的安装有问题?

编辑

有人建议我编辑这个问题来解释为什么它不是如何使用 Microsoft.Scripting.Hosting?

这两个问题都与从 C# 项目引用 Iron Python 库的问题有关。

然而,这个问题是关于将 C# 项目从 Iron Python 2.6.0 升级到更高版本时遇到的问题。请注意下面的评论:“我发现很多帖子(讨论 .NET 2.0 SP1 版本)包含现已过时的语句”。这个问题是关于 .NET 4.0 版本,而不是基于 .NET 2.0 CLR 构建的 .NET 3.5 版本。

未解析的库名称为搜索引擎提供了独特的签名,因此导致问题的特定搜索词是不同的。技术细节(例如库名称、Visual Studio、C# 和 .NET 版本)都不同,并且要解决的问题(库升级与新项目设置)也不同。

这两个问题的根本原因是 DLR 库在连续版本中迁移到 CLR,但每种情况下要解决的问题都是特定于各个问题的。

I installed IronPython 2.6.1 on Windows Vista x64 on a machine with Visual Studio 2010 installed. I expected to find these DLLs:

Microsoft.Scripting.Core.dll
Microsoft.Scripting.ExtensionAttribute.dll

... in the IronPython directory, but they are not there.

Is this a difference between IronPython 2.6.0 and 2.6.1 or do I have a problem with my installation?

Edit

It has been suggested that I edit this question to explain why it is not a duplicate of How to use Microsoft.Scripting.Hosting?

The two questions are both about problems referencing Iron Python libraries from C# projects.

However this question is about a problem encountered upgrading a C# project from Iron Python 2.6.0 to a later version. Note the comment below: "I found a lot of posts (discussing the .NET 2.0 SP1 version) containing statements that are now outdated". This question is about .NET 4.0 version, not .NET version 3.5 which builds on the .NET 2.0 CLR.

The unresolved library names provide a distinctive signature to a search engine therefore the specific search terms leading to the question are different. The technical details such as library names, Visual Studio, C# and .NET versions are all different and the problem being solved (library upgrade vs new project setup) is different.

The root cause of both questions is the migration of DLR libraries into the CLR over successive releases, but the problem being solved in each case is specific to the individual question.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

穿越时光隧道 2024-10-01 02:00:00

这些程序集实施了 DLR。它已移至 .NET 4.0 System.Core.dll 程序集中。

Those assemblies implemented the DLR. That's been moved in .NET 4.0, System.Core.dll assembly.

江湖彼岸 2024-10-01 02:00:00

我安装了 .NET 4.0 的 2.6.1,但这些程序集不可用,因为如果我没记错的话,它们已集成到 .NET 4.0 System.Core 中。

这些程序集在 IronPython 2.6.1 的 .NET 2.0 版本中仍然可用。

I have 2.6.1 for .NET 4.0 installed and those assemblies are not available since, if I'm not mistaken, they were integrated into .NET 4.0 System.Core.

Those assemblies are still available in the .NET 2.0 version of IronPython 2.6.1.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文