Can `ViteDevServerLauncher `be embedded in a .net process

[myderr]

I observed that the following code is used to start vite now

        var startInfo = new ProcessStartInfo(command, args)
        {
            CreateNoWindow = false,
            UseShellExecute = true,
            WindowStyle = ProcessWindowStyle.Normal,
            WorkingDirectory = Path.GetFullPath(workingDirectory),
        };

If UseShellExecute is set to false and the input and output streams are managed, can a dos window be reduced and IsViteDevelopmentServerRunning can also be removed? because vite has been started and stopped with the main process

        var startInfo = new ProcessStartInfo("node", args)
        {
            CreateNoWindow = true,
            UseShellExecute = false,
            RedirectStandardInput = true,
            RedirectStandardOutput = true,
            RedirectStandardError = true,
            WindowStyle = ProcessWindowStyle.Hidden, 
            WorkingDirectory = Path.GetFullPath(workingDirectory),
        };

For example, the following figure shows that I cannot stop Vite when it stops, so I cannot submit a pull request.

[Eptagone]

Hi, in fact, the old versions used to work that way.
But it was really problematic because that and the confusing logs in the same window. That's why I changed it and now works like the SpaProxyLaunchManager that Microsoft uses with their SPA templates.

[myderr]

Hi, in fact, the old versions used to work that way. But it was really problematic because that and the confusing logs in the same window. That's why I changed it and now works like the SpaProxyLaunchManager that Microsoft uses with their SPA templates.

Have you considered adding a parameter to allow us to freely choose between the two methods?

[RacerDelux]

Isn't the format of the logs from vite and .net pretty different?

I too would like this feature, purely for ease of use. I would prefer if the other developers that use this don't have to see a bunch of command line windows pop up.