Clever Geek Handbook

"The license for Visual Studio has expired." when compiled with Visual Studio from a TFS assembly

I need to create SSIS projects (.dtproj) on our build server. They are not supported by msbuild, so I need to use Visual Studio to do this. Wisdom points out that I don't need a new VS license for this ( Is a separate Visual Studio license needed for the build machine? ). I went to the build server as I did and registered Visual Studio. But I don't know how to tell the build agents to use my Visual Studio license. Using TFS2015, vNext build agents (not XAML).

I am calling C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com blah.sln /build Release

from a TFS build.

2017-05-02T21:56:08.6745925Z Microsoft Visual Studio 2015 Version 14.0.25420.1.
2017-05-02T21:56:08.6745925Z Copyright (C) Microsoft Corp. All rights reserved.
2017-05-02T21:56:08.6745925Z The license for Visual Studio has expired.
2017-05-02T21:56:09.2986224Z The evaluation period for this product has ended.
+3


source to share


2 answers


Found it out. If I register Visual Studio as me, then I can build. If I go to MSDN and get a product key ( https://msdn.microsoft.com/en-us/subscriptions/keys/ ) and then in Visual Studio go to the Unlock Product Key section and enter that key, now anyone (including the TFS build agent) can build.



+2


source


We had a similar problem. The exact scenario we are using devenv.com

because we are building SSIS projects.

It differs only in that we are using Visual Studio Team System Agents for the online TFS build offer and that we were unable to obtain the key using our MSDN licensing. Instead, we'll get a popup message dialog boxA product key is not offered with this edition of Visual Studio. To unlock the product, you must sign in using the login associated with your active Visual Studio subscription. By signing in, your IDE settings will sync across devices, and you can connect to online developer services.

We had to uninstall the agent under an account NT AUTHORITY\NETWORK SERVICE

and then reinstall it under an account where we could log into that account, open Visual Studio and have one of us sign-in

in the Visual Studio client with their credentials.



This fixed the issue and now our assemblies are shutting down under the service account.

Steps

  • Create a local account or use a domain account like domain\tfsservice

  • Sign in to the assembly with this account, start Visual Studio, sign-in

    in the Visual Studio client, using the credentials of someone with a valid license.
  • Reconfigure the agent to 1st uninstall it via config.cmd remove

    command line administrator
  • Then use 2 config.cmd

    to reconfigure the agent using the local or domain account instead of the accountNT AUTHORITY\NETWORK SERVICE

+1


source






More articles:


All Articles