How is GAT Package information persisted?

How does the GAT handle a package being used across different machines?

/ How is GAT Package information persisted?

For example, a recipe (part of Guidance Package ‘A’) is run, creating a new project. The recipe associates unbound references to the new project.

The new project is checked into source control.

The new project is checked out on another machine (which also has part of Guidance Package ‘A’ installed).

On the new machine, can the references still be seen?

If so how?

If not, why not?

Many thanks

GJB

[2378 byte] By [GJB] at [2008-1-26]

# 1

GAT is a per-user tool. In order to "move" your recipes to another machine, you have to send the .suo file together with the solution.

kzu at 2007-9-9 >

# 2

Thanks for clarifying.

Could you perhaps elaborate on the decision to make the GAT a per user tool?

Do you anticipate the facility to specify in a recipe whether it will be user or solution specific?

Many Thanks again

GJB at 2007-9-9 >

Visual Studio Hot Topic