However, it did require creating a publish profile in Visual Studio. I knew that it could package the the output to a single zip. I took a step back and removed my build/publish steps and fell back to using msbuild directly. The “dotnet” command line utilities do not support this packaging.
#VISUAL STUDIO PUBLISH TO IIS PACKAGE ZIP#
Typically, for most other deployments using WebDeploy, the output is packaged as a single zip file. This lead me to thinking that having all of the output in a single folder was the issue. Regardless of the combination of switches, I couldn’t seem to get it to work. I attempted deploying the content folder using msdeploy. This is where things become more difficult, though. The only thing unique is that I specify an output path for the dotnet publish. You can see that all of these build steps are pretty straight-forward. Within Team City, I configured these build steps using the. My first issue was that I was trying to run this sequence to get an output and then call msdeploy with the files generated: But, we can get around this a bit with MSBuild.
The current tooling for Dotnet Core doesn’t directly support this, though. Ideally, it would be really nice to be able to deploy to IIS using msdeploy. NET Core app deployed to an IIS hosted instance.
#VISUAL STUDIO PUBLISH TO IIS PACKAGE TRIAL#
Throw in a continuous integration tool, like Team City, and it becomes a bit of trial and error to get a. NET Core applications to IIS, is a bit lacking.
Microsoft’s guidance, in regards to deploying.
0 kommentar(er)
