C# Versioning? - Programmers Heaven

Howdy, Stranger!

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

Categories

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.

C# Versioning?

preetipreeti Posts: 2Member
What does it mean when we say that [italic][blue]"C# is versionable"?[/blue][/italic]

Could someone please explain this concept.
Thanks very much.

Comments

  • WEBMASTERWEBMASTER Posts: 549Member
    I think it is that you can have different versions of the same component at the same time and your applications will know which version to use and what vesions not to use.

    In the past you had a "DLL HELL" where when you upgraded a DLL older software stopped working due to new features or rewritten code. Now with .NET you will have less problem with this.


    [blue][italic][b]/WEBMASTER[/b][/italic][/blue]


  • romancingliferomancinglife Posts: 3Member
    I HAVE DONE THE WHOLE OF C SHARP AND THERE IS NOTHING LIKE THIS I HAVE COME ACCROSS.

    CAN U TELLME AS TO WHERE U READ THIS FROM !?

    : What does it mean when we say that [italic][blue]"C# is versionable"?[/blue][/italic]
    :
    : Could someone please explain this concept.
    : Thanks very much.
    :


  • WEBMASTERWEBMASTER Posts: 549Member
    Take a look at the documentation about assembly and there you will find info about versioning.


    [blue][italic][b]/WEBMASTER[/b][/italic][/blue]


  • rukidingmerukidingme Posts: 2Member
    You're absolutely right. To be more precise, it is the .Net framework that handles the versioning (so VB.NET code is versionable also). Basically, when you push out a new build, old code will still pick up the previous versions of your dll's while your new code will use the new dll's. This happens automatically, seamlessly, and (so far) perfectly.




    : I think it is that you can have different versions of the same component at the same time and your applications will know which version to use and what vesions not to use.
    :
    : In the past you had a "DLL HELL" where when you upgraded a DLL older software stopped working due to new features or rewritten code. Now with .NET you will have less problem with this.
    :
    :
    : [blue][italic][b]/WEBMASTER[/b][/italic][/blue]
    :
    :


Sign In or Register to comment.