Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Facebook Sign In with Google Sign In with OpenID

Categories

We have migrated to a new platform! Please note that you will need to reset your password to log in (your credentials are still in-tact though). Please contact lee@programmersheaven.com if you have questions.
Welcome to the new platform of Programmer's Heaven! We apologize for the inconvenience caused, if you visited us from a broken link of the previous version. The main reason to move to a new platform is to provide more effective and collaborative experience to you all. Please feel free to experience the new platform and use its exciting features. Contact us for any issue that you need to get clarified. We are more than happy to help you.

Assemblies

smashingpravinsmashingpravin Posts: 1Member
[b][red]This message was edited by smashingpravin at 2006-12-14 5:41:35[/red][/b][hr]
I m new to .Net want to know how memory management handled in assemblies

Thanks

Pravin



Comments

  • DrMartenDrMarten Posts: 748Member
    [b][red]This message was edited by DrMarten at 2006-12-14 14:9:7[/red][/b][hr]
    : I m new to .Net want to know how memory management handled in assemblies
    :
    : Thanks
    :
    : Pravin
    ______________________________________________________________________

    Hi,

    I guess it is all handled by the FRAMEWORK routines.
    Once a program is created in VB.Net or any other Visual Studio language then the memory is allocated as needed by your program with the Dim statements etc.

    Memory is released when Sub's or/and when your program EXITS/ ENDS.

    However for some programs/solutions/projects ( whatever you call them ), then you will see examples of the DISPOSE command which release resources back to the system for those objects/items it is called to act upon.

    See this FORUM site.>> http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=10&SiteID=1

    where a staff member of Microsoft or someone else may give you a definitive answer.

    Memory managemennt is not something i'd
    personally concern myself over. :-|


    Regards,

    Dr M.
  • rlcrlc Posts: 448Member
    If your assemblies are all managed code than the garbage collection in .Net should take care deallocating objects itself. The garbage collection has three levels 0,1,2. Typically I have had no problems with managed code except some issues when creating delegates and timers on workers threads that needed to be removed before the references created would allow the memory to be released for the final stage of collection. Unmanaged code such as COM objects will still require to be released much of the time. here are some links.

    ~rlc

    http://msdn.microsoft.com/msdnmag/issues/1100/gci/
    http://msdn.microsoft.com/msdnmag/issues/1200/GCI2/
    http://www.codeproject.com/dotnet/garbagecollection.asp
Sign In or Register to comment.