Monospaced Programming Fonts with Ligatures
4 days ago
It's rare that a projectGuid will ever change. In this case, we had to make the MyClassLibrary a VSTO plug in for word. I didn't do the conversion (and wouldn't have caught something like the projectGuid changing if I did), but for some bizarre reason we ended up with a new projectGuid for MyClassLibrary.
<projectReference include="..\MyClassLibrary.vbproj">& >
The fix was simple, all I had to do was copy the correct Guid to the
copy "$(TargetPath)" "$(SolutionDir)MyApp\bin\Debug"work on the build machine, you can do something like this:
IF EXIST "$(SolutionDir)MyApp\bin\Debug" copy "$(TargetPath)" "$(SolutionDir)MyApp\bin\Debug"That should work in most cases (your mileage may vary).
Will this application ever need to support multiple languages?More often than not, this answer will be "No, that's crazy. Don't add support for that. It will take way too much time".