We have moved to GitHub Issues
Created by Pieter Dubelaar 11 Feb 2016, 16:19:06 Updated by Lars-Erik Aabech 22 Mar 2016, 09:31:47
I've run into this using Umbraco 7.3.7. If you create a blank Visual Studio project, download Umbraco via NuGet, and create an Azure publish profile, the deployment fails throwing an error "The 'Connection String' argument cannot be null or empty."
Steps to reproduce: In Azure:
In Visual Studio 2015:
After the project is created:
MSBuild will now choke on the fact 'connectionString' and 'providerName' are empty in the web.config:
The error given in Visual Studio:2> C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4276,5): Error : The 'Connection String' argument cannot be null or empty.
I naively added a connection string, assuming (hoping) the installer would pick up on the fact the connected database did not have Umbraco installed (and the fact
The best way to publish the site directly to Azure, seems to be to remove the umbracoDbDSN keys altogether.
@pieter you need to do 2 things before you can deploy: 1) build the solution (as it says in the readme. 2) start the site locally so that the setup runs. The setup will set the umbracoConfigurationStatus and the connectionstring (you can enter the connectionstring to the db you already have and it will add all the tables etc)
@vnbaaij thanks for the reply! Part of the reason for submitting this exception is to help Umbraco become more resilient to misuse. There obviously is 'the' right way to install it. But we make assumptions on how to deploy a system. The more accepting a system is of installation procedures other than the right way, the more mature a system feels. This is more of a 'feature request' - change the CMS in such a way that common mistakes don't lead to Yellow Screens Of Death, but are gracefully accepted. A quick win would be to sanity check the state of both the web.config (both umbracoConfigurationStatus and connectionString, not just the first) as well as the database the connection string links to.
Solution for this is to add
Project\PropertyGroup in the .pubxml file under properties\publishprofiles, and
Not much HQ can do to mitigate this.
Backwards Compatible: True
Due in version: