Then after installation, you get a few new project types. Installation is easy, as long as you first uninstall any previous IronPython tool you have installed into Visual Studio. But it's still a bit unclear what Microsoft's intentions are.) And to make it even more confusing, Microsoft's open source development site, CodePlex, hosts both IronPython and these new tools.Īnyway, because IronPython has been available for a long time and isn't new here, I'm going to focus this review on the CPython aspect of this new tool. (The beta of these new tools was announced back in March, so this isn't a sudden surprise. I'm not sure if they've changed their mind about Python, or what. And so for Microsoft to release an updated set of tools for IronPython is a bit perplexing. But it was unclear what Microsoft was doing a lot of people were surprised because there had been growing interest in a version of python that targets.
IronPython continued to live on as a community-supported, open-source project within the Microsoft's CodePlex open source site. Shortly after that, the original creator of IronPython left his job at Microsoft. But some of you might remember something that happened almost a year ago: Microsoft suddenly stopped supporting IronPython. But if I do find out later (and DaniWeb readers even care), I'll post the answer in the comments. I wasn't able to find out at the time of this writing. I'm not really sure if this is a competing tool to the main IronPython tool, or if this is the next generation. Trying Out Python Tools For Visual Studioįirst, in case you're wondering, this tool replaces the previous IronPython tool for Visual Studio. The tool is free and open source, and it works in any of the non-free versions of Visual Studio, or with the free, standalone Visual Studio Shell.
Why? Because it supports CPython, not just IronPython. NET, I use C#.Īnd so while the IronPython tools for Visual Studio have sat idle on my computer, I'm certainly open to a new tool put out by a team at Microsoft called Python Tools for Visual Studio. Instead, when I use python, it's the original python, called CPython (because it's written in C), that I use. As such, I've had little use for the IronPython tools for Visual Studio, which is a tool that lets you develop and debug IronPython code from within Visual Studio. In the past, oh maybe four years, I've created a grand total of two IronPython programs, each consisting of maybe three lines of code, just to try it out. NET implementation of python called IronPython, truth be told, I never use IronPython anymore.
And although I once wrote a raving review of the. And over the years, I've been pleased with the array of development tools that have been created for it, including the different IDEs. People who know me know that Python has always been one of my favorite languages.
0 kommentar(er)
