Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
ASP.NET 2.0 Professional If you are an experienced ASP.NET programmer, this is the forum for your 2.0 questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Professional section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old October 9th, 2007, 01:41 AM
Authorized User
 
Join Date: Feb 2007
Location: , , .
Posts: 32
Thanks: 0
Thanked 0 Times in 0 Posts
Default Assembly Versioning

Hello All,

I was working with asp.net 2.0 some time back. Now i start working on asp.net 2.0. But i am very much confused in deploying web application in asp.net 2.0. And offcourse i dont have any idea how to play with different version of assemblies. In which scenerio we should change assembly version and which portion we should change(major or minor or build). I search on web a lot... but did not find any good article. Plz help me out..
Thanks in advance.

  #2 (permalink)  
Old October 9th, 2007, 09:38 AM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

This seems to usually be a matter of personal preference.

Typically the major and minor version numbers easy to dictate. You simply need to decide what they are based on the release of your software.

From what I've read Microsoft applies the build number as a date. For example, v2 of the framework is this version:

   2.0.50727

It's major version 2, minor 0, built on 2005 July(07) 27th. Using this method makes it easy to see when a particular assembly was created.

I've yet to find any explanations as to what the revision number represents. I've used CruiseControl.NET to fire off release builds of software. If that case I've set up the build system to set the revision number to the incremental build number that comes from CruiseControl. This provides an association between a given assembly and a particular build that is logged and archived.

Unfortunately there isn't a cut and dried standard for versioning. Like everything else in software, there are lots of ways of doing it, and it's up to the individual or organization to decide what's best. The important thing is to be consistent with all your systems.

-Peter
  #3 (permalink)  
Old October 9th, 2007, 10:29 AM
Imar's Avatar
Wrox Author
Points: 70,322, Level: 100
Points: 70,322, Level: 100 Points: 70,322, Level: 100 Points: 70,322, Level: 100
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Quote:
quote:I've yet to find any explanations as to what the revision number represents
AFAIK, the revision number with .NET assemblies is the number of seconds since midnight for the day of the built....

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
  #4 (permalink)  
Old October 9th, 2007, 10:43 AM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Quote:
quote:Originally posted by Imar
 AFAIK, the revision number with .NET assemblies is the number of seconds since midnight for the day of the built....

This is true when you use this as your assembly version in the AssemblyInfo file:

     x.x.*

The * tells VS to fill in the build and revision numbers. However, if you set it explicitly (1.2.0.0) the 0.0 will remain.

-Peter
  #5 (permalink)  
Old October 9th, 2007, 10:47 AM
Imar's Avatar
Wrox Author
Points: 70,322, Level: 100
Points: 70,322, Level: 100 Points: 70,322, Level: 100 Points: 70,322, Level: 100
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Right; I thought you were referring to the fixed revision number in assemblies deployed by the .NET Framework. e.g. the .1378 in 2.0.50727.1378

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
  #6 (permalink)  
Old October 9th, 2007, 10:59 AM
planoie's Avatar
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Oh right. In that case, yes, I think you are correct.

-Peter


Similar Threads
Thread Thread Starter Forum Replies Last Post
Converting .NET 2.0 Assembly to .Net 1.x Assembly pskaushik .NET Framework 2.0 1 November 25th, 2006 01:51 PM
assembly sreenu.pocha C# 4 July 26th, 2006 07:31 AM
Automatic Versioning in AssemblyInfo piyushnu Assembly Language 1 April 16th, 2006 02:36 PM
Assembly arv1980 VS.NET 2002/2003 1 January 15th, 2006 11:42 PM
Web Services Versioning RM82 .NET Web Services 2 March 2nd, 2005 12:08 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.