CODEWITHSUNDEEP
clickoncecruisecontrol.net
mmmm
mmmm

Reputation: 2471

Incrementing assembly version in CruiseControl.NET for ClickOnce publish

Although this seems like other questions (here and here), I have a problem that is not quite addressed by these answers.

I have an application that is deployed as a ClickOnce application, and I can publish it from Visual Studio 2010, which increments the assembly version correctly. When I do the same in CC.NET, then how do I increment the version and then check this back in (if I need to do that), so that the versions are correct the next build ?

Thanks in advance

Update

The build labeller looks like this ..

  <labeller type="assemblyVersionLabeller">
    <build>-1</build>
    <incrementOnFailure>True</incrementOnFailure>
    <major>1</major>
    <minor>1</minor>
    <revision>-1</revision>
  </labeller>

How do I get that value into the MSBuild for publishing ?

Upvotes: 4

Views: 692

Answers (1)

Mahesh KP
Mahesh KP

Reputation: 6446

Try this thing

< labeller type="defaultlabeller">

  < prefix>2.2.0.< /prefix>

  < incrementOnFailure>False< /incrementOnFailure>

< /labeller>

There is an interesting post on this here

Upvotes: 2

Related Questions