Static members initialized or invoked at compile time or runtime ? and those static members stored in heap or stack ?

Question

0.00/5 (No votes)

See more:

we have two types members in c#

1.static members
2.instance members

when class loaded at the time static members are internalized or invoked either in compile time or runtime?

and also those static members stored in heap or stack?

What I have tried:

when class loaded at the time static members are internalized or invoked either in compile time or runtime?

and also those static members stored in heap or stack?

Posted 30-Dec-17 20:00pm

Krishna Veni

Updated 30-Dec-17 23:18pm

Add a Solution

Comments

Krishna Veni 31-Dec-17 2:31am

please help me

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2017-12-30T21:56:00

Static members are initialized before the static member is accessed for the first time and before the static constructor, if there is one, is called.
So until you access the class at run time, the static member are not initialized, but they will be before any code in the class containing them is executed, so that your code can rely on them being ready.

Stack or heap? Heap. Think about it: there is only one static object, and there are as many stacks as there are threads. The only place the static object can reside is the heap, and it is referenced via the Type Object for the compiled class (which is used to track inheritance among other things) so that is it never garbage collected until the AppDomain is unloaded.