0

I have had webdeploy running for YEARS on a Windows Server 2012 machine with standard MSBuild arguments (like this).

Yesterday I installed the Windows (Server Hosting) version of the .NET Core Installer from the .NET Core downloads page.

Since then my build tasks are running and successfully building my website, but not actually running any web deploy publishing. It is not failing - it is just not being run.

I want to stress I am talking about a 'legacy' .NET application - not a .NET Core application. I just installed .NET Core for somebody else.

I can verify this with the following observations:

  • There are no errors in any event viewers (except ones that are months old)
  • There is no message in the msbuild logfile that says Start Web Deploy Publish, however log files from just a couple days ago do have this message.
  • I can connect to the local server at port 8172 and it makes a connection.
  • It is happening with multiple projects that nobody else has access to.
  • _PublishedWebsites does get created with the latest files - it just never gets deployed anywhere.

What could possibly have broken this? Did the Windows Server Hosting package break it - or was it just some other update that came in? I've run out of ideas how to fix it and don't want to revert to xcopy!

Simon_Weaver
  • 140,023
  • 84
  • 646
  • 689

1 Answers1

0

Managed to fix it :-) Not sure exactly which of these steps did it, but I suspect it was Visual studio.

I was using TFS Express 2015 and upgraded to Update 3.

I also installed Visual Studio 2015 on the server itself.

I had previously had .NET Core RC2 (or whatever they called it at the time) installed and I uninstalled that before installing .NET Core RTM. Wondering if that removed some component that was required.

Like I said everything was working fine before I installed the .NET Core RTM - but fortunately installing VS and TFS brought everything back to normal.

Simon_Weaver
  • 140,023
  • 84
  • 646
  • 689