2

I developed an console application, with the dotnet framework. I want the application to run when called in a terminal session and when executing the .exe file.

Now I got a problem with the design of my application. When launching the exe, I need to ask if the program should be terminated, so that the user can read the output of my application (otherwise the application and therefore the terminal would close before any human could read what hs been printed).

But exactly this process of asking before the application stops executing is annoying if the application has been launched from the terminal, let's say by running dotnet myapp.dll. This is because when launching a terminal session the terminal doesn't close after an application has terminated.

So my question is if there exists any advice/ best practice/ or if there is a way of detecting if the application has been launched via an exe file or in the terminal.

Thanks for your advice.

Moritz
  • 378
  • 5
  • 14
  • Is it command-line tool? Such tools aren't doing anything special. *"the terminal would close before any human could read"* - is not their problem. – Sinatr Jul 28 '20 at 13:09
  • Actually I've seen a tool which uses `MessageBox`, but it does it always if command parameters are missing or wrong. Specifically to you question see [this](https://stackoverflow.com/q/17508093/1997232). – Sinatr Jul 28 '20 at 13:12
  • 1
    See my answer [here](https://stackoverflow.com/a/63135555/10413298) – Koray Elbek Jul 28 '20 at 13:55
  • Perhaps you could use the [Environment.UserInteractive](https://learn.microsoft.com/en-us/dotnet/api/system.environment.userinteractive?view=netcore-3.1) property, but it [only works on .NET Framework, not .NET Core](https://github.com/dotnet/core/issues/3017) as far as I remember ([Further link](https://github.com/dotnet/runtime/issues/770)) – Pieterjan Jul 28 '20 at 14:21
  • @CoReeYe I guess your solution doesn't work on Linux or Mac without installing extra programs – Moritz Jul 28 '20 at 15:21
  • @Sinatr yea, but I thought there might be an (easy) workaround. But I seems as there is no workaround. – Moritz Jul 28 '20 at 15:24

0 Answers0