Developer News

IronPython and WPF Part 3: Data Binding Here?s the short

IronPython and WPF Part 3: Data Binding
Here?s the short version of this post: data binding in WPF to IPy objects just works…mostly. However, I?m guessing you are much more interested in the long version. Typically, data binding depends on reflection. For example, the following snippet of XAML defines a data bound list box where t
Harry Pierson

Microsoft vs TestDriven.NET - 06 June 2007

Today Microsoft kindly extended my deadline by 24 hours so that I could further consult my lawyers. So far they have done a very good job of keeping the pressure on. This isn’t simply a case of knocking out a quick email Pirate Bay style!

Before I released support for Visual Studio Express, I made a point of carefully reading the Express EULA. After reading it I was confident that the technique I was using wasn’t in breach of the license. I am now acutely aware that if I turn out to be wrong I could end up losing everything. This isn’t a situation that any developer wants to find themselves in.

Unfortunately the alternative to fighting this is bowing down to a vague catchall clause. I am an anxious person and don’t want live in fear of this kind of thing.

TestDriven.Net 2.11: Parameterized NUnit Tests

TestDriven.Net has always supported parameterized test methods when used with the MbUnit testing framework. When using MbUnit, it is common for a single test method to execute multiple tests with different parameter inputs. The most famous of these test types is the MbUnit RowTest.

Until now there has been little reason to add support for executing parameterized tests using NUnit (historically NUnit has only supported parameterless test methods). However Andreas Schlapsi has recently written an implementation of MbUnit’s RowTest using NUnit 2.4’s Addin extensibility mechanism.

I’ve updated TestDriven.Net 2.11 to better support NUnit add-ins and enable the targeting of RowTests and other parameterized test types. This version also includes a workaround for a log4net related issue that was causing a noticeable delay when launching the NUnit 2.4 GUI. You can find the release notes for TestDriven.Net 2.11 here.

To install the RowTest Extension for NUnit you will need to do the following:

1. Download and install TestDriven.Net 2.11.
2. Download the RowTest Extension for NUnit 2.4.5 (Binary).
3. Create a directory called ‘addins’ in ‘%ProgramFiles%\TestDriven.NET 2.0\NUnit\2.4′.
4. Copy the ‘NUnitExtension.RowTest.AddIn.dll’ file into the ‘addins’ directory (don’t put any non-assembly files there).
5. Add a reference to ‘NUnitExtension.RowTest.dll’ from your NUnit test project.

You can then start writing and executing MbUnit style RowTests inside your NUnit projects! You can find Peli’s original RowTest example here.

To view your RowTests inside the NUnit GUI you will need to use ‘Test With > NUnit 2.4′. You will find this option on the ‘Solution Explorer’ project context menu.

Thanks to Wayne Brantley for letting me know about the RowTest Extension for NUnit.