Title: RE: [IronPython] Road Map for IronPython
Closer to the former.<g> Obviously, it's a highly iterative project, so releases can easily build up functionality in whatever order is important. Python projects with syntax highlighting would be easy. IntelliSense is harder, mostly because of Python's dynamic typing, not VS itself. I'm not sure what's involved with a debugger, though it's a lot easier to hook up a managed language into the existing managed debugger (than wiring up a custom native debugger). Build support would be writing an MSBuild task, once there's a compiler.
 
http://msdn.microsoft.com/vstudio/extend/ is the SDK home page. You have to register to download it, but it's free to do so. Sometime soon there will be a documentation update my team did, which contains a bunch of updated topics on managed language services.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith J. Farmer
Sent: Wednesday, 11 May, 2005 20:31
To: Discussion of IronPython
Subject: RE: [IronPython] Road Map for IronPython

I wouldn’t expect it to be.  But would it be a do-it-in-a month project, or a do-it-in-a-year-with-help project?

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, May 11, 2005 7:51 PM
To: 'Discussion of IronPython'
Subject: RE: [IronPython] Road Map for IronPython

 

Language services are in the Visual Studio SDK realm (formerly VSIP SDK). There's a managed library for creating them. But it's not a do-it-in-a-weekend project to fully support a new language in Visual Studio.

_______________________________________________
users-ironpython.com mailing list
users-ironpython.com@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

Reply via email to