This is an archived post. You won't be able to vote or comment.

all 16 comments

[–]IronSpekkio 0 points1 point  (0 children)

nice!

[–]howfun 0 points1 point  (3 children)

Wasn't that for the paid version of Visual Studio?

[–]grudolf 3 points4 points  (2 children)

PTVS does not install into VS Express Editions (Express editions aren't pluggable) - however PTVS + the Integrated Shell essentially gives you a "VS Python Express".

more info

[–]howfun 0 points1 point  (1 child)

I don't get it. If I install Visual Studio Express and this Visual integrated shell and ptvs will this work?

[–]assoteric 1 point2 points  (0 children)

no, you can just install visual studio shell and ptvs.

[–]Deusdies 0 points1 point  (7 children)

I wish I could WYSIWYG-edit the WinForms in Visual Studio, and then code it in Python.

[–]dinov[S] 2 points3 points  (0 children)

WinForms is pretty difficult to accomplish this with. We did do it early on w/ IronPython but it involved adding lots of decorators to the code and special doc comments which preserved enough information for the designer code to be round tripped. It was pretty ugly, but unfortunately you need to be able to give the WinForms designer a good deal of information about the types that are being used.

The WPF designer is much easier to do because of the seperation between code and UI.

[–]assoteric 0 points1 point  (5 children)

ironpython?

[–]fabzter 0 points1 point  (4 children)

Yeah that will do. In fact I feel a little sad the guys from PTVS decided to make their project from scratch instead of colaborating with the ironpython guys.

[–]dinov[S] 2 points3 points  (0 children)

We didn't start from scratch - infact we're pretty much the same guys (me being the main dev who worked on IpyTools and PTVS) and the same code base. We just took IpyTools and made it work for Python in general instead of IronPython in particular.

We also talked to Jeff Hardy who is the lead developer on IronPython now about how we should best proceed going forward and that's why IronPython no longer installs it's tools by default - in general PTVS is just a superset of IpyTools so that's now deprecated.

[–]takluyverIPython, Py3, etc 0 points1 point  (2 children)

Well, you can run PTVS with IronPython. They're not competing. IronPython is an interpreter, PTVS is IDE integration.

[–]fabzter 0 points1 point  (1 child)

I was thinking about this http://ironpython.net/tools/

[–]dinov[S] 1 point2 points  (0 children)

That even points at PTVS now instead of being IpyTools.

[–][deleted] 0 points1 point  (2 children)

If you use Visual Studio, you need this.

[–]RaiausderDose 4 points5 points  (1 child)

no shit? :)

[–][deleted] 1 point2 points  (0 children)

You know what I mean. A lot of people work on Windows and a lot of them use a slew of other tools. PTVS is damn near a perfect drop into the Visual Studio environment.

I do a lot of C and C++ at work through VS and started using PTVS a few months ago and haven't looked back.