Hurm, I think I may have gone w/ the wrong alias. Try ironpy at microsoft.com instead.
The problem w/ a graphical way to add references is that we start to get into a complex world where the .py files are not representing everything that your code needs and therefore running them from the command line is not identical to running them in VS. We could consider an add references dialog which pastes code into a .py file but I'm not sure how weird this would be. We could also even consider providing intellisense for when you're filling in the string for clr.AddReference(...). IronPython Tools includes 2.6.1 RC1 for .NET 4.0 as the version of IronPython it works against by default. Because it targets Visual Studio 2010 it'll always target primarily CLR4. You can configure what interpreter it runs against in project properties but that won't have any impact on the code analysis (or the REPL process) right now. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Cronin, Ted Sent: Wednesday, February 24, 2010 2:32 PM To: 'Discussion of IronPython' Subject: Re: [IronPython] IronPython Tools Any word on the email address not connecting, also was just pointing out that AddReference was not accessible from References. Nice to have a graphical way to add references rather than just through code. By chance has the issue been resolved for adding references for our own assemblies from Gestalt. Do the tools work with 261, or does that really matter, or should we be testing with 26? So far this is really nice, in that we now have access to more than just winform capability, so thank you for doing this for the community. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dino Viehland Sent: Wednesday, February 24, 2010 2:23 PM To: Discussion of IronPython Subject: Re: [IronPython] IronPython Tools Currently the best way to add a reference is to call clr.AddReference('assemblyname'). The analysis engine will pick up the call and include the assembly as being available in the list of imports. I'll take a look at the crashing bug. As for ASP.NET support we'll need to look into getting some templates and including our existing ASP.NET support in the overall package. There was also interest at PyCon about this so it seems likely we'll add this in (and it shouldn't be too much work to create a template). As for online templates we're likely to ship all of the templates we make w/ IpyTools. But I think you should be able to create on-line templates for other users to use. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Cronin, Ted Sent: Wednesday, February 24, 2010 2:10 PM To: 'Discussion of IronPython' Subject: [IronPython] IronPython Tools So, that's cool, it appears you have gestalt inside of Ipy Tools, How do we add Reference, also when trying to add a new search path, VS crashes with an Unhandled Exception, duped in sl and wpf. Will there be an asp.net web form project? There are no online templates.
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
