Code

Vstest says, “Path too long”? I fix.

A weird thing started happening on my TFS build server recently. When it came time to run the unit tests, the build would fail with:

The specified path, file name, or both are too long. The    fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

For reference, here’s the standard testing step that was failing.. Note the “Test Assembly” parameter.. Nothing out of the ordinary there.

So I dug in..Read More »Vstest says, “Path too long”? I fix.

XSD.exe and imports – a solution

If you’re reading this right now, it’s likely because you just discovered that XSD.exe doesn’t honor import declarations within XSD files.

It sure caught me and several others by surprise.

The fix, it turns out, is to manually specify each XSD that the primary XSD requires. Something like xsd.exe primary.xsd imported.xsd another.xsd

In my case, my primary XSD file imported several XSD files… those those imported XSD files imported their own XSD files.. And putting that nasty command line together manually is just too far below my pay grade. Read More »XSD.exe and imports – a solution