NWSGI 2.0 Release Candidate 2

The final release candidate of NWSGI 2.0 is now available. Except for version numbers, this is what will become NWSGI 2.0 as soon as IronPython 2.6 is released.

NWSGI 2.0 Release Candidate 2 includes all of the features of NWSGI 2.0 Release Candidate 1, and adds support configuring tracing, lightweight scopes, and the profiler. It is built against IronPython 2.6 RC3.

The following issues are fixed in this release:

• Add configuration option for Profiler
• Add configuration option for Lightweight Scopes
• Add configuration option for tracing

IronPython Extensions for Visual Studio 2010

UPDATE (Feb 28, 2010): The IronPython team recently announced IronPython Tools for Visual Studio, so this project is no longer being maintained.
 
Lately, I’ve been experimenting with the new editor APIs in Visual Studio 2010 to build some simple extensions to make Python editing a little better. Helpfully, IronPython exposes most of the complicated infrastructure (the tokenizer) to make the job easy. The documentation for the new editor APIs is still a bit weak; hopefully that will improve by the final release. In the meantime, the examples are the best source of information. There also a series of blog posts by Mike Feingold about the NDjango editor for VS2010 that form a great end-to-end example.

Download & Installation

Download IronPython Extensions for Visual Studio 2010 (and the source code; Ms-PL as always) from my BitBucket repository or from the Visual Studio Gallery (direct link). For direct downloads, just run (double-click) the .vsix file to install it into Visual Studio. Otherwise, you can use the extension manager (search for "IronPython") and install it directly from Visual Studio.

Features

The extensions provide three features so far: syntax highlighting, brace matching, and outlining.

In the future I'm planning on adding project support, templates, and (most difficult of all) IntelliSense.
an unknown author

NWSGI 2.0 Release Candidate 1 Released

To coincide with IronPython 2.6 RC1, NWSGI 2.0 RC1 is now available.

This release is identical to Beta 2, except for the version of IronPython is uses.

Using NWSGI 2.0 Beta 2 with IronPython 2.6 RC1

UPDATE: This won't work. The IronPython team made some changes that break the ABI (Microsoft.Dynamic, I'm looking at you) which renders this fix unworkable.

NWSGI is linked against specific versions of IronPython, so every time the IronPython team changes the AssemblyVersion, I need to respin NWSGI. In the meantime, an <assemblyBinding/> section can be used in web.config to make previous NWSGI version work with newer IronPython versions.

Thanks to Markus Törnqvist for coming up the specific elements for this case:

    <runtime>
       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
           <dependentAssembly>
               <assemblyIdentity name="IronPython" publicKeyToken="31bf3856ad364e35" culture="neutral" />
               <bindingRedirect oldVersion="2.6.0.20" newVersion="2.6.10920.0" />
           </dependentAssembly>
           <dependentAssembly>
               <assemblyIdentity name="Microsoft.Scripting" publicKeyToken="31bf3856ad364e35" culture="neutral" />
               <bindingRedirect oldVersion="0.9.6.20" newVersion="1.0.0.0" />
           </dependentAssembly>
       </assemblyBinding>
   </runtime>

I’ll try to get an update of NWSGI out as soon as possible.

NWSGI 2.0 Beta 2 Released

NWSGI 2.0 Beta 2 is now available. This release in linked against IronPython 2.6 Beta 2, and also fixes a couple of bugs. The big change is that the install does not add NWSGI to the GAC; without IronPython also installed to the GAC, it doesn't make much sense to put NWSGI there.