TestDriven.NET 2.7 on Orcas Express! I’m happy to report that
May 11, 2008 – 11:00 amTestDriven.NET 2.7 on Orcas Express!
I’m happy to report that TestDriven.NET is working on Orcas Express! If you’d like to try out the new C# 3.0/VB 9.0 language features without installing the full Visual Studio Orcas Edition then now’s your chance. You should find this version works with Visual C#, VB and C++ Orcas Express CTP/.NET 3.5 Beta 1. Due to some changes Microsoft made to Orcas it works even more seamlessly than it does in Visual Studio 2005 Express!
NOTE: There is a chance this functionality will be disabled at 4 PM London time next Friday, 1 June 2007. Why find a technical solution to a problem when you have an army of lawyers?
TestDriven.Net 2.10: ‘Go To Reflector’ now supports generics
Over the past year the ‘Go To Reflector’ command has become a first class citizen inside TestDriven.Net. You will find the ‘Go To Reflector’ button on many different context menus inside Visual Studio. The ones I use most often during development are the ‘Code Context’ and ‘Project Reference’ menus. When I’m debugging I tend to use the ‘Call Stack’ and ‘Modules’ context menus.
For a long time I’ve put off attempting to add support for generics to the ‘Go To Reflector’ command. The Visual Studio CodeModel and StackFrames APIs don’t really support generics, so I wasn’t even sure if this would be possible. This was becoming a problem with more and more code being written that uses generics. I decided it was time to bite the bullet and see what could be done.
I’m happy to say that TestDriven.Net 2.10 now has pretty decent support for generics.
You can ‘Go To Reflector’ from your generic class definitions. Generic methods, classes, fields, properties and nested classes are all supported.
You can round trip and ‘Go To Source Code’ from inside Reflector. I often find using Reflector is the fastest way to navigate my own code.
When you’re debugging you can ‘Go To Reflector’ from any stack frame in the ‘Call Stack’ window. This is particularly useful when the debugging option ‘Just My Code’ is turned off. When an exception is thrown you can quickly see what caused it by selecting the top of the call stack.
Note: For updated ‘Go To Reflector’ on ‘Call Stack’ support you will need to be using TestDriven.NET 2.10.2173 or later (I released this a few days after the original 2.10 build). You can read the release notes and download the latest version from here.
Review: LINQ Quickly
One of the big advantages of LINQ is that we could use it against Objects, collections, XML, etc. Most importantly, searching a collection or a node in XML can be easily done using LINQ. LINQ uses queries similar to SQL, which is rather easy compared to querying an XML using XPath. The author, Satheesh Kumar, explains LINQ and how it can be used to solve the most common issues lying around objects, XML, SQL, Datasets and XSD. This is a great book for beginners.
Jesudas Chinnathampi (Das)
It has been over a month since my last update. I just want to put to rest any rumors of TestDriven.Net’s early demise. With the help of my lawyers, I responded to Microsoft’s lawyers‘ letter and am now attempting to come to a resolution of the issues. Continuing to play this out on the blogosphere would unnecessarily antagonize the situation and undo the good progress which has been made.
To be clear I am not anti-Microsoft. I am simply a passionate advocate of unit testing for developers of all experience levels. To my mind test driven development is like climbing with ropes. Beginner climbers can gain the confidence to climb without the fear of landing in a mess at the bottom. Expert climbers can take on overhangs and other hard problems that they wouldn’t otherwise have the confidence to try. Climb without ropes if you like, but I am certainly not going to encourage it for anything outside your comfort zone.
To end on a happy note the Wells for Zo charity that many of you supported last year through the .NET Developer’s Charity Auction is about to enter a new phase. You can read about the pump workshop which is being set up in Mzuzu, Malawi later this year. There is also a photo blog which is being updated by our guy in the field (when the Internet works). Perhaps the people who suggested I put up a PayPal button to help with legal fees would prefer to save their money for something worthwhile and make a donation here instead. :-)
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;
You must be logged in to post a comment.