Dino, thanks for the ideas, but I'd rather not do anything too drastic like that. I have a complex application that can be extended by other DLLs and it has to behave like a standard .NET 3.5 app. I'm trying to implement scripting on top of that, so scripting will have to fit in...
2008/8/18 Dino Viehland <[EMAIL PROTECTED]>: > The only thing I can think of is to explicitly provide the list of > assemblies (which I believe you can do through config) and exclude > System.Core – of course that only works if you're not using any of the new > features. I haven't tried it though so maybe that doesn't work L… But I do > believe ASP.NET via CodeDom is passing /noconfig to the compiler. > > Another idea would be to lock your project back to .NET 2.0. There's a new > CompilerVersion tag that needs to be specified via config that was added w/ > .NET 3.5. You can set the version there to v2.0 and we'll then use the > original C# 2.0 compiler. _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
