On Tue, Jun 2, 2009 at 10:48 AM, Dave Fugate<dfug...@microsoft.com> wrote: > I think it's a safe bet that when the final version of .NET 4.0 is released > we'll either: > * re-release the latest final version of IronPython against it. If .NET 4.0 > had already shipped today, this would end up being "IronPython 2.0.1 for .NET > 4.0" > * release the next version of IronPython (e.g., IP 2.7/3.x Alpha/Beta/etc) > against it > In any event, we definitely plan on shipping something built against .NET 4.0 > that doesn't contain "Community Technology Preview" in the title. > > Until the final version of .NET 4.0 ships, expect more preview releases of > IronPython for .NET 4.0.
OK, cool. I'm working on a version of NWSGI for .NET 4 and wanted to make sure it was worthwhile right now. > > As for your question about adding IronPython assemblies to the GAC, I'm not > aware of any extra requirements offhand. Maybe Dino knows... > See http://lists.ironpython.com/pipermail/users-ironpython.com/2008-October/008698.html. Curt doesn;t mention anything specific, though. - Jeff _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
