Home → Questions →

Visual studio 2017

• Edit

vincent

Apr 17, 2017 @ 08:09 PM

I am trying to switch from vs 2015 to vs 2017, and of course, it is complaining missing assembly reference. Those assembly maybe already installed on the machine, but I am trying to get some pointers on where are they now and what version are installed.

- What version is the Microsoft.WindowsAzure.Diagnostics installed? I was using version 2.5.0.0
- Where is the Windows Azure Tools? On my local machine it is in C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\Windows Azure Tools\2.9

1. Support Staff 1 Posted by Feodor Fitsner on Apr 18, 2017 @ 01:40 AM

   

   Hi Vincent,

   Visual Studio 2017 image has Azure SDK 2.9 (3.0) installed. That's the only version available there - no previous versions installed.

   I'm not sure that C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\Windows Azure Tools\2.9 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.

   Look at this test Azure CS project created in VS 2017 and built on Visual Studio 2017 image: https://ci.appveyor.com/project/appveyor-tests/azurecloudservicevs2017

   SDK is in C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.9\ folder and Azure SDK .targets are in C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Windows Azure Tools\2.9

   Are you building on Visual Studio 2017 image?

   • Edit

2. 2 Posted by vincent on Apr 22, 2017 @ 07:46 AM

   

   Thanks. That path information helps.
   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?

   Starting SQL Server 2012 SP1 Express
   Start-Service : Cannot find any service with service name 'MSSQL$SQL2012SP1'.
   At line:1 char:1
   + Start-Service 'MSSQL$SQL2012SP1'
   + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       + CategoryInfo : ObjectNotFound: (MSSQL$SQL2012SP1:String) [Start-Service], ServiceCommandException
       + FullyQualifiedErrorId : NoServiceFoundForGivenName,Microsoft.PowerShell.Commands.StartServiceCommand

   • Edit

3. 3 Posted by vincent on Apr 22, 2017 @ 08:51 PM

   

   Nevermind. Change the test connection string to sql 2014 and it is working now.

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on Apr 22, 2017 @ 08:55 PM

   

   Yep, there are only SQL 2014 and 2016 installed on VS 2017 image.

   • Edit

5. vincent closed this discussion on Apr 23, 2017 @ 04:55 AM.