We recently made the call that Microsoft.Dynamic's API surface would ship in .NET 4 as all internal API surface. It's still open source so anyone can pick it up and include it in their own languages to get COM support but C# needs it in the box somewhere so they can provide COM support as well. But we're not really sure what we want .NET COM support to look like long term yet so we don't want to commit to shipping the API forever just yet. The CLR2 flag allows us to build it as publicly accessible APIs on .NET 2/3/3.5 and build it as internal APIs in our internal builds for .NET 4.
________________________________________ From: [email protected] [[email protected]] on behalf of Seo Sanghyeon [[email protected]] Sent: Wednesday, July 15, 2009 2:43 AM To: Discussion of IronPython Subject: [IronPython] FePy status update Now I updated FePy's NAnt build file to include newly introduced Microsoft.System.Debugging.dll. I also found that I need to define CLR2 symbol to compile Microsoft.Dynamic.dll. Without the symbol it won't compile. What is the purpose of this symbol? Sorry for the delay, -- Seo Sanghyeon _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
