Web Publish .net core website using MSBuild
up vote
0
down vote
favorite
I'm trying to Web Publish a .zip created by dotnet publish from Azure DevOps. There's a WinRM Web Publish task but it's unsatisfactory because it uses port 5986 and requires a self-signed certificate on the target server, which only lasts for one year.
Is it possible to use MSBuild instead such that it doesn't attempt a build and only does a publish?
I figure this should be possible because I can use Web Publish from Visual Studio and it doesn't use port 5986.
asp.net-core msbuild
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
add a comment |
up vote
0
down vote
favorite
I'm trying to Web Publish a .zip created by dotnet publish from Azure DevOps. There's a WinRM Web Publish task but it's unsatisfactory because it uses port 5986 and requires a self-signed certificate on the target server, which only lasts for one year.
Is it possible to use MSBuild instead such that it doesn't attempt a build and only does a publish?
I figure this should be possible because I can use Web Publish from Visual Studio and it doesn't use port 5986.
asp.net-core msbuild
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to Web Publish a .zip created by dotnet publish from Azure DevOps. There's a WinRM Web Publish task but it's unsatisfactory because it uses port 5986 and requires a self-signed certificate on the target server, which only lasts for one year.
Is it possible to use MSBuild instead such that it doesn't attempt a build and only does a publish?
I figure this should be possible because I can use Web Publish from Visual Studio and it doesn't use port 5986.
asp.net-core msbuild
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
I'm trying to Web Publish a .zip created by dotnet publish from Azure DevOps. There's a WinRM Web Publish task but it's unsatisfactory because it uses port 5986 and requires a self-signed certificate on the target server, which only lasts for one year.
Is it possible to use MSBuild instead such that it doesn't attempt a build and only does a publish?
I figure this should be possible because I can use Web Publish from Visual Studio and it doesn't use port 5986.
asp.net-core msbuild
asp.net-core msbuild
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
asked Nov 10 at 0:42
Ian Warburton
5,5841255112
5,5841255112
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Do publish without build, you can use dotnet publish --no-build. You can check the additional options here. If you need to change the port, you can change it from the Program.cs file with this:
WebHost.CreateDefaultBuilder(args)
.UseUrls("http://localhost:5054")
.UseStartup<Startup>()
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
Dotnet publish doesn’t build already. And the port number is for Web Publish not the website itself.
– Ian Warburton
Nov 10 at 1:29
add a comment |
up vote
0
down vote
accepted
MSBuild depends on or uses MSDeploy, which handles Web Publish. (I could see this from the summary of the publish profile in Visual Studio.)
There's an Azure DevOps task for this here...
https://github.com/rschiefer/MSDeployAllTheThings/tree/master/Tasks/MSDeployPackageSync
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Do publish without build, you can use dotnet publish --no-build. You can check the additional options here. If you need to change the port, you can change it from the Program.cs file with this:
WebHost.CreateDefaultBuilder(args)
.UseUrls("http://localhost:5054")
.UseStartup<Startup>()
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
Dotnet publish doesn’t build already. And the port number is for Web Publish not the website itself.
– Ian Warburton
Nov 10 at 1:29
add a comment |
up vote
0
down vote
Do publish without build, you can use dotnet publish --no-build. You can check the additional options here. If you need to change the port, you can change it from the Program.cs file with this:
WebHost.CreateDefaultBuilder(args)
.UseUrls("http://localhost:5054")
.UseStartup<Startup>()
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
Dotnet publish doesn’t build already. And the port number is for Web Publish not the website itself.
– Ian Warburton
Nov 10 at 1:29
add a comment |
up vote
0
down vote
up vote
0
down vote
Do publish without build, you can use dotnet publish --no-build. You can check the additional options here. If you need to change the port, you can change it from the Program.cs file with this:
WebHost.CreateDefaultBuilder(args)
.UseUrls("http://localhost:5054")
.UseStartup<Startup>()
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
Do publish without build, you can use dotnet publish --no-build. You can check the additional options here. If you need to change the port, you can change it from the Program.cs file with this:
WebHost.CreateDefaultBuilder(args)
.UseUrls("http://localhost:5054")
.UseStartup<Startup>()
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
answered Nov 10 at 0:59
Neville Nazerane
2,32811433
2,32811433
Dotnet publish doesn’t build already. And the port number is for Web Publish not the website itself.
– Ian Warburton
Nov 10 at 1:29
add a comment |
Dotnet publish doesn’t build already. And the port number is for Web Publish not the website itself.
– Ian Warburton
Nov 10 at 1:29
Dotnet publish doesn’t build already. And the port number is for Web Publish not the website itself.
– Ian Warburton
Nov 10 at 1:29
Dotnet publish doesn’t build already. And the port number is for Web Publish not the website itself.
– Ian Warburton
Nov 10 at 1:29
add a comment |
up vote
0
down vote
accepted
MSBuild depends on or uses MSDeploy, which handles Web Publish. (I could see this from the summary of the publish profile in Visual Studio.)
There's an Azure DevOps task for this here...
https://github.com/rschiefer/MSDeployAllTheThings/tree/master/Tasks/MSDeployPackageSync
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
add a comment |
up vote
0
down vote
accepted
MSBuild depends on or uses MSDeploy, which handles Web Publish. (I could see this from the summary of the publish profile in Visual Studio.)
There's an Azure DevOps task for this here...
https://github.com/rschiefer/MSDeployAllTheThings/tree/master/Tasks/MSDeployPackageSync
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
MSBuild depends on or uses MSDeploy, which handles Web Publish. (I could see this from the summary of the publish profile in Visual Studio.)
There's an Azure DevOps task for this here...
https://github.com/rschiefer/MSDeployAllTheThings/tree/master/Tasks/MSDeployPackageSync
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
MSBuild depends on or uses MSDeploy, which handles Web Publish. (I could see this from the summary of the publish profile in Visual Studio.)
There's an Azure DevOps task for this here...
https://github.com/rschiefer/MSDeployAllTheThings/tree/master/Tasks/MSDeployPackageSync
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
answered Nov 10 at 23:10
Ian Warburton
5,5841255112
5,5841255112
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53235018%2fweb-publish-net-core-website-using-msbuild%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
