views:

125

answers:

2

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?

+1  A: 

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.

João Angelo
Thank you for the very quick reply. It was very helpful to know that the DLLs weren't supposed to be there. Your answer led me to find this: http://ironpython.codeplex.com/SourceControl/changeset/changes/71898 which has the change to IronPython.csproj that removes Microsoft.Scripting.ExtensionAttribute.dll. Looking at the diff showed that the file wasn't supposed to be used with .NET 4.0 even before it was removed.
richj
+4  A: 

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

Hans Passant
This is correct - and Micorosoft.Scripting.ExtensionAttribute has been in System.Core since .NET 3.5 but previous versions of IronPython only needed .NET 2.0 SP1 or later which is the reason why we shipped that one.
Dino Viehland
I found a lot of posts (discussing the .NET 2.0 SP1 version) containing statements that are now outdated - so I ended up very confused. Thank you both for these definitive statements.
richj