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?
Related
I am required to write an Azure Function, with HTTP triggers. My problem is, when I choose Azure Functions template in Visual Studio 2017, it just creates an empty project with two files, host.json and local.setting.json, which makes me believe that I have version 2 of the Azure Functions installed.
When I try and compile this version of the Azure Functions I have installed, I get a message saying that I need .Net Frameworik 4.7.2 installed, and I cannot install this framework version on my Windows 10 version.
How can I downgrade or install the Azure Functions version 1?
My Environment:
Windows 10 (Build 10240)
Visual Studio 2017 Professional (version 15.5.4)
Any help?
I recommend you to update your Visual Studio 2017 to 15.8.1 if possible.
15.5.4 seems too old and doesn't work with latest Azure Functions and Web Jobs Tools.
Many templates support in latest Azure function extension.
While you are creating a new Azure Functions project in Visual Studio, you get asked which version (v1 or v2) you want. The structure of the project (the two files you mention) are the same for both versions.
The difference is that v1 is targeting full .NET Framework 4.6+, while v2 is targeting .NET Standard 2.x.
I've just tried with VS 15.8 and v1 project template is targeting 4.6.1 by default, so this version should be enough.
You can try to create function app from command line using func command. To install CLI I recommend use of chocolatey and simply type choco install azure-functions-core-tools.
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.
I'm getting this message after upgrading to Azure Storage Emulator 4.6 and v8.0.0 of WindowsAzure.Storage.
I have spent two days trying to get this to work including reformatting and installing all dev tools on two machines. This has happened with THREE previous Microsoft releases, either the Azure SDK, or the emulator or some combination of the two is broken.
I managed to get things working with the previous version (again) with the following steps:
Uninstalled v4.6 of the Storage Emulator.
Deleted database files (mdf, ldf) under C:\Users\\
Downloaded and installed v4.5 Storage Emulator.
Reverted WindowsAzure.Storage to v7.2.1 (via NuGet)
Did a search for "8.0.0" in the solution to identify any remaining binding redirects that use v8.0.0 of WindowsAzure.Storage. Delete these if any are found.
This got me up and running again until there is a proper solution to use the latest version of the above libraries.
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.
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