tag:help.appveyor.com,2012-11-13:/discussions/questions/3677-visual-studio-2017AppVeyor: Discussion 2017-04-23T04:55:30Ztag:help.appveyor.com,2012-11-13:Comment/423757692017-04-18T01:40:24Z2017-04-18T01:40:24ZVisual studio 2017<div><p>Hi Vincent,</p>
<p><code>Visual Studio 2017</code> image has Azure SDK 2.9 (3.0) installed. That's the only version available there - no previous versions installed.</p>
<p>I'm not sure that <code>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\Windows Azure Tools\2.9</code> is correct path to SDK for VS 2017. On my dev machine I have VS 2017 installed with Azure support, but that folder does not exist.</p>
<p>Look at this test Azure CS project created in VS 2017 and built on <code>Visual Studio 2017</code> image: <a href="https://ci.appveyor.com/project/appveyor-tests/azurecloudservicevs2017">https://ci.appveyor.com/project/appveyor-tests/azurecloudservicevs2017</a></p>
<p>SDK is in <code>C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.9\</code> folder and Azure SDK <code>.targets</code> are in <code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Windows Azure Tools\2.9</code></p>
<p>Are you building on <code>Visual Studio 2017</code> image?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/423757692017-04-22T07:46:43Z2017-04-22T07:46:43ZVisual studio 2017<div><p>Thanks. That path information helps.<br>
Yes, I am using the visual studio 2017 image. I do get an error for the sql 2012 express setup. Is sql 2012 express still supported?</p>
<p>Starting SQL Server 2012 SP1 Express<br>
Start-Service : Cannot find any service with service name 'MSSQL$SQL2012SP1'.<br>
At line:1 char:1<br>
+ Start-Service 'MSSQL$SQL2012SP1' + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (MSSQL$SQL2012SP1:String) [Start-Service], ServiceCommandException + FullyQualifiedErrorId : NoServiceFoundForGivenName,Microsoft.PowerShell.Commands.StartServiceCommand</p></div>vincenttag:help.appveyor.com,2012-11-13:Comment/423757692017-04-22T20:51:51Z2017-04-22T20:51:51ZVisual studio 2017<div><p>Nevermind. Change the test connection string to sql 2014 and it is working now.</p></div>vincenttag:help.appveyor.com,2012-11-13:Comment/423757692017-04-22T20:55:15Z2017-04-22T20:55:15ZVisual studio 2017<div><p>Yep, there are only SQL 2014 and 2016 installed on VS 2017 image.</p></div>Feodor Fitsner