DCSIMG
Team Build Sidekick Visual Studio add-in released! - Team Foundation Sidekicks

Team Build Sidekick Visual Studio add-in released!

Version 1.0 of Team Build Sidekick add-in is released today! We also have made available source code for the product and an article describing the application design and how Team Foundation Server object model was used in the product.

Those familiar with Team Build integration in Visual Studio know that while creating new build type is supported through nice (though not very advanced) wizard, editing of existing build type requires series of simple yet annoying steps to be performed before and after actual file change took place (those instructions appear as the header of every .proj file created by Team Build wizard).

The add-in allows you to perform editing of Team Build type proj file by single-clicking context menu in Team Explorer. The add-in may be configured to use either Visual Studio or tool of user's choice (hint hint! think MSBuild Sidekick) for build project file editing.

The article describes TFS Version Control object model methods used to implement the application functionality as well as means of accessing Team Explorer in add-in. We hope that together with the source code that will be a good starting point for anyone seeking to extend TFS in Visual Studio.

If you have any questions or suggestions, just leave us a comment.

Enjoy!

Published Sunday, August 27, 2006 11:25 PM by Eugene Zakhareyev
תגים:,

Comments

# re: Team Build Sidekick Visual Studio add-in released!

What great funI cannot install this. I get an error stating "File .addin does not exist". Any clues to why this might happen?

Thursday, August 31, 2006 12:59 PM by Graham

# re: Team Build Sidekick Visual Studio add-in released!

Hi there.
I get the same error, and so does a collegue of mine.
When I open the solution in VS, then I see that there is one shortcut with an exclamation mark in the TfsAddin project: "TfsAddin - for Testing.addin".

Double-clicking this file give this error message: "Cannot find the file '...\Documents and Settings\eugenez\My Documents\Visual Studio 2005\Addins\TfsAddin - For Testing.AddIn'. It may have been moved or deleted."

Can this have something to do with the install-error?

Thursday, August 31, 2006 1:17 PM by Charles

# re: Team Build Sidekick Visual Studio add-in released!

After some searching, I managed to get it working by:
- manually compiling the source of the TfsAddin project (Release build).
- copying the binaries into the "C:\Program Files\Attrice Corporation\Team Build Sidekick add-in" folder
- copying the "SidekicksAddin.addin"-file from the TfsAddin projectfolder to "{user folder}\My Documents\Visual Studio 2005\Addins\".
- updating the "Assembly Location" element in the "SidekicksAddin.addin" file to the value "C:\Program Files\Attrice Corporation\Team Build Sidekick add-in\SidekicksAddin.dll"

I think that the installer package doesn't cope well with the fact that in our company, a user's personal folder resides on a network drive, being accessed via a UNC-path.

Cheers,

Charles

Thursday, August 31, 2006 4:21 PM by charles

# re: Team Build Sidekick Visual Studio add-in released!

Charles,
you make my life better,
Thanks,
Maciek

Thursday, August 31, 2006 5:37 PM by Maciek

# re: Team Build Sidekick Visual Studio add-in released!

Hello all,

Thank you very much for the feedback.

First, about the source code. The add-in configuration file is required for debugging the add-in, and it is should be located at your user's directory "..\Documents and Settings\[User name]\My Documents\Visual Studio 2005\Addins\TfsAddin - For Testing.AddIn". The file itself (TfsAddin - For Testing.AddIn) is included in distribution, so what you need is to place it in appropriate folder.

Secondly, problem on setup is not related to shortcut in project. If you look under setup project in Visual Studio, there is file "SidekicksAddin.addin", and that file is copied during installation into user's "My Documents\Visual Studio 2005\Addins" folder and that file is updated during the installation. Essentially, setup does the sequence of steps described in Charles' post.

Now, may be file is not copied during setup because of some permissions issue or indeed UNC may be to blame (though MSI is supposed to copy that).

We shall investigate that further, thank you very much for your insights!


Friday, September 01, 2006 1:32 AM by Eugene Zakhareyev