Geek asks and answers

Why are some Azure instances not present on Azure instances?

An Azure role is likely to need a set of Azure-specific .NET collections, such as Microsoft.WindowsAzure.ServiceRuntimeand Microsoft.WindowsAzure.StorageClient. It turns out the latter is not in the GAC on Azure instances , so I need to set "Copy local" to "True" in the Visual Studio project so that it falls into the service package and deploys to Azure. If I do not do this, there is no assembly, and the missing dependency will prevent my role from starting.

It makes no sense to me. Either it's just a mistake, or I'm not getting the big picture.

Is there a good reason why key assemblies are not present in Azure GAC instances and should I wear them with my service pack?

+3
source share
2 answers

These key Azure assemblies are not part of the .NET Framework - why they are not in the GAC. Perhaps in the future they will be added to the .NET Framework.

Azure is not intended to run only .NET code. People use it for other platforms like Java, PHP, node.js, python, etc. It would not make sense to add assemblies that are specific to the implementation of .NET Azure in instances of the VM role.

Yes - it was also a nuisance when I first started working on Azure, but the same is true if you published it locally on a machine without the Azure SDK.

+3
source

Is there a good reason why key assemblies are not present in Azure GAC instances and should I wear them with my service pack?

, , , ​​. - . Windows Azure. , . , , Web/worker Windows Azure, true. , , .

,

Ming Xu.

0

More articles:


All Articles