I want to be able to use dedicated or co-located caching in my Azure web roles.
The problem is that the application I am migrating uses HttpSessionState extensively. I don't want to change all of this code because:
This is time consuming (especially with testing)
I can't enforce developers from using HttpSessionState
I want to avoid vendor locking as much as possible
Is there no session provider for dedicated and co-located caching so that I can keep existing code as is?
I fixed the problem. To use the ASP.NET Session State in the dedicated or co-located Azure caching, the following session provider needs to be setup in the web.config:
<sessionState mode="Custom" customProvider="AFCacheSessionStateProvider">
<providers>
<add name="AFCacheSessionStateProvider"
type="Microsoft.Web.DistributedCache.DistributedCacheSessionStateStoreProvider, Microsoft.Web.DistributedCache"
cacheName="default" dataCacheClientName="default"
applicationName="AFCacheSessionState"
/>
</providers>
</sessionState>
Related
I have installed elmah to my asp.net mvc application using below nuget package
<package id="Elmah.AzureTableStorage" version="1.0.0.0" targetFramework="net452" />
Also i have configured Azure storage connection to store logs in to Azure tables as below
<add name="ElmahAzureTableStorage" connectionString="{my connection string}" />
Now it's storing all error logs in Elmah table in Azure table storage , I would like to keep local & live error logs in different folder so is there any way i can define to use which table according to diff local & live env (web.config & web.release.config)?
You should use web.config transformation for this, like described here: Use multiple logs for different environments. The article uses elmah.io as an example, but the approach is similar when using Azure table storage.
Basically, you need to configure the local environment in your web.config and "override" the ElmahAzureTableStorage setting in web.release.config like this:
<add
key="ElmahAzureTableStorage"
value="{my live connection string}"
xdt:Transform="SetAttributes"
xdt:Locator="Match(key)"/>
With most Azure services I can run an emulator on my local machine, for example the storage emulator. This allows me to store the credentials to my real azure storage account as an app setting on my azure web site. And locally I have the credentials to the emulator in my web.config.
But how to achieve the same kind of security with Azure DocumentDB? I would prefer not to store the credentials in my local web.config, but at the same time I need to be able to run the application locally when developing. As I understand there is no emulator for the DocumentDB? And the endpoint and auth key is the same for all DocumentDB's I create?
So, to sum up my question, what is the best practice to handle the auth key / end point when developing and using Azure DocumentDB?
You are doing the right thing by storing your connection strings in your Azure Website environment so they are not in your web.config and therefore not in your source control system. And your local development process works well for you only because you are using the emulator which doesn't require any credentials. That is not always going to be the case though as you pointed out with Document DB and potentially with other resources you may be using to store data.
The guidance for storing and deploying app settings and connection strings is to keep those in separate config files locally that are never checked into your source control system. Then, in your web.config file, reference these files. This keeps the confidential information out of your web.config.
For example, for connection strings it would be something like this:
<connectionStrings configSource="ConnectionStrings.config">
</connectionStrings>
For app settings it would be something like this:
<appSettings file="..\..\AppSettingsSecrets.config">
<add key="webpages:Version" value="3.0.0.0" />
<add key="webpages:Enabled" value="false" />
...
</appSettings>
More information on this technique is available here.
Another alternative is to store the key as an environment variable and get your code to read it.
On another note, your development environment should have a separate docdb, one that is not your production environment. Since docdb does not offer an emulator and no free-tier, this leads to higher costs for development.
Is it possible to a custom configuration section inside of an Azure Cloud Service Configuration, the same way you would in a regular ASP.NET website?
I.e in a regular ASP.NET site your Web.Config would have something like this:
<configuration>
<configSections>
<section name="myCustomConfig" type="MyNamespace.MyType" />
</configSections>
<myCustomConfig someProperty="someValue" />
</configuration>
How is this done in Cloud Services and shared across multiple different roles?
At this time I do not believe this is possible. There is a post for it on user voice you can vote up: http://www.mygreatwindowsazureidea.com/forums/169386-cloud-services-web-and-worker-role-/suggestions/459944-enable-custom-configuration-sections-in-csdef-cscf.
As a way around this you could put configuration into a file that is stored in BLOB storage. On start up, or when it is needed, all instances could then go pull the file to get the configuration. To deal with changes to the configuration you could either have the instances pulling the configuration from time to time as a refresher, or you could tap into the environment changed event in RoleEntryPoint that is used to detect changes to the Service Configuration. Add a setting to the service configuration that is a version number of your shared config file or something, just anything that could be modified to trigger the RoleEnvironment.Changing event.
I am trying to understand how I can configure my .NET website to display each domain or groups of domains as Applications in the New Relic RPM console.
There is an article explaining here how to do it for PHP
https://newrelic.com/docs/php/per-directory-settings
Applications can be named individually in the application's web config file. This is done by adding the following to the <appSettings> element:
<appSettings>
<add key="NewRelic.AppName" value="my_web_app" />
<add key="NewRelic.AgentEnabled" value="true" />
</appSettings>
Multiple instances of an application can report to the same name in the New Relic UI by giving each application instance the same name as shown above.
Of course, you can separate applications by giving them different names.
You can use this naming feature to group application instances by name as you need. Your application instances can be running on the same server, on different servers, or on a mix of these.
See this page for some additional information on application naming.
Note that you can also enable/disable monitoring of an application or application instance using the NewRelic.AgentEnabled key in the app settings section.
At this time, the .NET agent doesn't support differentiating which
application to report to based on the hostname of each request.
https://discuss.newrelic.com/t/report-websites-or-applications-running-in-the-same-iis-app-pool-as-different-new-relic-applications/36828
UPDATE December 2017: Please go to the URL above and vote for the feature if you think this feature would be useful.
I'm building a Node.js app to be deployed as an Azure Cloud Service Worker Role.
As a good practice, I like keep all sensitive info (API keys, etc) out of my repos. My usual solution for this is to add sensitive info as environment variables, and have my app access those.
In the (relatively new) Azure Websites, this is easily done through the "app settings" section of the "Configure" tab. Add new settings and grab them in Node.js with process.env.<setting key>. These settings persist across updates and deployments.
In Azure Cloud Services, however, this doesn't seem to be the case. I've added "Configuration Settings" to my ServiceConfiguration.Cloud.cscfg:
<ConfigurationSettings>
<Setting name="API_KEY_1" value="" />
<Setting name="API_KEY_2" value="" />
</ConfigurationSettings>
...and my ServiceDefinition.csdef:
<ConfigurationSettings>
<Setting name="API_KEY_1" />
<Setting name="API_KEY_2" />
</ConfigurationSettings>
When I deployed, these settings became editable through the web portal, and I added their values.
When I redeploy, however, the settings are overwritten. The only way I can see to keep their appropriate values is to add the values to the .cscfg. But that would mean committing this info into my repo.
Is there a solution I'm missing?
General approach I would use it to put the settings into a storage account and then have a cscfg setting that targets the storage account. On startup, you can read the values out of the storage account and keep them locally in whatever manner you need them.
That aside, if you wish to continue using the cscfg file, you can keep multiple copies of that file and just deploy with the correct version.