I just did a little experiment:
public abstract class MyClass
{
private static int myInt = 0;
public static int Foo()
{
return myInt;
}
publi
They will persist for the duration of AppDomain. Changes done to static variable are visible across methods.
MSDN:
If a local variable is declared with the Static keyword, its lifetime is longer than the execution time of the procedure in which it is declared. If the procedure is inside a module, the static variable survives as long as your application continues running.
See following for more details:
If it's a static variable, that means it exists exactly one place in memory for the duration of the program.
It persist for duration of the program execution, or until you overwrite it with another value. If you want to make the result as what you want it to be, you should specify myInt = 0 in the constructor before return myInt;