I was getting weird errors about not being able to resolve task dependencies. The executable still exists with VS2017 as well but it doesn’t work quiet right in all scenarios. ![]() I typically run MSBuild.exe from the following path as it has worked for several versions of VS:Ĭ:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild This cuts down the feedback time for results of project changes I make as opposed to waiting for the TFS build or worse the CD pipeline to complete. I routinely test my builds by running MSBuild.exe manually from the commandline. In general, that has worked out really well but I have had one nagging issue. I decided to not install older versions of Visual Studio and only install VS2017. ![]() ![]() I recently paved and installed Windows 10 on my work laptop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |