.NET (Core and Framework)

Sandeep Akhare wrote:

If it is true then valu types declared in class will get stored in Heap.

Sandeep Akhare wrote:

And GC will deallocate them.

Sandeep Akhare wrote:

So what about the performance whenever we are using value types in class

Mark Salsbery
Microsoft MVP - Visual C++

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)

Sandeep Akhare wrote:

Any way can you give any article link ?

Mark Salsbery
Microsoft MVP - Visual C++

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.

Mark Salsbery
Microsoft MVP - Visual C++

Mark Salsbery wrote:

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

Mark Salsbery wrote:

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

Mark Salsbery wrote:

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

Mark Salsbery wrote:

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

vidhyap wrote:

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

SqlCommand command = new SqlCommand("SP_abc");
command.CommandType = CommandType.StoredProcedure;
command.Parameters.Add("@a", SqlDbType.Int);
command.Parameters["@a"].Value = somevaluehere;
command.ExecuteNonQuery()
string b = (string)command.Parameters["@b"];