Legal aid for whistle-blower site Rights groups help whistle-blowing site
February 29, 2008 – 7:00 amLegal aid for whistle-blower site
Rights groups help whistle-blowing site Wikileaks fight attempts to knock it offline….
Colin Harman MACITP
Pixware ships XMLmind XML Editor v3.7.0
Pixware has released version 3.7.0 of XML Editor, with a DITA add-on that now fully supports the DITA DTD 1.1. It includes its own minimal copy of DITA Open Toolkit version 1.4. The new Tools|Helper Application sub-menu contains entries that allow …
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.
Problem on Sending E-mail
I wish to incorporate e-mail in my page such that when a user had pressed a button, an email will be sent to the recipient. This has been my code.
TestDriven.Net 2.10: Smart Build
There are a number of new features in TestDriven.Net 2.10 that I want to highlight (apart from the VS 2008 crash workaround). The one I’m going to focus on here is subtle, but significant I believe - especially for people working with large solutions.
Smart build is a new optimization that allows you to skip the build step before test execution when there are no source code changes. Anyone working on a solution with a large number of projects will know how time consuming the build can be before any tests can be executed. Somewhat surprisingly this remains true even when no actual source code edits have been made and nothing needs to be compiled. I’ve had reports of the build check taking as long as 45 seconds before any tests could be executed! (Thanks to Brian Genisio in particular for bringing this to my attention)
The new smart build feature overcomes this particular problem by monitoring your solution for source code edits and automatically skipping the build step if there is nothing new to compile. This can significantly improve performance when running multiple tests in the same solution. For example there is now no penalty for choosing to execute all tests in a fixture after an individual test starts to pass: a common usage pattern.
I will elaborate further on other new features in future posts. In the meantime you can read the latest release notes and download TestDriven.Net 2.10 from here. If you find any issues, please don’t hesitate to contact me.
You must be logged in to post a comment.