|
Thanks Urs,
So, for console application and Windows service application without GUI, Application.Exit is useless, right?
regards,
George
|
|
|
|
|
If there is no Application.Run process running, then the Application.Exit function is useless.
As far as i'm aware your statement is true.
Cheers,
|
|
|
|
|
Cool, Mark!
Question answered.
regards,
George
|
|
|
|
|
Hi George,
A lot of applications don't need Application.Exit(), even Windows Forms applications
can do without if one wants them to only terminate when the main form gets closed.
Service means no forms, means no Application.Exit().
I trust you are aware of Environment.Exit()?
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Yes, Luc! Currently, I am using Environment.Exit (-1). And I want to keep on learning new things. Is Environment.Exit safe that no resource leak will occur (and all expected exception handler and finally blocks are executed)?
regards,
George
|
|
|
|
|
Hi George,
1.
yes Environment.Exit() will clean up and avoid leaks.
Everything that terminates a process will clean up the resources allocated by
the process itself, that is basic functionality in Windows itself.
Nevertheless, it is good practice to do it explicitly;
and you should clean up if your program has two or more parts that are rather
independent, so after part 1 you could and should clean up before starting
part 2, so part 2 gets a maximum of available resources (memory, handles, whatever)
and hence gets the best performance.
2.
George_George wrote: finally blocks are executed)?
Why don't you try it? you really should replace some of your questions by
looking it up yourself and/or testing it yourself. Here is enough code to
figure it out (put it in e.g. a button click handler):
try {
Application.Exit();
} finally {
StreamWriter tw=File.CreateText("finally.txt");
tw.Close();
}
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Cool, Luc!
Finally block is not executed. I think the reason is, process is terminated by Environment.Exit, and resources are released by Windows, so there is no need to execute finally block, right?
regards,
George
|
|
|
|
|
Hi George,
George_George wrote: Finally block is not executed
It was executed in my experiment, with the code snippet in a button click handler,
the file got generated in \bin\debug folder.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Hi Luc, can you post your code please? Finally block is not executed, here is my code.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace ConsoleApplication2
{
class Program
{
static void Main(string[] args)
{
try
{
Environment.Exit(-1);
}
finally
{
Console.WriteLine("Hello world");
}
}
}
}
regards,
George
|
|
|
|
|
Hi George,
you already have my code[^].
I am not surprised your code snippet is fooling you, after all you ask it to
perform console I/O where the application is exiting, hence forms, consoles,
and other UI stuff is winding down. The file system however remains alive to
the very end of the app.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Sorry Luc,
Here is your code, the finally blocked is not executed. Could you reproduce? I am confused.
using System;
using System.IO;
using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace ConsoleApplication2
{
class Program
{
static void Main(string[] args)
{
try
{
Environment.Exit(-1);
}
finally
{
StreamWriter tw = File.CreateText("finally.txt");
tw.Close();
}
}
}
}
regards,
George
|
|
|
|
|
Hi George,
my example was on Application.Exit() which causes an Application.Run() to return,
I guess asynchronously by sending a Windows message or something; so the thread
has the opportunity to first execute the finally block.
Your test was on Environment.Exit() which, from your observation, seems to cause
an immediate exit. I trust the exact behavior is hidden somewhere in the documentation.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Thanks Luc,
I think for console and Windows Service application, we should never use Application.Exit, right?
regards,
George
|
|
|
|
|
Application.Exit() causes Application.Run() to return, both make sense in windows apps only.
this has been asked and answered many times in the last couple of days, it is not going
to change any time soon ...
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Thanks Luc,
Question answered.
regards,
George
|
|
|
|
|
I never use Application.Exit; I just call the form's Close method.
|
|
|
|
|
Thanks PIEBALDconsult,
I just want to confirm in console and Windows service application, we should not use Application.Exit to terminate the process, right?
regards,
George
|
|
|
|
|
Hello everyone,
Mentioned in the book -- "CLR via C#", page 15, chapter 1 "The CLR's Execution Model",
--------------------
the C# compiler will emit NOP (no-operation) instructions into the code. The NOP instructions are emitted to enable edit-and-continue feature while debugging.
--------------------
What means "edit-and-continue" feature? Why emitting NOP instructions will facilitate this feature?
thanks in advance,
George
|
|
|
|
|
Hi George
Edit and Continue is that you can stop the running program on a break point, change the code in that method and continue the execution, i.e. you can code while debugging.
Why the compiler adds nops, I don't know
Urs
-^-^-^-^-^-^-^-
no risk no funk
|
|
|
|
|
Thanks Urs,
I am also wondering why NOP instructions will facilitate edit-and-continue feature. Let us wait for comments from others.
regards,
George
|
|
|
|
|
Perhaps it replaces the NOP's with any new sets of instructions if you edit your code while debugging.
I don't really know, but it seems quite possible.
My current favourite word is: Bacon!
-SK Genius
|
|
|
|
|
Interesting point, SK!
But the developer when debugging may insert as many instructions as possible. How many NOP instructions of IL will be generated?
regards,
George
|
|
|
|
|
I didn't mean it would replace just the NOP instruction with other instructions. Infact, thats quite difficult since a NOP is 1 byte and most other instructions are more like 3bytes+
I meant instead of the debugger having to start inserting extra instructions after the current one, or before it. It can just replace (and expand) the current instruction (which is just a NOP).
But of course, what if you remove instructions, what happens then?
I think the answer to this is way beyond me
My current favourite word is: Bacon!
-SK Genius
|
|
|
|
|
Thanks SK,
I agree with the basic policy you posted above. But suppose I can copy and paste a large code segment into current function, save it and continue to run. In this case, I do not think compiler will be smart enough to know in advance I will past a lot of code and will reserve a lot of NOP operations. Any comments?
regards,
George
|
|
|
|
|
Pehaps they are just there for somewhere for execution of the program to wait at, safely without fear of the current instruction changing.
If you stopped on something like push 01 and you wanted to change that to push 02 and exection had paused on that instruction, would it be able to change it? Whereas if you where stopped on a NOP then the instruction will never be changed even if everything else around it is.
I think we need some kinda expert on this one.
My current favourite word is: Bacon!
-SK Genius
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
