![]() Such script for my company which at build time adds elements into projects so we don't have to have every single dependency inside the same solution). The problem of not waiting for a shared dependency to build and launching multiple instances of it happens only in VS2017 and only if projects in solution utilize custom MSBuild targets that bring additional project references during build time (I wrote This almost always leads to multiple processes trying to access the same file and build ultimately failing. Hopefully I've now created a repro issue that should reproduce it on most other computers as well. I've spent the better part of last two weeks trying to pinpoint down a build synchronization issue that was brought by using VS2017 instead of VS2015: build steps of one shared project can be, under some conditions, launched two or more times during the
0 Comments
Leave a Reply. |