I'm not sure where you got the idea that IronPython 1.0 only works with .NET 1.1? I can compile the IronPython solution using the VS 2005 Beta 2 release (and have, several times tonight). For what it's worth, IronPython needs the 2.0 runtime, since it uses 2.0 code generation, and supports 2.0 generics. As far as ASP.NET compiling pages written in IronPython, my memory is that ASP.NET would need to be modified to recognize a new language. At least, that's the case in 1.1; it's possible that 2.0 is more extensible in this regard (wish list if not). Speculation: you should be able to subclass Pages in IronPython, and then modify the aspx page to inherit from your IronPython class. Of course, we'd need to have compilation running (is that on the list for 1.0?). ----- Keith J. Farmer [EMAIL PROTECTED]
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lorenzo Bolognini So basically what's the story for the .NET 2 runtime support? Will you make it possible to integrate IronPy in VS .NET 2005 final release and use the .NET 2 runtime to develop ASP .NET apps? If I remember correctly IronPy 1.0 will only be compatible with the 1.1 runtime. Will it support something like partial classes à la C# so that the code-behind file doesn't get polluted with the IDE generated code? I wouldn't really care about other .NET 2 features if I could have that so I would happily use .NET 1.1 to develop aspx. _______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com