We're seeing very slow builds on large .NET projects when running through the cli with --all-projects, and there are some inconveniences in this plugin that could probably help alleviate this.
This PR:
Removes --no-cache when doing dotnet restore. Not sure why I even added this. Think I wanted to have a clean slate guarantee.
The general recommendation is to drop a specified output path all together, but I don't see a trivial way of getting dotnet to tell me where it intends to publish by default.
We're seeing very slow builds on large .NET projects when running through the cli with
--all-projects
, and there are some inconveniences in this plugin that could probably help alleviate this.This PR:
--no-cache
when doingdotnet restore
. Not sure why I even added this. Think I wanted to have a clean slate guarantee.--output
in favor of--property:PublishDir=<dir>
as per https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/7.0/solution-level-output-no-longer-valid#recommended-action suggestions.The general recommendation is to drop a specified output path all together, but I don't see a trivial way of getting
dotnet
to tell me where it intends to publish by default.