It sounds like you need to re-build your own DLLs (or whatever SPTools is) to run against .NET 3.5 instead of .NET 4.0.
From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jaromír Matýšek Sent: Monday, March 28, 2011 8:09 AM To: iro...@googlegroups.com Subject: [IronPython] IPy 2.7 successfully built for .NET 3.5, but problem w. indirect v4 dependencies Hi, I've suceeded building 2.7 for .NET 3.5 (I'm using it in SharePoint, so there's no way to use .NET 4) and it works, using v2release configuration. I've built IronPython, IronPython.Modules, Microsoft.Dynamic, Microsoft.Scripting and Microsoft.Scripting.Core dlls. However, when I reference my class library (which is referencing my custom-built 2.7 dlls) from another solution and try to compile, I get several instances of the following warning and of course errors wherever I'm using some of my class library functions: The primary reference "SPTools ... " could not be resolved because it has an indirect dependency on the .NET Framework assembly "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" which has a higher version "4.0.0.0" than the version "2.0.0.0" in the current target framework. C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets I've now spent a day and half trying to get rid of this problem. I've combed through the project files - they're all switched to v2, there's nothing even vaguely v4 related, it all compiles too, the problem remains. I'd be very grateful for any ideas. Thanks Jaromír Matýšek
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
