How to stop that annoying beep on your server Many
July 4, 2009 – 12:01 amHow to stop that annoying beep on your server
Many years ago I was working on a project that had some large batch processing in it. To do this processing we had some dedicated servers, one of which sat under the desk next to me. Apart from the noise of the fan soudning like we had actually bought a jet fighter the most annoying thing about this processing was that it resulted caused the servers beep to continually sound. Something in the code caused it to fire. Boy it was annoying.
I?ve got lots to say just not enough time
I haven?t really spent anytime blogging in the past few months. I have a tons of things to say, unfortunately just don?t have enough time at the moment. I?ve obviously been writing my book on Azure and have loads to blog about regarding. I?ve also spent time messing around with design patterns Data Layers OR/M?s, Caching I?ve also been looking outside of the Microsoft stack which reaffirms my position of why I?m glad I work with Microsoft.
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:
- Download and install TestDriven.Net 2.11.
- Download the RowTest Extension for NUnit 2.4.5 (Binary).
- Create a directory called ‘addins’ in ‘%ProgramFiles%\TestDriven.NET 2.0\NUnit\2.4′.
- Copy the ‘NUnitExtension.RowTest.AddIn.dll’ file into the ‘addins’ directory (don’t put any non-assembly files there).
- 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.
Integration Services Design Principals
Whilst doing some design work today for a customer project I realised there are a set of principals I try and adhere to when creating SQL Server Integration Services packages. The list is no doubt incomplete but this is what I have so far. Minimise IO This is a general data processing principal. Usually disk and, to a lesser extent, network performance determine the overall processing speed. Reducing the amount of IO in a solution will therefore increase performance.
Hyper-V: How to remove disabled virtual network adapters from the parent partition
In May, I mentioned that we introduced a checkbox in the Hyper-V UI for Windows 7 and Windows Server 2008 R2 which determines whether a virtual NIC is created in the parent partition for External Virtual Networks. (To get a better understanding of Hyper-V networking and what this means, take a look at this article.
You must be logged in to post a comment.