The 'DefaultConnection-Web.config Connection String' argument cannot be null or empty
Visual Studio-2013Azure WebjobsVisual Studio-2013 Problem Overview
When I deploy my project with "Publish as Azure WebJob" using Visual Studio, I get the error in the title.
Visual Studio-2013 Solutions
Solution 1 - Visual Studio-2013
Fixed by removing the following markup from the .pubxml file. You must exit/restart VS after removing the markup (or VS will add it back in).
<ItemGroup>
<MSDeployParameterValue Include="$(DeployParameterPrefix)DefaultConnection-Web.config Connection String" />
</ItemGroup>
Solution 2 - Visual Studio-2013
Reason of the problem is one of the followings:
- Change the name of the connection string in the
web.config
. - Add a new connection string in the
web.config
Solution
- Select the website project, right-click on it, and click publish.
-
Press the settings link and from the pop-up window select the 'Settings' Tab
-
Uncheck the
use this connection string at runtime
from all your connection strings.
- Click the
Save
button to close the window. (No need to restart Visual Studio) - Try to publish the website again, and it should publish without a problem.
- You can reconfigure the settings as it was previously, the unchecking just triggers VS to regenerate the .pubxml file, So you are not forced to change your settings at all.
NOTE
I am using VS 2017 (and according to the comments this also work in Visual Studio 2013)
Just for Note
After I did the previous steps, I noticed that the .pubxml file changed automatically. here is the difference which has been made (automatically without any interference from me)
So I think this is a better way because it is easier for the developer and also it let the visual studio to solve its problems himself, without forcing it into a specific thing.
Solution 3 - Visual Studio-2013
Create a Parameters.xml file in the Project root with the following content:
<?xml version="1.0" encoding="utf-8" ?>
<parameters>
<parameter name="DefaultConnection-Web.config Connection String"
description="DefaultConnection"
defaultValue="Server=tcp:x.database.windows.net,1433;Database=x_db;User ID=x@y;Password=z;Trusted_Connection=False;etc." tags="" />
</parameters>
All the other missing config elements can be added here as well.
Solution 4 - Visual Studio-2013
I have Visual Studio 2015 Update 3 and i was facing the same issue. The solution i found that is working for me is the following:
-
Open *.pubxml file under properties -> publish profiles.
-
Look for the Path attribute under PublishDatabaseSettings section:
-
Set Path attribute value to the following:
-
Delete the existing webjob deployment in Azure Job Collection Scheduler.
-
Re-Deploy the webjob, Re-run the webjob from the scheduler and it starts working with no issues!
Hope this helps.