I have been working today with Jeremy Millers’ ScreenBinder stuff and ran into a problem today with the tests. The tests all passed fine in Visual Studio, and with rake at the command line on my computer. The problem however came when I checked the code into source control, I got a nasty test failure message in TeamCity:

 

Here is the error: Test(s) failed. System.Runtime.InteropServices.COMException : The program issued a command but the command length is incorrect. (Exception from HRESULT: 0×80070018)

So I did some googling around and found there is a bug in the .NET Framework 3.5 SP1 regarding this issue. So a little more work and I found a work around. I believe this bug only pertains to WPF stuff.

 

Workaround

On the build agent do the following:

1. Stop the TeamCity Build Agent service (Start –> Run –> services.msc –> TeamCity Build Agent –> Right Click –> Stop)
2. Browse to the service file (C:\TeamCity\BuildAgent\launcher\bin)
   
3. Right click TeamCityAgentService-windows-x86-32.exe and click Properties
4. Go to the Compatibility Tab
   
5. Click Show settings for all users
6. Change the Compatibility mode to be Windows XP (Service Pack 2)
   
7. Click OK a few times to close all the windows
8. Start the TeamCity Build Agent service.

You should now have a working build with WPF unit tests. Hope this helps somebody out as I was banging my head on the wall trying to figure it out.

Tags: How-To, NUnit, TeamCity, Testing, WPF

Tonight I am going to write a short review on a nice little product that we use company wide on a daily basis. The product I am speaking of is called CONNX. So you are now wondering what is CONNX? CONNX provides connection to data sources and legacy applications through open standards across all major platforms. We use CONNX extensively to get data in and out of an RMS database on a VMS server into SQL Server 2005. I will not go into detail on this process to much during this post, I am saving this for later. CONNX can take data out of relational and non relations database systems, transaction systems and legacy applications. Some examples of the compatible systems are ADABAS, DB2, IMS, VSAM-MVS, Informix, Oracle, SYBASE, RMS, PostgreSQL, and SQL Server.

 Installation of CONNX is fairly straighforward and the wizard walks you through most everything. Starting with CONNX 1o, you will need to also have a server or box on the network that can act as the CONNX license server. CONNX also installs a nice little configuration management tool in Windows and comes with a powerful query application called InfoNaut.

I have only had a few issues with putting data back into RMS through CONNX, most of this has been configuration issues on my SQL Server box that seem to be resolved now. There are multiple licensing schemes available through CONNX to fit almost any need. So if you get into a project where you need data in and out of systems that you are not familiar with, look at CONNX and maybe you’ll be surprised.