NuGet bug: Microsoft.Scripting.* assemblies shouldn't be referenced

[tkellogg]

I just installed the IronJS-0.2.0.1 package which includes three Microsoft.Scripting.* DLLs. Two of these assemblies caused build warnings (Microsoft.Scripting.Core and Microsoft.Scripting.ExtensionAttribute) due to multiple assemblies with the same classes. The aspnet compile of Razor views completely failed for the same reason.

I fixed the problem by removing Microsoft.Scripting.Core and Microsoft.Scripting.ExtensionAttribute from the project references. Which brings me to the ultimate question, why were these being referenced at all?

I'm using .NET 4.5. I also asked this stack overflow question about it.

[fholm]

They are referenced for the .NET 2.0 build, they must have been included by
mistake in the .NET 4.0 project files.
*

Regards,
Fredrik Holmström*

On Mon, Oct 15, 2012 at 5:06 AM, Tim Kellogg notifications@github.comwrote:

I just installed the IronJS-0.2.0.1 package which includes three
Microsoft.Scripting.* DLLs. Two of these assemblies caused build warnings
(Microsoft.Scripting.Core and Microsoft.Scripting.ExtensionAttribute) due
to multiple assemblies with the same classes. The aspnet compile of Razor
views completely failed for the same reason.

I fixed the problem by removing Microsoft.Scripting.Core and
Microsoft.Scripting.ExtensionAttribute from the project references. Which
brings me to the ultimate question, why were these being referenced at all?

I'm using .NET 4.5. I also asked this stack overflow questionhttp://stackoverflow.com/q/12840880/503826about it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/92.