Can not publish since moving to VS 2019

Question

I have recently uninstalled VS 2017 and installed VS 2019.

When I publish my website via Web Deploy, if fails with 2 error messages

Failed to load publish certificate dialog due to error of Object reference not set to an instance of an object. MyWebsite.Ui

Web deployment task failed. (Connected to the remote computer ("example.com") using the specified process ("Web Management Service"), but could not verify the server’s certificate. If you trust the server, connect again and allow untrusted certificates. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CERTIFICATE_VALIDATION_FAILED.)

I'm totally clueless on how I can solve this...

Edit

As per the comments, there is a question which is the same, but that question is about Azure. I'm not connecting to anything Azure related. I'm not saying that this makes my questions unique, more that I don't have the knowledge to understand if the cause/solution is the same. Deploying to Azure from Visual Studio fails when connecting

Known VS2019 problem, Microsoft is largely ignoring bug reports about it. What does tend to work is [posted here](https://stackoverflow.com/questions/15621103/deploying-to-azure-from-visual-studio-fails-when-connecting). — Hans Passant, Jun 01 '19 at 13:27
Did you try as a workaround to allow untrusted certificates, as suggested by the error message? — RobertBaron, Jun 03 '19 at 13:27
@RobertBaron all of those links are for Azure. I am not using anything Azure — MyDaftQuestions, Jul 09 '19 at 11:41

MyDaftQuestions · Accepted Answer · 2021-06-25T11:30:01.910

If you trust the server, then you can simply ignore the warning/error by editing the publish file directly

https://stackoverflow.com/a/33662970/3252861

Open the publish profile file (.pubxml) inside /Properties/PublishProfiles in a text editor

Inside the PropertyGroup element, set AllowUntrustedCertificate to True (AllowUntrustedCertificate> True /AllowUntrustedCertificate>) or add it if it doesn't exist

Set UsePowerShell to False (False).

I didn't do the 3rd point, so I guess I either have previously or didn't need it

Now we can follow the advice on https://developercommunity.visualstudio.com/content/problem/484286/publish-fails-to-iis-using-msdeploy-webdeploy.html and actually add the following 2 entries

<UseMSDeployExe>True</UseMSDeployExe>
<AllowUntrustedCertificate>True</AllowUntrustedCertificate>

It should be pointed out that some have reported you only need to use one of those two:

<AllowUntrustedCertificate>True</AllowUntrustedCertificate>

So, the start of the pubxml XML file now looks like

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <UseMSDeployExe>True</UseMSDeployExe>
        <AllowUntrustedCertificate>True</AllowUntrustedCertificate>
        <WebPublishMethod>MSDeploy</WebPublishMethod>
        <LastUsedBuildConfiguration>Release</LastUsedBuildConfiguration>
        <LastUsedPlatform>Any CPU</LastUsedPlatform>
        <SiteUrlToLaunchAfterPublish />
        <LaunchSiteAfterPublish>True</LaunchSiteAfterPublish>
        <ExcludeApp_Data>True</ExcludeApp_Data>
        <MSDeployServiceURL>domain</MSDeployServiceURL>
        <DeployIisAppPath>name</DeployIisAppPath>
        <RemoteSitePhysicalPath />
… 
…

Both was to much and give an error (Remote provider closed connection).Only add True worked perfect — Dinand, Feb 01 '20 at 17:00
Microsoft Visual Studio Community 2019 Version 16.4.5, And the problem is still there. — Fabio Maulo, Feb 12 '20 at 15:10
If you still have issues, just make sure that .pubxml is included in the project. — sandeep talabathula, May 09 '20 at 13:03
Instead of allowing untrusted hosts, is there a way to set the certificate inside the publish profile? That would be more logical. — SandRock, Apr 27 '23 at 12:11

score 8 · Answer 2 · answered Jun 12 '19 at 07:18

8

In your /Properties/PublishProfiles/xxxxxx.Settings.pubxml file, add the following two lines

<UseMSDeployExe>True</UseMSDeployExe>
<AllowUntrustedCertificate>True</AllowUntrustedCertificate>

answered Jun 12 '19 at 07:18

John Rah

1,757
1
14
13

score 6 · Answer 3 · answered Feb 11 '21 at 22:08

I know this is old, but I did find a different solution that worked for me (after trying to create/upload certificates; reset publishing profiles, etc.)

If you have the nuget package MSBuild.Microsoft.VisualStudio.Web.targets installed in your project, it's old and that's what breaks it. Remove that package and your publish will work. No need to add the AllowUntrusted flat in your pubxml as long as your server IS trusted. (*ie Azure.)

score 2 · Answer 4 · answered Jun 11 '21 at 15:38

2

I´m using VS 2019

Add the next lines into PropertyGroup node:

<UseMSDeployExe>True</UseMSDeployExe>
<AllowUntrustedCertificate>true</AllowUntrustedCertificate>

answered Jun 11 '21 at 15:38

Matías Gallegos

111
5

1

This worked for me! thanks – whisk Nov 09 '21 at 15:09

score 0 · Answer 5 · answered Apr 16 '20 at 14:17

0

I am from the product team and I can confirm that this is the only property that needs to be set if the server certificate is untrusted.

<AllowUntrustedCertificate>True</AllowUntrustedCertificate>

answered Apr 16 '20 at 14:17

vijayrkn

461
4
7

score 0 · Answer 6 · answered Jan 08 '21 at 10:28

0

Verify your code if there is any errors /C#/ Razor syntax, sometimes errors will not show in errors window.

answered Jan 08 '21 at 10:28

Muni Chittem

988
9
17

score 0 · Answer 7 · answered Jun 15 '22 at 16:55

Same problem here. I attempted to delete the obj file folder figuring that was the problem. And it was, I had two pdf files in them that wouldn't delete being they required Admin privilege's to delete. I used the command prompt utility to go in and delete them and then did a rebuild and published with no issues.

Can not publish since moving to VS 2019

7 Answers7

Linked