Professional Web Applications Themes

version numbers and releasing software... - ASP.NET Web Services

I am about to install a asp.net web application I have written in the 'real' world - this app uses mutilple assemblies (minimum of 10) and calls out to web services which in turn call some COM+ components all of which I have written in C# .net. Currently the AssemblyVersionAttrbiute is set to '1.0.0.1' for all the assemlbies, What I want to know is when I make an update to my software what is the best policy for revision numbers and will asp.net and COM+ automatically use the newer assemblies or will I have to rebuild the applications for each ...

  1. #1

    Default version numbers and releasing software...

    I am about to install a asp.net web application I have written in the 'real'
    world - this app uses mutilple assemblies (minimum of 10) and calls out to
    web services which in turn call some COM+ components all of which I have
    written in C# .net.

    Currently the AssemblyVersionAttrbiute is set to '1.0.0.1' for all the
    assemlbies, What I want to know is when I make an update to my software what
    is the best policy for revision numbers and will asp.net and COM+
    automatically use the newer assemblies or will I have to rebuild the
    applications for each release?

    Cheers

    Jim


    Jim Guest

  2. #2

    Default Re: version numbers and releasing software...

    COM+ is not the issue as long as the interface (public methods, etc.) do not
    change. And, you can "inform" you .NET app to automatically use newer
    versions.

    --
    Gregory A. Beamer
    MVP; MCP: +I, SE, SD, DBA

    ************************************************
    Think Outside the Box!
    ************************************************
    "Jim hotmail.com>" <<ME> wrote in message
    news:ejlnmXZaEHA.3512TK2MSFTNGP12.phx.gbl...
    > I am about to install a asp.net web application I have written in the
    'real'
    > world - this app uses mutilple assemblies (minimum of 10) and calls out to
    > web services which in turn call some COM+ components all of which I have
    > written in C# .net.
    >
    > Currently the AssemblyVersionAttrbiute is set to '1.0.0.1' for all the
    > assemlbies, What I want to know is when I make an update to my software
    what
    > is the best policy for revision numbers and will asp.net and COM+
    > automatically use the newer assemblies or will I have to rebuild the
    > applications for each release?
    >
    > Cheers
    >
    > Jim
    >
    >

    Cowboy \(Gregory A. Beamer\) [MVP] Guest

Similar Threads

  1. Pro version numbers do not display correctly;other update weirdness
    By Joseph_Haefeli@adobeforums.com in forum Adobe Acrobat Macintosh
    Replies: 1
    Last Post: September 5th, 05:54 PM
  2. educational version of software
    By user@domain.invalid in forum Macromedia ColdFusion
    Replies: 2
    Last Post: May 19th, 08:16 PM
  3. Version Control Software for Database Objects
    By Mark Dexter in forum PostgreSQL / PGSQL
    Replies: 4
    Last Post: January 14th, 02:40 PM
  4. Modules/code for comparing version numbers?
    By David Coppit in forum PERL Modules
    Replies: 1
    Last Post: September 16th, 05:12 AM
  5. Anybody can please confirm these version numbers for me?
    By Niall Litchfield in forum Oracle Server
    Replies: 0
    Last Post: December 19th, 10:22 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139