Developer News

TestDriven.Net 2.13: Support for NUnit 2.4.7The latest release of TestDriven.Net

TestDriven.Net 2.13: Support for NUnit 2.4.7

The latest release of TestDriven.Net is now compiled against NUnit 2.4.7. This version of NUnit includes Andreas Schlapsi’s popular RowTest extension. The RowTest attributes have been moved to the ‘nunit.framework.extensions’ assembly (which you can find here: \Program Files\TestDriven.NET 2.0\NUnit\2.4\nunit.core.extensions.dll).

Here is an example RowTest method that tests a prime number function:

The prime number function might look like this:

As you can see the intention of the test is very clear and there is no repetition. I’ve written more about parameterized unit tests here.

NCoverExplorer… v1.4.0

Syndicated from Kiwidude’s Geek Spot

I’ve had this "quietly available" on the download page for a few weeks to gain feedback on any issues and with no known issues outstanding it seems appropriate to more publicly announce it.

A big change in NCoverExplorer 1.4.0 is that it is no longer published under the GPL license. I made this change for a number of reasons; amongst which was the concern that a number of companies have of deploying GPL based tools into their development process. This roadblock has been removed and should no longer prevent your companies from using this toolset.

My original choice of GPL was based on using the ICSharpCode 1.x texteditor control. I have now dropped that component in favour of using the superior (but commercial) Actipro SyntaxEditor control instead. The improvements are not only in stability and features but also visual as you can see below in the code highlighting screenshot. A splitter window is available as also shown.

So why should you upgrade to NCoverExplorer 1.4?

This release is less about adding new features (although there are some to be found) and more about stabilisation for the future. The core model code has been rewritten and better tested. There have been countless code coverage corner cases (say that five times in a row!) arise that should be better catered for. Better performance for .NET 2.0 users, lower resource usage, better error handling and some minor gui quirks addressed.

Some of the "internal" changes have spilled over externally. For instance the configuration file format used by NCoverExplorer.Console with /c has changed to support new features, although I have retained legacy compatibility for those who choose not to upgrade their build scripts immediately.

What about the new features? Well, the ones I did squeeze in were…

• Support for the //pm (profiling a process by name) argument in NCover 1.5.8;
• Copy command in the source code text area via right-click;
• Print preview command in the File menu;
• /fc argument for NCoverExplorer.Console to fail a build if the combined total coverage of all assemblies does not meet the minimum specified. This was the original behaviour of the /f command before it was changed to fail if any individual assembly does not meet the minimum;
• Coverage exclusions now support the ‘?’ wildcard and multiple ‘*’ wildcards within the expression.
• Report xml contains a "totalSeqPoints" attribute as requested for developers writing alternate xsl reports that need to calculate the excluded code at each level;
• Update the NAnt/MSBuild task dlls to support the latest changes;
• Redesigned the options dialog as shown below;

PDC 2008
The website is live and it’s running with Silverlight http://www.microsoftpdc.com/ If I use this bling as my desktop; http://www.microsoftpdc.com/Social/Bling.aspx where it says “Meet Me in Los Angeles” then does that mean that I get to go to PDC? Note : Just like the PDC’s since 2000 it is …
mtaulty

Another way of looking at this

Jamie A comments to an article on Channel Register:

Here’s a slightly less technical way of looking at the issue:

Microsoft essentially have 2 editions of a program. The first edition speaks English (User Interface) to the user, but in behind can speak French (COM) to other components.

The second edition also speaks English and French, but can also speak Russian (VSIP - Visual Studio Integration Programme).

Microsoft intends that your components speak Russian in order to extend Visual Studio. Their VSIP license agreement also states that you can only try to speak Russian to the second edition of the software. Attempting to speak Russian to the first edition is not allowed (even if it does speak the language).

Rather than try and speak Russian, Jamie has been using French. He has asked Visual Studio if it talks a certain dialect (COM interface), and it has said “oui”. So he uses that dialect to talk to Visual Studio in order to do what he needs.

The main problem from Microsoft’s point of view is that they didn’t intend for anyone to use that dialect of French in order to talk to Visual Studio. They only expected Russian to be used. However, there’s nothing that explicitly states this. Microsoft even has public notes on the French dialect.

Therefore, Jamie thinks he’s in the right because Microsoft have not said that speaking French is forbidden. Microsoft sees it the other way. And the way things are going, it looks like the decision is going to come from a judge or jury.

There will be some French lessons in a follow up post.