For two days I’ve been wondering why NUnit wouldn’t see my new tests I added. The answer was: I have too much code. Well, that is, I have too many copies of the source in various directories.
Unlike Visual Studio (or Express Editions), NUnit saves the full paths to the DLL/Project. Because I moved the code off my thumb drive to another drive, it still held the old path. And of course the only difference between the two paths was the leading drive letter.
So naturally it’s all NUnit’s fault, how am I expected to know that the paths didn’t change? Shouldn’t it update automatically… Oh, boy.
Although, with different people running the code from different computers, this will definitely come up again. Maybe we should have a tool to mount a drive to any folder so everyone can have, say, an L drive for running, debugging, and checking in/out code. I’ll have to remember to find one…
[...] After my snafu with NUnit, I decided to look into ways of avoiding this pain. Googling found a command line utility called subst. From that I’m creating a GUI wrapper around it, so that you can keep the drive mapping after a reboot. It will be smart enough to be able to store multiple mappings, as well as seeing the available drives, and storing the settings in a config for use in other computers. It’s nearing completion, so I’ll be able to eat my own cooking soon. [...]