VersionedTFSBuild Discussions Rss Feed

New Post: Support for tfs 2012

deepakstoic — Mon, 18 Mar 2013 10:47:11 GMT

can you please provide this template for tfs 2012?
Thanks
Deepak

New Post: File with version is not downloaded to local folder

guzzam — Mon, 25 Feb 2013 08:51:04 GMT

Hi,

Verify that you have defined the build process parameter "VersionFileLocation" (as mentioned in the setup guide).

New Post: Labeling automated build

aplocher — Wed, 14 Nov 2012 21:09:07 GMT

I can't seem to find the information you're referring to.

There is mention of the drop location in another discussion, but the fix for that was to place it in the workflow after the Version number has been determined (which you fixed in your most recent release). My drop location gets the correct name, and the Label occurs immediately after the drop location is created, so the version has been determined by that time. The default variable value for LabelName is BuildDetail.BuildNumber, but this is the same as it was before when it worked correctly with the DefaultTemplate.xaml (when it created labels like: MyBuild Nightly_20121113.1).

Thanks

New Post: Labeling automated build

Vaccano — Wed, 14 Nov 2012 02:55:17 GMT

There is an easy fix for this.

One of the discussion points shows how to do this. (I am sorry that I don't have a link for it right now.)
________________________________
From: aplocher [email removed]
Sent: Tuesday, November 13, 2012 6:22 PM
To: [email removed]
Subject: Labeling automated build [VersionedTFSBuild:403109]

From: aplocher

Hello, first of all, this component has been very helpful.

My only question/complaint, is once I implemented this it changed my TFS source control Label names from "MyBuild Nightly_20121113.1" to "104" (TFS's internal build number).

I would like it to use the same version that I'm using for everything else. Either "MyBuild Nightly_0.58.0.4" or just simply "0.58.0.4".

Is this easy to accomplish?

Thanks!

Read the full discussion online<http://versionedtfsbuild.codeplex.com/discussions/403109#post941313>.

To add a post to this discussion, reply to this email ([email removed]<mailto:[email removed]?subject=[VersionedTFSBuild:403109]>)

To start a new discussion for this project, email [email removed]<mailto:[email removed]>

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings<https://versionedtfsbuild.codeplex.com/subscriptions/thread/project/edit> on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

-------------------------------------------------------------------
The information transmitted by this e-mail and any included
attachments are from ARUP Laboratories and are intended only for the
recipient. The information contained in this message is confidential
and may constitute inside or non-public information under
international, federal, or state securities laws, or protected health
information and is intended only for the use of the recipient.
Unauthorized forwarding, printing, copying, distributing, or use of
such information is strictly prohibited and may be unlawful. If you
are not the intended recipient, please promptly delete this e-mail
and notify the sender of the delivery error or you may call ARUP
Laboratories Compliance Hot Line in Salt Lake City, Utah USA at (+1
(800) 522-2787 ext. 2100

New Post: Labeling automated build

aplocher — Wed, 14 Nov 2012 01:22:15 GMT

Hello, first of all, this component has been very helpful.

My only question/complaint, is once I implemented this it changed my TFS source control Label names from "MyBuild Nightly_20121113.1" to "104" (TFS's internal build number).

I would like it to use the same version that I'm using for everything else. Either "MyBuild Nightly_0.58.0.4" or just simply "0.58.0.4".

Is this easy to accomplish?

Thanks!

New Post: File with version is not downloaded to local folder

kis1 — Tue, 14 Aug 2012 08:49:39 GMT

Hi,

I'm trying to use this extension, but when Workspace.Get is executed to get fileversion file to local folder it doesn't get copied to C:\temp. As result i get later exeption :

Could not find a part of the path 'C:\temp\BuildVersions04bc37bf-81b7-4a6b-940f-8afa8361df76\Version.txt'.

It's in GetAndIncrementVersionNumber activity. Any ideas ?

New Post: Error in XAML in activities between Get Workspace and Update Buildnumber

JDM6763 — Wed, 27 Jun 2012 16:18:06 GMT

I'm having major difficulty in getting errors resolved in the xaml in activities between Get Workspace and Update Buildnumber. I've got the custom assemblies in a folder under my build templates folder and have my build controller pointing to that folder. I've refreshed and restarted my build controller and have gone as far as recompiling the custom assembly source code. Still the errors persist. There is also a red dot to the right of the assembly in the import section. Can someone tell me how to get this working? I'm very new to TFSBuild and evaluating it to see if this is something we can used to help our build process. So far I can't get any custom assemblies to work. Oh, I can successfully do a build but there are no errors in the build log.

Thanks in advance!

New Post: Drop Folder does not include Build Number Format

Vaccano — Tue, 29 May 2012 17:50:14 GMT

I have created a new version that should have this issue fixed.

New Post: Drop Folder does not include Build Number Format

Antondeg — Wed, 16 May 2012 17:18:27 GMT

Is there an updated script yet?

If not can I please get more information on how to change the existing one to solve the build number problem.

Thanks

New Post: Drop Folder does not include Build Number Format

amitdeserwani — Wed, 18 Apr 2012 08:09:35 GMT

vaccano wrote:

That is exactly it.

I had intended to respond with the instructions on how to make that change (or just update the code), but you beat me too it :)

That is exactly it.

I was meaning to

Could you please send me the updated script?

Amit

New Post: Drop Folder does not include Build Number Format

amitdeserwani — Wed, 18 Apr 2012 08:08:50 GMT

Hi,

Can somebody post the exact steps to fix the build script please?

Regards

Amit

New Post: UpdateVersionBackToTFS method fails - access denied.

chaks7 — Wed, 22 Feb 2012 20:36:01 GMT

Looking at your code to increment versions. Unable to write the updated version back to the file, I get Access to the path is denied inside UpdateVersionBackToTFS method. Do you know why this could happen? I gave permissions to the folder where the Build Service is running.

Am I doing something wrong?

-Thanks

Chakri Bireddy.

New Post: Error in loading the assembly

gkkishan — Sat, 31 Dec 2011 06:15:15 GMT

Hi,

I am running in to some issues with versioning the binaries. I think this tool will modify AssemblyInfo.cs file in the background and generate the binaries. However, when my primary project is built, it could not load assembly.

Ex: Project A & Project B being a libary is consumed by Project A

Now, i see that project B.dll is compiled successfully will version 1.0.0.0 (for ex) and Project A.dll also compiles with the version 1.0.0.0.

When i run the application, it throws the error that "Could not load Project B.dll with the version x.x.x.x (ex: 2011.12.31.2 - version number that was part of assembly info.cs).

Could you please look in to this problem?

Regards,

Kishan G K

New Post: Drop Folder does not include Build Number Format

gkkishan — Fri, 16 Dec 2011 10:53:13 GMT

Hi,

First of all, thanks for this excellent package. This has indeed reduced lot of my time customizing it.

It would be good if we can post the updated workflow as part of the download itself. Thanks.

Regards,

Kishan

New Post: Drop Folder does not include Build Number Format

gkkishan — Fri, 16 Dec 2011 10:53:12 GMT

Hi,

First of all, thanks for this excellent package. This has indeed reduced lot of my time customizing it.

It would be good if we can post the updated workflow as part of the download itself. Thanks.

Regards,

Kishan

New Post: Additional changeset with every build

vaccano — Mon, 05 Dec 2011 15:26:31 GMT

The build keeps the version number in the TFS Source Control tree.

That checkin updates the version number.

If you don't want to keep the version number in TFS Source Control, you could modify the Build Template to use a local file instead.

I do not plan to add a feature like this to the source of this template as I really like keeping the version in source control (and the extra Changesets do not bother me)

New Post: Additional changeset with every build

deepakstoic — Mon, 05 Dec 2011 08:46:12 GMT

there is an extra changeset as displayed below with every build. Is there any way to stop this as this will cause double no. of changesets.

Changeset 5565: NO_CI - Updating Version

New Post: Drop Folder does not include Build Number Format

kootsoop — Tue, 18 Oct 2011 15:13:34 GMT

Cool! Thanks for the confirmation. :-)

New Post: Drop Folder does not include Build Number Format

vaccano — Tue, 18 Oct 2011 15:12:22 GMT

That is exactly it.

I had intended to respond with the instructions on how to make that change (or just update the code), but you beat me too it :)

That is exactly it.

I was meaning to

New Post: Drop Folder does not include Build Number Format

kootsoop — Tue, 18 Oct 2011 15:10:53 GMT

The problem turned out to be that the XAML file that comes with this project puts the updates to the BuildNumber too late in the process. Moving the creation of the drop folder to AFTEr the build number is calculated fixed the issue.

VersionedTFSBuild Discussions Rss Feed

New Post: Support for tfs 2012

New Post: File with version is not downloaded to local folder

New Post: Labeling automated build

New Post: Labeling automated build

New Post: Labeling automated build

New Post: File with version is not downloaded to local folder

New Post: Error in XAML in activities between Get Workspace and Update Buildnumber

New Post: Drop Folder does not include Build Number Format

New Post: Drop Folder does not include Build Number Format

New Post: Drop Folder does not include Build Number Format

New Post: Drop Folder does not include Build Number Format

New Post: UpdateVersionBackToTFS method fails - access denied.

New Post: Error in loading the assembly

New Post: Drop Folder does not include Build Number Format

New Post: Drop Folder does not include Build Number Format

New Post: Additional changeset with every build

New Post: Additional changeset with every build

Changeset 5565: ***NO_CI*** - Updating Version

New Post: Drop Folder does not include Build Number Format

New Post: Drop Folder does not include Build Number Format

New Post: Drop Folder does not include Build Number Format

Changeset 5565: NO_CI - Updating Version