Sdk: dotnet command line argument to terminate remaining build processes that are finished but dont exit

Created on 22 Jan 2019  路  4Comments  路  Source: dotnet/sdk

Is your feature request related to a problem? Please describe.

I'm am trying to build and publish... but unfortunately there are hanging processes in Task Manager .NET Core Host that lead to a publish error if i try to dotnet publish

Describe the solution you'd like

I want the Remaining Tasks to close after the build OR publish process has ended.

Describe alternatives you've considered

Since now i've been terminating them by hand, it would be good to have a dotnet <command> to terminate all open .Net Core Hosts that remain.

Additional context

Here is a Screenshot of the remaining Tasks:

1

unbenannt

Most helpful comment

@CreativeHouseDotOrg

Does the command dotnet build-server shutdown help terminate these processes?

Note that the build servers will shut themselves down automatically after a period of inactivity.

All 4 comments

This is by design.

These are our long running processes (MSBuild node reuse, VBCSCompiler and Razor compiler). They are used to improve performance by avoiding paying for startup time all the time.

What errors are you getting that you believe this is the cause?

cc @peterhuene

@CreativeHouseDotOrg

Does the command dotnet build-server shutdown help terminate these processes?

Note that the build servers will shut themselves down automatically after a period of inactivity.

@livarcocc
I am building my apps in NPM Console inside Visual Studio Community 2017 and everytime i try to call the publish command after the build command (that seems to be finished) but the output shows an error that another process is being used and it tries to "retry" with a time counter (trying again in #Seconds)

@peterhuene You are a Hero!! +1 +1 +1

dotnet build-server shutdown is exactly what I'm looking for!

Thank you very much!

Creative regards!

Was this page helpful?
0 / 5 - 0 ratings