You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
@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.
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
AspNetCore.SpaYarp/src/AspNetCore.SpaYarp/SpaProxyLaunchManager.cs
Line 158 in ad4656f
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.
The text was updated successfully, but these errors were encountered: