versioning

I have a system that uses MEF to load parts. Each of these parts rely on a core library. When I build the project, I add a version number to the .dll files like this: part1-1.0.0.0.dll part2-1.0.0.0.dll Also, there is an application that performs MEF composition. It also uses the core library. I've found that I can just deploy the "part" dlls, and composition works fine because the application has already loaded the core library that the parts rely on. So my file system looks something like this: /parts/part1-v1.dll /parts/part2-v1.dll composer-v1.exe core-v1.exe The trouble I'm having is how

Right now our assemblies have a version number like 2.0.831.0. As I understand it, that's major version, minor version, date and build number. If I make a change and build again on the same day it's 2.0.831.1, 2.0.831.2 etc. My TeamCity build number format is simply 2.{0} where {0} is an auto incremented number that just goes on forever (2.195, 2.196 etc). How do I make TeamCity look exactly like the assembly version? We want to be able to associate the Change Log with the assembly version so anyone can say assembly version 2.0.831.2 had these changes in these files. Extra info: Our build step

What would be the best way to version a rails application? We want to start to get into more structured testing cycles and having a set version per build is a part of that. We use subversion but I would like to avoid using revision numbers for versions. Is there an easy way to do this automatically? Or should I just define a app_version method in the application helper? (We are using subversion for source control) You can use subversion keywords: Essentially, you could have a helper method... def app_version "$Id$" end $Id$ is a keyword which svn will expand (the link above has others you

There has certainly been posts around for this, but I actually did a commit because I thought it was the right thing to do. So, I have two repositories, one development and one production. I had to edit something in the production because it was an urgent bugfix, and now I have three files that are newer in the production than in the development. I committed the three files on the production and tried a pull, but it told me there were merge errors. I tried copying and pasting the new files to the development server and retrying the whole thing and it didn't work. Now I'm sure that what I need

Given this snippet from Blah.dll's AssemblyInfo.cs: [assembly: AssemblyVersion("3.3.3.3")] [assembly: AssemblyFileVersion("2.2.2.2")] And then in a separate .exe: var fileInfo = FileVersionInfo.GetVersionInfo("/path/to/Blah.dll"); fileInfo.ProductVersion == fileInfo.FileVersion == true; Other SO questions show ProductVersion being "correct", curious if there is something odd about how I'm using it. Shouldn't ProductVersion be "3.3.3.3" and FileVersion be "2.2.2.2"? What would cause it to report both properties as AssemblyFileVersion? Matt Davis I found the answer originally here . I'm

The MSDN documentation states: Version numbers consist of two to four components: major, minor, build, and revision. The major and minor components are required; the build and revision components are optional, but the build component is required if the revision component is defined. All defined components must be integers greater than or equal to 0. The format of the version number is as follows (optional components are shown in square brackets ([ and ]): major.minor[.build[.revision]] The components are used by convention as follows: Major: Assemblies with the same name but different major

I'm looking at building basic CMS functionality into our web product and am researching tips and design ideas for versioning content. I'm specifically looking for database schemas in use today. What are you using for content versioning? What patterns apply if you have different types of content that need versions stored? How is question versioning handled on Stack Overflow? Thanks Stephan Eggermont Literature uses a 5 dimensional model for this: version (wanting to change) status (life cycle: creating, testing, deploy, retire) view (html, pdf, file system, derivability) hierarchy (page,

Every time I publish the application in ClickOnce I get get it to update the revision number by one. Is there a way to get this change automatically to change the version number in AssemblyInfo.cs file (all our error reporting looks at the Assembly Version)? Jason Stangroome We use Team Foundation Server Team Build and have added a block to the TFSBuild.proj's AfterCompile target to trigger the ClickOnce publish with our preferred version number: <MSBuild Projects="$(SolutionRoot)\MyProject\Myproject.csproj" Properties="PublishDir=$(OutDir)\myProjectPublish\; ApplicationVersion=$

We have 2 separate products that need to communicate with each other via web services. What is the best-practice to support versioining of the API? I have this article from 2004 claiming there is no actual standard, and only best practices. Any better solutions? How do you solve WS versioning? Problem Description System A Client class SystemAClient{ SystemBServiceStub systemB; public void consumeFromB(){ SystemBObject bObject = systemB.getSomethingFromB(new SomethingFromBRequest("someKey")); } } Service class SystemAService{ public SystemAObject getSomethingFromA(SomethingFromARequest req){