CODEWITHSUNDEEP
azureazure-web-app-servicemembershipreboot
nachojammers
nachojammers

Reputation: 1225

Connection strings set in Azure portal not being picked up by application

I have a webapp deployed to an Azure Web App. In the webapp I am using MembershipReboot, with Entity Framework. The Sql Server database is also in Azure.

It is deployed via BitBucket integration and continuous deployment, in a staging slot.

As part of the build process, a web.config transfrom, changes the connection string value to "dummy".

I set this the connection string, named MembershipReboot, in the Azure portal.

When I browse to the application, I get this error:

Format of the initialization string does not conform to specification starting at index 0.

If I change the connection string in the web.config, to be the Sql Azure connection string the app loads fine. If I set it back to "dummy" then I get the above error.

This indicates to me that the connection string set in the Azure portal isn't being picked up by the application.

I created this Azure enviromnent using the ARM template deploy, mixed with some Azure powershell commands. I've tried creating the environment by hand too, with the same issue.

Any ideas on what to look at next?

edit: Just to say, the correct connection string is viewable within Kudu.

Upvotes: 0

Views: 752

Answers (1)

nachojammers
nachojammers

Reputation: 1225

Managed to fix this.

It was due to StructureMap being invoked, and creating a database context (via global.asax), before the environment was providing the correct connection string.

In our case, the app was mixing Owin startup and global.asax Application_Start, we had to move the global.asax startup into the Owin startup, and not allow the database context to be created during that startup. I suspect we could have just done the latter.

Upvotes: 0

Related Questions