tag:help.appveyor.com,2012-11-13:/discussions/problems/5369-the-license-for-visual-studio-has-expired-previous-visual-studio-2015AppVeyor: Discussion 2017-02-14T17:00:00Ztag:help.appveyor.com,2012-11-13:Comment/409014862016-10-03T21:39:48Z2016-10-03T21:39:48ZThe license for Visual Studio has expired - Previous Visual Studio 2015<div><p>Hi Jeff,</p>
<p>We'd like to reproduce the issue here on the current image.
"Previous" won't always work as with the next update the current
image will become previous and the build will be finally broken. We
have to understand root cause and fix it. Other customers would
benefit too.</p>
<p>How does <code>devenv</code> command look like in your case? Or
maybe you can do a simple repro project in a public repository?
That would help a lot. Thank you!</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/409014862016-10-04T14:08:02Z2016-10-04T14:08:02ZThe license for Visual Studio has expired - Previous Visual Studio 2015<div><p>Here is the command line with sensitive information replaced
with client.project</p>
<p>"C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\devenv.com" Client.Project.Setup.sln /build Debug
/project
Installers\Douglas.Fumiguide.Setup\Client.Project.Setup.vdproj
/projectconfig Debug /Out errorFile.txt</p>
<p>I understand with the previous, current image changing. That's
why I made that other post about previous functionality being
broken because once the images progress I'd be completely locked
out.</p></div>Jeff Klawitertag:help.appveyor.com,2012-11-13:Comment/409014862016-10-04T14:11:26Z2016-10-04T14:11:26ZThe license for Visual Studio has expired - Previous Visual Studio 2015<div><p>I just looked back on previous builds and Visual Studio was
putting up messages of how long the license was valid for. On
September 29th it said</p>
<blockquote>
<p>The license for Visual Studio expires today.</p>
</blockquote>
<p>And indeed on September 28th it had</p>
<blockquote>
<p>The license for Visual Studio expires in 1 day</p>
</blockquote></div>Jeff Klawitertag:help.appveyor.com,2012-11-13:Comment/409014862016-10-05T01:19:50Z2016-10-05T01:19:50ZThe license for Visual Studio has expired - Previous Visual Studio 2015<div><p>Hi Jeff,</p>
<p>We believe we've fixed the issue with building vdproj projects
(<a href="https://ci.appveyor.com/project/appveyor-tests/vdproj-test/build/1.0.5">test
build results</a>). We are going to deploy updated build worker
image later this week/early next week.</p>
<p>In the meantime, you can run your builds on Google Compute
Engine (GCE) environment. I added a new <code>Visual Studio 2015 -
GCE</code> build worker image under <code>TheNerdery</code>
account. If you use <code>appveyor.yml</code> then add <code>image:
Visual Studio 2015 - GCE</code> to run that project on GCE;
otherwise select image on Environment tab of AppVeyor project
settings. Note, that build on GCE starts in 3-4 minutes - this is
the time required to provision a new VM.</p>
<p>Hope that helps. Let me know how that worked.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/409014862016-10-05T13:26:57Z2016-10-05T13:26:57ZThe license for Visual Studio has expired - Previous Visual Studio 2015<div><p>Feoder,</p>
<p>That worked perfectly.</p>
<p>Does the fix for vdproj include the registry entry so I do not
need to edit it anymore?</p></div>Jeff Klawitertag:help.appveyor.com,2012-11-13:Comment/409014862016-10-05T20:36:06Z2016-10-05T20:36:06ZThe license for Visual Studio has expired - Previous Visual Studio 2015<div><p>Great to hear that!</p>
<p>Registry fix is not yet applied, but we'll make sure it's
applied in the next image update.</p></div>Feodor Fitsner