mandogroup/ProductionSchedule — pull request #1 by dpen2000 (2013-11-12 09:53:50+00:00)
Title: Deploy to azure fix

I'm able to deploy to azure Websites and have it override a connection string in the website from the portal after these changes.
I've changed the database initializer transform to refer to our context etc.
I've changed the Connection string name to ProductionScheduleContext. In my testing, I haven't been able to create a new connection string just using it in the portal (I suspect it lacks the information specified in the providerName attribute): it has to override one. I've also tested overriding one named DefaultConnection and this still results in an error about connecting to the instance.

To deploy with these changes, there needs to be a connection string named ProductionScheduleContext under the Configure tab for the Website in the portal.