January 2009 - Posts
Hi there,
If you have TFS Web Access 2008 be sure to install this Service Pack that solves a security issue.
Yigael Oscar
Hi there,
I ran into a confusing matter today at work.
We have a build that ran on TFS Build 2005 that did the following:
- …
- Execute a custom task in BuildNumberOverrideTarget that:
- checked out a file
- change the file version that it holds tor the project (++)
- checked in the file
- Override the BuildNumber parameter
- Get Source
- Compile.
- …
After upgrading to TFS Build 2008 we noticed something very confusing, when we checked the dll versions it was always one version older than expected. (If we had a folder named 1.0.43.0 the dll inside were version 1.0.42.0 for example)
It was a little hard to understand the problem but the solution was very easy.
The problem lays with the fact that the architecture of the build in TFS was changed somewhat in 2008, instead of getting the latest version by default in the Get Source stage the new default is to get the last changeset when the build was started, this change was made to make sure that if someone else checked in something in that exact same moment it will not be compiled accidently. Of course the problem is now that the changed version number will not be in the version that will be downloaded and compiled.
The solution is simple, you just have to override the GetVersion parameter like this
1: <GetVersion>T</GetVersion>
The meaning of T is that the Get command will get the latest version.
Simple, isn’t it?
Yigael Oscar
I have just encountered a very good MSDN article published recently by Microsoft.
The article takes the problems installing or configuring TFS and make recommendations on how to solve or avoid them.
http://msdn.microsoft.com/en-us/library/dd266793.aspx
Have Fun!!!
A few days ago when installing the Team Foundation Server 2008 at a client site I have encountered the following error:
“The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337”
After searching a solution in Google and exploring the logs I found out that the reason for the error is probably corrupted installation files.
After downloading the installation disk again and reinstall the TFS all worked fine.
i must say that while downloading the installation disk again I have tried to reinstall the TFS from the same disk just to be failed again with the same nice informative error.
Hi,
Today We had a situation that after installing TFS MSSCCI Plugin for Visual Studio 6, We open VB6 and There's no "Team Foundation" under Tools menu.
Repairing the installation of the plugin did not help, neither did re-installing.
The solution to this problem provided in Maor David's blog, by fixing the ini file of VB6 (c:\windows\vbaddin.ini)
Here's the post:
http://blogs.microsoft.co.il/blogs/maordavid/archive/2008/09/26/team-foundation-menu-doesn-t-exist-in-vb6-after-msscci-installation.aspx
Enjoy,
Dan
How many times we can see similarities in different solutions comes from different companies? The answer is many...
Today we can see many companies using the same features in there solutions as there competitors or even the same as features comes from solutions in different fields, you don't see many revolutionary changes between log-in solutions, on-line shops, user settings etc.
So if we can see similarity with the features why not to use the same test cases that are approved to be comprehensive instead of reinventing the test solution?
I was reading a great article written by James Whittaker located here talking exactly about that!
I was amazed of this revolutionary thinking and I believe it will be our reality real soon...
Hi,
Some of us would prefer to have build numbers that will NOT contain Date.
I discovered a great post regarding this issue by Scott Allen.
It shows how to create custom task to set an alternate build number, step by step.
But setting build number is not enough. Scott Allen shows us a simple way to manage the build version numbering: The custom task gets as a parameter a base build name and uses it to create a build version id : BaseBuildName.Counter . When activated, the task advances the counter by checking the build previous version.
Enjoy: http://odetocode.com/Blogs/scott/archive/2006/09/28/7203.aspx
Dan
This post is the fifth and last post that builds the MSProject Guide. See the first post here
On this post I will talk about the different links between work items and how it works with MSProject in the Team System 2010.
In the Team System 2010(Rosario) there are new types of links a few of them are being implemented by the MSProject.
Parent/Child Link
In the MSProject we can indent work items.
We can see in the screenshot indenting work items.
The indentation represents Parent/Child link type.
Predecessor/Successor Link
Another link type that is implemented in the MSProject is the Predecessor/Successor.
In the snapshot we can see 3 tasks that are linked with the Predecessor/Successor link type.
One last thing before I close this guide!
I have forgotten to explain how to create links in MSProject, so in order to add links do the following:
Use the “Links and Attachments” button
Note: In order to use it you will need to publish the target work item first.
Have fun using the MSProject with the Team System, it is a very strong tool...