14 writes to IsolateConsole
aspire (8)
Commands\AppHostLauncher.cs (1)
466IsolateConsole = true,
DotNet\DotNetCliRunner.cs (2)
196IsolateConsole = IsolateConsole, 446IsolateConsole = options.IsolateConsole,
Projects\DotNetAppHostProject.cs (1)
1557IsolateConsole = true,
Projects\DotNetBasedAppHostServerProject.cs (1)
657IsolateConsole = runControl?.IsolateConsole ?? false,
Projects\NativeAppHostServerProject.cs (1)
260IsolateConsole = runControl?.IsolateConsole ?? false,
Projects\PrebuiltAppHostServer.cs (1)
825IsolateConsole = runControl?.IsolateConsole ?? false,
Projects\ProcessGuestLauncher.cs (1)
132IsolateConsole = isolateConsoleForGracefulShutdown,
Aspire.Cli.Tests (6)
DotNet\ProcessExecutionDetachedTests.cs (1)
138IsolateConsole = true,
DotNet\ProcessExecutionFactoryEnvironmentTests.cs (1)
198IsolateConsole = true,
DotNet\ProcessExecutionTests.cs (3)
187IsolateConsole = isolateConsole, 238IsolateConsole = true, 374IsolateConsole = isolateConsole,
DotNet\ProcessInvocationOptionsTests.cs (1)
34IsolateConsole = true,
9 references to IsolateConsole
aspire (5)
DotNet\DotNetCliRunner.cs (3)
131/// On Windows it keeps a console (hidden when <see cref="IsolateConsole"/> is set) so it can still receive CTRL+C. 196IsolateConsole = IsolateConsole, 446IsolateConsole = options.IsolateConsole,
DotNet\ProcessExecutionFactory.cs (2)
157if (OperatingSystem.IsWindows() && (options.IsolateConsole || options.KillOnParentExit || options.Detached)) 164startInfo.CreateNoWindow = options.IsolateConsole;
Aspire.Cli.Tests (4)
Projects\DotNetAppHostProjectTests.cs (2)
339Assert.True(options.IsolateConsole); 1098Assert.True(options.IsolateConsole);
Projects\NativeAppHostServerProjectTests.cs (1)
185Assert.True(options.IsolateConsole);
Projects\ProcessGuestLauncherTests.cs (1)
46Assert.True(executionFactory.LastProcessInvocationOptions?.IsolateConsole);