<div>
Hi Hakan,<br />
<br />
You can do a direct assignment if it's a managed object and ideally you should let .Net Runtime take care of the rest of the stuff. <br />
<br />
For unmanaged objects explicitly nullifying an object Or calling dispose is better suited. <br />
<br />
<br />
Also, If you want better control over garbage collection there are other techniques you can use as well, for example you can use using block. <a href="https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/using-statement" rel="ugc">https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/using-statement</a><br />
<br />
Regards, <br />
Chinmay.
</div>


Hi Hakan,

You can do a direct assignment if it's a managed object and ideally you should let .Net Runtime take care of the rest of the stuff.

For unmanaged objects explicitly nullifying an object Or calling dispose is better suited.


Also, If you want better control over garbage collection there are other techniques you can use as well, for example you can use using block. https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/using-statement [https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/using-statement]

Regards,
Chinmay.

<div>
Hey Chinmay,<br />
<br />
How can understand is it managed or not managed object?
</div>


Hey Chinmay,

How can understand is it managed or not managed object?

Developer & Coffee Roaster

Scott Fell

Skale

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
I'd like to know that, is there any benefit pros/cons assign a object variable which has already existing object.<br />
<br />
For example i have global variable MyModel with a type MyComType and it has a ObjectValue,<br />
<br />
After a while if i changed it's value to another object with the same type; is there any cons using like this.<br />
<br />
I think this is more related to lifetime of objects but i'd like to ask here.
</div>
</div>


Hello,

I'd like to know that, is there any benefit pros/cons assign a object variable which has already existing object.

For example i have global variable MyModel with a type MyComType and it has a ObjectValue,

After a while if i changed it's value to another object with the same type; is there any cons using like this.

I think this is more related to lifetime of objects but i'd like to ask here.

Is it required to set a object property null before assign a object in C#

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).