Skip to content
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

[Feature Request] Start the launch Command in a separate process #8

Open
mdowais opened this issue Dec 17, 2021 · 1 comment
Open

Comments

@mdowais
Copy link

mdowais commented Dec 17, 2021

Hello, The application is executing the Launch Command (Process.Start), if it was not started seperately. But it also closes the process when the Debugging stops/restarts. As stated in the line below

private void LaunchDevelopmentClient()

But, it would make it more better if, it stayed even after stopping, which would be a great improvement when dealing with large SPA application.

The Stopping process is called using powershell, and I guess it could be started using the same way, which would keep it alive even when stopped debugging

I suggest to create a property in SpaDevelopmentServerOptions, which allows a functionality like LaunchDevServerIndependently, which wont close when debugger is stopped / restarted.

It makes it easy, so that the developer doesnt have to start the devserver manually/independently.

@BenjaminVettori
Copy link

@mdowais to achieve what you want, you can launch the development server using npm start manually first and then (once your angular client is up and running, listening to your configured port) start your c# backend. It should automatically recognize the already running client live-server and skip starting a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants