![microsoft visual studio 2017 only create dll not exe microsoft visual studio 2017 only create dll not exe](https://support.zemax.com/hc/article_attachments/1500007642341/KA-01636_image10.png)
I have vaguely the same problem since upgrading to Visual Studio 2017.5.2. The only possible solution that I have at this moment is restarting my pc, which makes the development impossible.ĭoes anyone have any idea why this is commented on Thu Dec 14 2017 It returns " The process with PID ProcessID could not be terminated." Error, with " This task is not running currently" as reason. this window will automatically close when the debugging has completely stopped." but it can not stop the dotnet.exe process.Įven the "End Process" on the Processes-Tab can not terminate the dotnet.exe process, it gives an AccessDenied warning.Įven the command "taskkill /pid ProcessID /f" cannot terminate it. You can force debugging to stop immediately, but any processes being detached may be terminated instead. Visual studio shows the popup window " Stop Debugging in Progress." with the message: " Debugging is being stopped but is not yet complete.
![microsoft visual studio 2017 only create dll not exe microsoft visual studio 2017 only create dll not exe](https://www.technical-recipes.com/wp-content/uploads/2012/11/dll1.jpg)
![microsoft visual studio 2017 only create dll not exe microsoft visual studio 2017 only create dll not exe](https://blog.matrixpost.net/wp-content/uploads/2020/11/corflags001.png)
The solution contains 3 dotnet core projects (Identity server, Api and Web application). GeneralĪfter migration of 3 dotnet core projects from dotnet core 1 to 2.0, Visual Studio cannot stop dotnet.exe processes after stopping the debugging. Visual studio is unable to stop dotnet.exe process. Commented on Wed Visual studio 2017 can not stop dotnet.exe