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.
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.
I am trying to update a cloud service to use .NET 4.6. I changing the osFamily="4" to osFamily="5" in the .cscfg file as specified here: https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-guestos-update-matrix
Looking at my file system I have this SDK version installed:
C:\Program Files\Microsoft SDKs\Azure.NET SDK\v2.9
Looking at Web PI, I have these installed:
VS Community 2105 with Azure SDK - 2.9.6
VS Community 2105 with Azure SDK - 3.0
Microsoft Azure SDK for .NET (VS 2015) - 2.9.6
Microsoft Azure SDK for .NET (VS 2015) - 3.0
I normally use Powershell cmdlets to deploy using New-AzureDeployment/Set-AzureDeployment from a build & deployment server. I will occasionally deploy from my desktop using powershell for testing.
If I leave the osFamily="4" unchanged and deploy with Powershell everything works as expected.
If I use VS2015 and the Publish Azure Application tool to do the deployment it succeeds as expected if I choose either osFamily="4" or osFamily="5".
Checking which module is used:
C:\> (Get-Command Set-AzureDeployment).Module.Path
C:\Program Files\WindowsPowerShell\Modules\Azure\3.8.0\Azure.psm1
Running the deployment Set-AzureDeployment (given an existing package has been deployed) gives me the following error -
Set-AzureDeployment : BadRequest : The OS family 5 you are trying to deploy is not supported by the SDK package. The SDK package supported OS families:3,4,1,2,98. Please try to deploy to a different operating system. To do this specify a different osFamily and/or osVersion in your .cscfg file.
I don't see which SDK "package" the commandlet is complaining about...any ideas?
Try using a newer version of the 2.9 Azure Authoring Tools.
I reproduced this problem with Azure Authoring Tools 2.9.1, but remedied it by upgrading to version 2.9.5.3. Actually it's mentioned as fixed in the release notes for Azure '3.0' SDK (download link):
Visual Studio now supports deploying Cloud Services to OS Family 5
(Windows Server 2016) virtual machines. For existing cloud services,
you can change your settings to target the new OS Family. When
creating new cloud services, if you choose to create the service using
.net 4.6 or higher, it will default the service to use OS Family 5.
For more information, you can review the Guest OS Family support
table.
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
I am a beginner in Azure. I had a soln which was using the old version of SDK 2.1 and now have upgraded to 2.6 on my local. I use Visual Studio Team Services to deploy it on the cloud(which has the old version). All is working fine. So I have deployed to cloud using Team Services. But the cloud service still shows the old version. Is there any way I can check anything to see of the upgraded version 2.6 has been transitioned to the cloud service ?
Once you have installed the latest sdk on your machine you will still have to upgrade your project within Visual Studio.
To do this: Within your solution select the Azure Cloud Service project (the one that contains the ServiceDefinition.csdef etc). Press Alt+Enter or right-click and from the context menu select properties (found at the very bottom).
This will open the document page shown below and will display the version of the Azure sdk your project is using. If a newer version is found on your machine you will see an upgrade button.
I'm creating an Azure web role "manually". (I.e. using cspack.exe and deploying with Powershell rather than using Visual Studio.)
My Web Role SDK version shows as 2.2.6492.2 but I would like to upgrade it to 2.4. I have tried changing the schemaVersion in the .cscfg file to 2014-06.2.4 but this didn't work.
Turns out I was using cspack.exe v2.2 - upgrading to v2.4 upgraded the SDK in the role.