.NET (Core and Framework)

5-Aug-08 20:31

Hi all,
I don't know how many times this question has been asked in any .NET Forum, but still i have certain doubts regarding value types storage.
In almost every book (I read)it is written that value types are going to be stored in Stack. But in some articles i read "value types are stored where they are declared" is that true ?
If it is true then valu types declared in class will get stored in Heap.
And GC will deallocate them.
So what about the performance whenever we are using value types in class
Boxing is going to happen ? What happening inside ? Please i require more information regarding these as i couldn't find it.

Thanks and Regards
Sandeep

If If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "

Check My Blog

modified on Wednesday, August 6, 2008 2:52 AM

Mark Salsbery6-Aug-08 7:48

6-Aug-08 7:48

Sandeep Akhare wrote:
If it is true then valu types declared in class will get stored in Heap.

Only if the object of the class they are members of is allocated on the managed heap.
What if they are members of a value class?

Sandeep Akhare wrote:
And GC will deallocate them.

The GC only manages objects allocated on the managed heap.

Sandeep Akhare wrote:
So what about the performance whenever we are using value types in class

Value types are passed by value - that means a copy has to be made
every time a value type object is passed. That's going to be slower
than passing a reference I would guess. If value types are members of a
ref class then there's no difference - the ref class object holds the value
type objects.

Mark

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Sandeep Akhare6-Aug-08 20:00

6-Aug-08 20:00

Thanks Mark,
Seems intresting Confused | :confused:

I don't see any good reason to use value types in the class ?
As value types are going to be over head (as GC will Deallocate them)
We are not having the benefit of value types when used in Class

Any way can you give any article link ?

Thanks and Regards
Sandeep

If If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "

Check My Blog

Mark Salsbery7-Aug-08 5:24

7-Aug-08 5:24

Sandeep Akhare wrote:
I don't see any good reason to use value types in the class ?
As value types are going to be over head (as GC will Deallocate them)

A value type as a member of a class is more efficient than a reference type.
A value type just takes up space, which will just be part of the space new/gcnew
allocates for the object. Reference types need to be allocated and collected
separately, adding more overhead.

Sandeep Akhare wrote:
Any way can you give any article link ?

Common Type System Overview[^]

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Sandeep Akhare8-Aug-08 3:34

8-Aug-08 3:34

Thanks Mark

Thanks and Regards
Sandeep

If If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "

Check My Blog

Mark Salsbery8-Aug-08 9:21

8-Aug-08 9:21

Hopefully you found what you were looking for Smile | :)

I don't like my last post - it seems irrelevant. The
most important thing IMO is how objects are passed around.
By reference means just a reference to an object is passed, so
any changes to the object effect everywhere a reference is held.
Value types are passed by value, so there's always a new unique copy
passed. That can be important to know.

Cheers,
Mark

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Sandeep Akhare10-Aug-08 20:06

10-Aug-08 20:06

Hey Mark,
I am aware of these concepts, My real concern was we use value types in the code because those are light weight (as GC wont come into picture and will get diallocated automatically from Stack when their life span is over).
But when we use value types in class we lost these advantages as GC will have to remove them and will remain in memory even though their life span is over.
I hope, i was able to explain this properly Wink | ;)

Its really very nice to see that MVP like you is looking back and sees what should and what shouldn't have posted
Thanks Mark keep it up Smile | :)

Thanks and Regards
Sandeep

If If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "

Check My Blog

Mark Salsbery11-Aug-08 5:36

11-Aug-08 5:36

Sandeep Akhare wrote:
But when we use value types in class we lost these advantages as GC will have to remove them and will remain in memory even though their life span is over.

I see what you mean, but there's really not a way around it in
a managed/garbage-collected environment.

C++/CLI (and C# maybe a little) gives you more flexibility in
deterministic finalization if it's really an issue.

There can also be a benefit to forcing a garbage collection at certain
points in an app's lifetime.

It just depends on the situation - It's definitely something to think about
in performance applications.

Cheers!
Mark

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Sandeep Akhare12-Aug-08 1:27

how to close the parent window after closing the child window

12-Aug-08 1:27

Mark Salsbery wrote:
see what you mean, but there's really not a way around it in
a managed/garbage-collected environment.

Yes you are right, Actually i had issue with this one only

Mark Salsbery wrote:
C++/CLI (and C# maybe a little) gives you more flexibility in
deterministic finalization if it's really an issue.

In C#, we will ovveride the Finalization if object is using some sysytem resources and GC can't realase them

Mark Salsbery wrote:
There can also be a benefit to forcing a garbage collection at certain
points in an app's lifetime.

This is what i read in many books " GC is slef tuning don't mess with it "
Its good to call GC if you know best time to call (End of game application .. etc )

Mark Salsbery wrote:
It just depends on the situation - It's definitely something to think about
in performance applications.

Very true,

Thanks and Regards
Sandeep

If If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "

Check My Blog

vidhyap5-Aug-08 19:48

vidhyap

5-Aug-08 19:48

Hi,

from javascript i am opening one window using window.open(),in dat window i m displaying one web page.in that page after clicking on one link i m opening one more window using window.showmodaldialog().

in showmodaldialog window i m doing some validation.if validation is successful i should close only showmodaldialog window.if validation fails i need to close both showmodaldialog window and parent window.

I m able to close the showmodaldialog window if the validation is successful.I m facing the problem to close the parent window if validation fails.

can anybody help me?

regards
vidhya

Re: how to close the parent window after closing the child window

Abhijit Jana6-Aug-08 17:57

Abhijit Jana

6-Aug-08 17:57

vidhyap wrote:
I m facing the problem to close the parent window if validation fails.

how did you try to close the parent window ?

Try with document.opener this will help.

cheers,
Abhijit

DotNet 2.0 Framework required for Windows Mobile

Muhammad Nauman Yousuf5-Aug-08 0:58

Muhammad Nauman Yousuf

5-Aug-08 0:58

Dear All,

I am unable to find Microsoft DotNet 2.0 Framework for Windows Mobile, that I can actually install to my IMate (KJAM)

Any help in this regard is highly appericated.

Best regards,
Nauman

"Mess with the Best, Die like the rest"

BadDataException

srisravani4-Aug-08 19:07

srisravani

4-Aug-08 19:07

I have declared an instance of a class called Application and named the variable ‘app’. Application has a method called Process() which throws a BadDataException on failure. Write the code to call this method.

Re: BadDataException

Mark Salsbery5-Aug-08 6:33