New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dotnet.exe remains even though Visual Studio unit test finishes #6528

Closed
takuya-takeuchi opened this Issue May 5, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@takuya-takeuchi
Copy link

takuya-takeuchi commented May 5, 2017

Steps to reproduce

Do unit test in VS 2015. Target project is *.xproj.

And my environmental is

dotnet.exe --version
1.0.3

Expected behavior

After finish unit test, all dotnet.exe processes exit.

Actual behavior

All dotnet.exe remain.
Every time I do unit test, dotnet.exe goes on increasing.

When I saw task manager, there are a lot of dotnet.exe and they consume large memory.
Should we have to kill them by the following command?

taskkill /f /im dotnet.exe

And this behavior is similar with #5311.

Others

anime

@livarcocc

This comment has been minimized.

Copy link
Member

livarcocc commented May 6, 2017

@takuya-takeuchi I am not sure how this is possible.

CLI 1.0.3 no longer supports project.json. As in, it won't run it at all. You must have a global.json in your repo with a sdk node pointing to a preview2 CLI.

Either way, we no longer support project.json. Please, migrate your project to msbuild and use VS2017. If this issues still reproes there, please re-activate.

@livarcocc livarcocc closed this May 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment