We’ve never had a problem with VS2015, same server, etc. We’re building a .sln file directly from VI. Using VisualStudio2017, only option select is ‘Safe mode’.
I’m not sure if perhaps we’ve installed incorrectly, or maybe MS changed the licensing such that the build server now needs it’s own? We’ve been working around it by a developer going in and re-authenticating with VS… then copying the necessary files into our build users folders… Obviously non-optimal, works for a while then fails requiring redo.
Any suggestions?
I’m guessing you are using devenv rather than msbuild? Unless you have a very good reason to use the VS action (which calls devenv), I would use the MSBuild action instead.
BTW, other than that, you should complain to Microsoft, their online licensing scheme is fraught with problems. The only way to get around that is to purchase a non msdn copy of visual studio (so you get a license key) to install on the build machine.
Thanks, I’ll pass this along… I think we can use msbuild, likely used the VS action because it was there.