EditPlus Configure C # compilation and running environment

Assuming that the source program file directory is C:\Files, you first build a subdirectory C:\Files\bin to facilitate saving the execution file.

(1) Compiling:
Actions: Add Tools >> Modify "menu text" to "C#compile";

"Command" is "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\csc.exe" (the directory where the CSC command is located);

Parameter is/target:exe/out:$ (filedir) \bin\$ (filenamenoext). exe $ (FileName)

"Starting directory" is $ (filedir). Finally, we have to check the "capture output" so that the result will be displayed in the window below the EditPlus.

Description: The parameters look very complex, if you use a constant instead of a variable in DOS to execute you know what it means. Before running, you must set up a folder bin in the directory where the CS files are located, so that all of the CS files are saved in this directory after compiling the EXE files.

Check "Capture Output", "Output mode" for "Default output mode", "Application", "OK", write a small program to see:

(2) Run:

Actions: Add Tools >> Modify "menu text" to "C#run";

"The Command" is "$ (filenamenoext)";

"Parameter" is empty;

"Start Directory" is $ (filedir) \ Bin

Description: Why the command is "$ (filenamenoext)". Since the compiled EXE file name is the same as the CS filename, we can remove the suffix name when we execute it; why do I need to add a "\ Bin" to the start directory? You understand.

3. Other instructions: If configured to (Capture output), the program appears from the keyboard record the user's input situation, such as "Console.ReadLine ()" And so on, EditPlus will not give input prompts, some just wait ..., You can continue to compile and run other programs only after you have finished running EXE files from the process, and the temporary solution is to not allow EditPlus to capture the output, that is, "capture output" is not checked.

Ctrl 1 try to see ~ ~