Have Geek Brain

Creating an assembly from TFS

When are you going to release a build using TFS, what do you usually do? Just use a custom changeset, create a branch or a tag / tag?

Note: This build is not intended for release, it is for our user adoption / hosting environment.

0


a source to share


6 answers


The build system will automatically create a label based on the name. This is usually good enough for most companies.



+1


a source


When we start developing on a new version, we insert and push the new code and revisions into this branch.

This allows us to do two things:



  • We've created a night-time merge process that dumps the branch back onto the trunk. This allows bug fixes to be propagated to all versions in development (any other branches are merged with the main and back again depending on the priority of the version number).
  • We also created a nightly build for each branch that was deployed in the morning to our staging environment.
0


a source


I use a fairly simple formula to determine if it should be a tag or a branch, if there is a chance you will need to fix or fix a build, use a branch. Otherwise, if you just want to reference the code at some point, use a label. Another important consideration is that labels have a limited configuration manager, for example. they can be removed or changed by anyone with permission without any change history.

0


a source


I actually have more than one assembly. I use the Version Tasks that come with the free MSBuild packages (MSBuild Community Tasks, MSBuild Extension and MSBuild SDC) to change my version in Team Build and in my binaries.

I have a custom version that has the format 1.2.3.4 (major.minor.revision.build)

My nightly build build number. When I am about to make a release for testing, I run a build that will contain the version number.

Then, when you are ready for prod, you can release the tested version.

0


a source


I suggest doing a nightly build as suggested above by @Vaccano, or you can do continuous integration. You can find good build tools to turn you off in the right direction at http://www.newagesolution.net/SpecialEvents/SessionatOrlandoCodeCamp2009.aspx . To achieve automatic assembly and packaging, there must be Powerpoint and code samples.

0


a source


As part of the nightly compilations / planned builds, I would also like to generate release notes from the version store and the workItems repository.

The release notes that are available are of great advantage. You can now use the TFS ChangeLog / TFS ReleaseNotes Generator from http://tfschangelog.codeplex.com .

The TFS ChangeLog application allows users to provide information about the start point and end point of their changeset (we call it as the changeset) and then retrieves the information for each changeset that is present between the start and end changesets. This extracted information is then stored in an XML file, and then an HTML release notes report is generated using an XSLT 2.0 transformation.

I hope this helps.

Best wishes,

Dharmesh Shah.

0


a source






More articles:


All Articles