I need to be able to use AzCopy on a computer that only has .NET 4.0 available. The only download link I have been able to find is http://aka.ms/downloadazcopy but this points to version 5.1.x which requires .NET 4.5. Does anyone know where I can get an older version or any other workarounds?
Thanks!
Now, Microsoft only provides latest version Azcopy. I search on Google, I could not find older version to download. If you could not upgrade your NET Framework 4.0 version. I suggest you could use Azure CLI 1.0 or Azure CLI 2.0 to manage Azure storage account. Azure cli does not require NET Framework.
Azure CLI 2.0: Our next-generation CLI written in Python, for use with
the Resource Manager deployment model.
Azure CLI 1.0: Our CLI written in Node.js, for use with both the
classic and Resource Managerdeployment models.
Update from comment:
I am using https://github.com/Azure/blobxfer and used py2exe to create a Windows executable I can call from a console app.
Related
I am using Azure DevOps to deploy a .Net Web Application. I wanted to update to the new Os Family which is based on Windows 2019 so i can Update my projects to .net framework version 4.7.2 as seen here. I have updated my cloud service configuration '.cscfg' file to osFamily="6" but when i try to deploy the app even though the Build succeeds i get this error when i reach the Release step in Azure pipeline:
The OS family 6 you are trying to deploy is not supported by the SDK package. The SDK package supported OS families:3,4,5,1,2,98,97. Please try to deploy to a different operating system. To do this specify a different osFamily and/or osVersion in your .cscfg file.
I am using the Hosted VS2017 agent.
According to the error information it indicates that the OS family 6 are not supported by Hosted VS2017 agent.
Based on the link you mentioned that Compatible SDK versions should be Version 2.9.6+.
So my workaround is that you could use the Self-host agent with latest Azure SDK installed. We could download the latest Azure SDK from this link.
or you could have a try to install the Azure SDK on the Host 2017 agent (without test)
You also could give your feedback to Azure Devops team.
We have an Azure based deployment of 'Corda Single ledger N/w' for Corda version 1.0
Azure seems to support deployment only Corda 1.0/2.0 max.
We need to upgrade it to the latest 3.1
Do we have a manual way for doing this please?
Image of parameters.json
If you're looking for getting your VMs deployed with the 3.1 version just download the template from azure, open the parameters.json and specify cordaVersion as seen in maven central, so it would be "3.1-corda".
I am not sure if I download Azure SDK 2.7 will it let me target .NET 4.5.2? Currently I have Azure SDK 4.5 and it does not let me publish when I have a worker role targeting 4.5.2.
Thanks
Worker roles currently do not support .NET 4.5.2 without manual installation.
You can either set up VM access to install .NET 4.5.2 onto the worker role's underlying VM or look at usin a powershell script to install it when your application starts up.
See proof in release notes for SDK 2.6 and instructions to how install .NET on cloud services here.
Azure SDK's currently only allow you to target 4.5.1 in PaaS services. Azure SDK v2.5 and on is able to to target 4.5.2 but only if it is a VM instance
https://msdn.microsoft.com/en-us/library/azure/dn873976.aspx
Is there a way to keep Diagnostics 1.0 but upgrade to Azure SDK 2.5?
We use very simple diagnostics that just writes into Trace (and as a result into storage table). We also deploy our service as a package via Azure portal. Introducing of Diagnostics 1.3 is a quite a breaking change for our process, since it requires PowerShell to deploy Diagnostics extension.
I tried to revert back Cloud configuration files (import Diagnostics module) but it is not working. It seems that I have to stay on SDK 2.4 for now.
Is there a way to keep Diagnostics 1.0 but upgrade to Azure SDK 2.5?
Unfortunately No. If you upgrade your Cloud Services to SDK 2.5, you can't use diagnostics 1.0. You have to use 1.3 version of the diagnostics.
We did the same with our projects and faced more or less the same issues as you faced and had to revert back. What we did was kept SDK 2.5 installed on the machines however our projects still use SDK 2.4 i.e. all referenced libraries in our project are from SDK 2.4.
I already have my azure web role running in cloud using azure sdk 1.6. I want to use sdk 1.7 to try new features. If i install sdk 1.6, can i still manage my old web role?
Windows Azure SDK 1.7 is side by side compatible with Windows Azure SDK 1.6. When you install the SDK and use it to create an application you will be give a chance to choose which SDK you want as below:
On 64bit Windows machine, new SDK 1.7 is installed here:
C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\2012-06
This way you can manage your previous Windows Azure SDK 1.6 based code and try and use new Windows Azure SDK 1.7 based features side by side.
You sure can keep running your Windows Azure Web Role with Windows Azure SDK 1.6 however if you decided to upgrade it to Windows Azure 1.7 based Web Role, then you just need to follow the same steps as you do to any other SDK update.