CODEWITHSUNDEEP
c#.netazureazure-role-environmentazure-service-runtime
Ross Vernal
Ross Vernal

Reputation: 493

Detecting if a .NET app is running in Azure or on a non-Azure environment

We are currently moving some instances of our application to Azure, but will still maintain backwards compatibility with existing instances which are not Azure hosted.

Is there a good way to detect the environment without installing the SDK on the non-Azure production server?

I've tried using:

if (RoleEnvironment.IsAvailable)

from Microsoft.WindowsAzure.ServiceRuntime, and it works perfectly locally, and in Azure. However, I need to set the Microsoft.WindowsAzure.ServiceRuntime.dll to CopyLocal, and even then I get:

Could not load file or assembly 'msshrtmi, Version=2.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies

There doesn't seem to be a NuGet package, and I don't want to manually copy the msshrtmi dll about.

Perhaps there's a way of detecting without the dependency on Microsoft.WindowsAzure.ServiceRuntime?

Upvotes: 12

Views: 4136

Answers (4)

Nilesh Gajare
Nilesh Gajare

Reputation: 6398

You can check using if(RoleEnvironment.IsEmulated)

Upvotes: 2

Sandrino Di Mattia
Sandrino Di Mattia

Reputation: 24870

You can verify if the RoleRoot environment variable is present. If it is, your application is running in a Web or Worker Role.

Upvotes: 3

Matthew Steeples
Matthew Steeples

Reputation: 8073

You could try calling Assembly.Load on the msshrtmi, Version=2.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 assembly, and if it fails then don't try and call the RoleEnvironment.IsAvailable method (as you know you're definitely not running on Azure).

Alternatively you could try using the machinename, as all Azure Instances start off with "RD"

Upvotes: 0

greg84
greg84

Reputation: 7629

Unfortunately the easiest way to resolve this is to copy the msshrtmi.dll file from:

C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\{version}\bin\runtimes\base\x64

I know it's not very nice copying DLLs around, but this is the only one you'll need to prevent the error, and its tied to the SDK version you're using, so won't change until you update the SDK.

A viable alternative would be to add a config value in appSettings and apply a config transform when you build the application for Azure.

Upvotes: 6

Related Questions