I was able to track down the problem – jom had a dependency on a DLL (I think it was mspdb100.dll) which only existed in Visual Studio 2010, and so when I switched my path to point to Visual Studio 2013 it couldn’t find the DLL. I don’t think it’s a good idea to have jom rely on external dependencies like this (or if it must, those DLLs should be part of the installation) …
↧