I'm migrating from VS2015 to VS2017, and updating a repo's solutions to be able to be compatible with VS2017. In the process, I'm also updating the Azure SDK version from 2.7 to 3.0.
I'm setting up a fresh dev environment, and installed Azure SDK 3.0 via VS2017's Azure development workload.
When I opened the solution file in the repo, I got one notice per cloud service project that its Microsoft Azure Tools version was getting upgraded from 2.7 to 2.9...
...and the ProductVersion tag in the corresponding .csproj files was updated from 2.7 to 2.9.
Questions:
Why wasn't this updated to 3.0?
Is there anyway for me to update it
to 3.0 without manually editing the csproj file? I don't see an
option to do so in Properties when I right click the cloud service
projects in Solution Explorer.
Is there some reason I shouldn't be
doing this?
"Microsoft Azure Tools - v2.9" mentioned in your screenshot is just a little misleading.
Underlying reason is that Microsoft hasn't really changed the version number of most components as part of 3.0 SDK release. Even the binaries get installed in the same folder as 2.9.
Good news is that you don't need to do anything special apart from converting the project to target latest version, which you're already getting prompted for.
So once you do convert your project as per the prompt, you're essentially working with SDK 3.0, even though version string says v2.9, because as the links explain, most of the components haven't changed major version number as part of SDK 3.0 version (when comparing with 2.9)
Here are some of the links which talk about this -
Azure SDK for .NET 3.0 Release Summary
No breaking changes to the Azure SDK 3.0 have been introduced in this
release. There is also no upgrade process needed to leverage this SDK
with existing Cloud Service projects. To allow use of the Azure SDK
3.0 without requiring an upgrade process, Azure SDK 3.0 installs to the same directories as Azure SDK 2.9. Most the components did not
change the major version from 2.9 but instead just updated the build
number.
Visual Studio 2017 latest installer does not install Azure SDK 3.0
In this link look at the response from Devin Breshears - MSFT
Azure 3.0 SDK Install Weirdness
An independent blog talking about the same issue.
Related
Where can I find a specific version of Service FabriŃ, I need 5.6 runtime and 2.6 sdk version. Is there any download list for Service Fabric versions?
I found the link https://blogs.msdn.microsoft.com/azureservicefabric/2017/06/20/release-of-sdk-2-6-220-and-runtime-5-6-220-refresh-for-windows , but there no link for downloading this version. Every link leads to the latest version.
I found it!
https://servicefabricsdkstorage.blob.core.windows.net/public-release-notes/Microsoft%20Azure%20Service%20Fabric%20Release%20Notes%20-%20SDK%202.6.220%20-%20Runtime%205.6.220.docx
Here is a link where the downloading links of service fabric Runtime, SDK and VS Tools can be found.
So the algorithm for seeking download links:
Find the release update on Azure
site.(https://blogs.msdn.microsoft.com/azureservicefabric/2017/06/20/release-of-sdk-2-6-220-and-runtime-5-6-220-refresh-for-windows/
in my case)
Find release notes of a specific release.
Download Release Notes
Find Download links at the end of a document.
Can use Web Platform Installer to install different versions of Service Fabric SDK together with runtime. If you don't want to install the corresponding SDK, only runtime, actually you can go to Web Platform Installer's folder to find the package, such as "%LOCALAPPDATA%\Microsoft\Web Platform Installer\installers\ServiceFabricRuntime_6_5_CU5".
According to this article some support for older versions of Azure are going away:
https://azure.microsoft.com/en-us/blog/microsoft-azure-storage-service-version-removal/
We have a vs2008 application that is uploading files to Azure. {Using Azure 1.2 (for VS2008) - Microsoft.WindowsAzure.StorageClient v1.0.0 - Runtime v2.0.50727}.
We can't have this break since we are using this in production.
I need to know if there is a clear way to know if this is going to stop working.
I would really like to know if there is a way to upgrade the vs2008 project to use a compatible version of the StorageClient without migrating the project to vs2015.
Your version of the library should still be supported after the service removal. You can confirm which version of the service you are hitting by running requests through Fiddler and checking the x-ms-version. As you can see in the most recent post regarding our service deprecation, we are only removing version 2009-07-17 and older as of August 1, 2016.
We have two Azure cloud service solutions currently using Storage SDK 2.2. We are upgrading to Storage SDK 2.6 but cannot upgrade and support existing version from the same development environment. If the emulator is upgraded the solution with the older SDK binaries fails. Likewise, the newer SDK binaries do not work with the older emulator.
What is suggested for a mixed SDK version scenario like this? Are separate development environment really required?
My existing project, uses Azure .NET SDK 2.1. I wanted to upgrade the SDK to 2.4, so i dowloaded the latest from here for VS 2012. After successfull installation, when i opened up my solution, the cloud projects did not load. Thats ok, as they have been created using a lower version. So i removed them and created newer cloud projects.
But the thing which astonishes me is, there are many places in the worker role project where its throwing build error as it is not able to find out the assemblies and methods. Is there any easier way to upgrade to sdk 2.4 without making code changes. Which i think is a bad idea to make changes to the stable code, just for SDK upgrade.
When you open a project created using 2.1 SDK and try to open it using 2.4 SDK, you should see the project upgrade dialog which gives you the option to either download 2.1 SDK or convert existing project to target 2.4. Selecting the convert option should upgrade the project to 2.4. Any errors in this process will be reported in the project migration summary report.
If you are not seeing this dialog, then you might still have 2.1 sdk on your machine in addition to 2.4 sdk. In that case, you can go the Azure project properties. That will give you the option to upgrade your project to 2.4.
In regard to the build errors that you are getting for new projects, the error details will help in identifying the root cause.
I am very confused. I had the 1.6 library and then upgraded to 1.7.
Now I see the following:
Windows Azure SDK for Windows 8 and .NET 4(2.0.0.0)
Is this the latest library and is it just for Windows 8? I'm sorry but it's not very clear. When I try to download that it takes me to a web page with a link to download and no application. When I try for help it points me to stackoverflow.
Windows Azure SDK for Windows 8 and .NET 4 (2.0.0.0)
is probably
October 2012 Release (Version 1.8)
which is the latest release as of now (2012-12-04).
The version scheme changed a bit (e.g. storage client dll is now 2.0 because of breaking changes) while other parts remain unchanged/compatible (1.7/1.8) (see Windows Azure SDK and Tools).
The azure SDKs/client libraries should not depend on Windows 8.
You can find all downloads at windowsazure.com