To literally hide/show the console window on demand, you could use the following functions: It’s possible to hide/show the console by using ShowWindow. GetConsoleWindow retrieves the window handle used by the console. IsWindowVisible can be used to checked if a window (in that case the console) is visible or not. #include <Windows.h> void HideConsole() { … Read more
Ah, yes, this is one of the caveats of using the Windows console subsystem. When the user closes the console window (regardless of how the console was allocated), all of the processes that are attached to the console are terminated. That behavior makes obvious sense for console applications (i.e., those that specifically target the console … Read more
Starting from Windows Vista, a service cannot interact with the desktop. You will not be able to see any windows or console windows that are started from a service. See this MSDN forum thread. On other OS, there is an option that is available in the service option called “Allow Service to interact with desktop”. … Read more
Platform invoking the clipboard APIs is a possible solution. Example: using System.Runtime.InteropServices; class Program { [DllImport(“user32.dll”)] internal static extern bool OpenClipboard(IntPtr hWndNewOwner); [DllImport(“user32.dll”)] internal static extern bool CloseClipboard(); [DllImport(“user32.dll”)] internal static extern bool SetClipboardData(uint uFormat, IntPtr data); [STAThread] static void Main(string[] args) { OpenClipboard(IntPtr.Zero); var yourString = “Hello World!”; var ptr = Marshal.StringToHGlobalUni(yourString); SetClipboardData(13, ptr); … Read more
[EDIT: 4/2021 – new answer…] Due to a recent change in the Visual Studio debugger, my original answer stopped working correctly when debugging. To remedy this, I’m providing an entirely different approach. The text of the original answer is included at the bottom. 1. Just the code, please… To determine if a .NET application is … Read more
I’m pretty sure that you cannot affect or change this behavior. As you mention, it has nothing to do with your application itself, because it doesn’t do it when you double-click on the EXE. You only see this effect when you run the app from within Visual Studio without the debugger attached. Presumably, when you … Read more
You have some options: Use “Debug -> Command line arguments” option in Visual Studio; Use “Debug -> Attach to process” and find your process; it is not cmd.exe, but a process with executable name like “MyProject.exe”. You can use Process Explorer or another task manager with “tree view” support to easily find the Process ID … Read more
Use this Nuget package V1.9.x – Command Line Parser Library (CodePlex – Going away soon and out of date) V2+ – Command Line Parser (Ongoing support) Takes seconds to configure and adds instant professional touch to your application. // Define a class to receive parsed values class Options { [Option(‘r’, “read”, Required = true, HelpText … Read more
Read this about the difference between using Environment and Application : Application.Exit Vs Environment.Exit There’s an example of what you want to do in the bottom of that page: if (System.Windows.Forms.Application.MessageLoop) { // Use this since we are a WinForms app System.Windows.Forms.Application.Exit(); } else { // Use this since we are a console app System.Environment.Exit(1); … Read more
System.Web is there, but seems Visual Studio doesn’t sort by name by default. You’ll need to click Component name column to get that list sorted. I was able to run this code: Console.WriteLine(System.Web.HttpUtility.UrlEncode(” “)); // + Just adding a System.Web reference, without System.Web.Extensions. Also, You should replace your target framework from .NET Framework 4 Client … Read more