TFS: how to let Flare know that a project is already bound?

This forum is for all Flare issues related to using Source Control.
Post Reply
siskamoens
Propeller Head
Posts: 85
Joined: Wed Mar 21, 2007 3:01 am
Location: Belgium
Contact:

TFS: how to let Flare know that a project is already bound?

Post by siskamoens »

I recently created a new project in Flare to replace some documentation that existed in Word before. I wanted to do the migration first, before binding the project to TFS (Team System 2008).

When the project was finished, I bound it to TFS using Visual Studio - Source Control Explorer, which worked fine: the project is bound and mapped to the local workspace.
However, Flare 5 does not recognize the TFS binding. So I wanted to bind the project to the right location in TFS via Project Properties - Source Control tab. Flare lets me specify the right server and lets me browse to the right project directory, but then refuses to bind because "Source Control: AddFile: Unable to add files to Team Foundation Server. There is no working folder mapping for C:\Adam\SCC\..."

How do I solve this one?
Siska Moens
Technical communicator
ADAM Software
NigelBennett
Propeller Head
Posts: 68
Joined: Mon Jun 25, 2007 5:41 am
Location: Oslo, up north
Contact:

Re: TFS: how to let Flare know that a project is already bound?

Post by NigelBennett »

I have the same problem. Our TFS specialist created an account for me and bound my Flare projects using the Source Control Explorer, and the projects are now inaccessible. I contacted Flare support and they told me I had to remove the Flare projects from TFS, then re-bind them using the Flare Project Properties > Bind Project command. I have now attempted to bind a new project to TFS using the Flare-recommended procedure, but I get exactly the same result as for the previously-bound projects:

First the message:
"The source control operation finished with warnings and/or errors. Press Close when you are done reviewing the messages."

I press Close and an error message appears:
"Unhandled exception has occurred in your application. If you click... etc. etc. There is no working folder mapping for C:\Documentation...."

If I click Continue, another error message appears repeating the "There is no working folder mapping for C:\Documentation..." message.
Nigel
Confirmit, Oslo
siskamoens
Propeller Head
Posts: 85
Joined: Wed Mar 21, 2007 3:01 am
Location: Belgium
Contact:

Re: TFS: how to let Flare know that a project is already bound?

Post by siskamoens »

Projects in TFS are also "cached" in a version.config file, typically stored in C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Team Foundation.

Try doing a search for that file and removing the project there as well, before rebinding the project to TFS again via Flare.
Siska Moens
Technical communicator
ADAM Software
NigelBennett
Propeller Head
Posts: 68
Joined: Mon Jun 25, 2007 5:41 am
Location: Oslo, up north
Contact:

Re: TFS: how to let Flare know that a project is already bound?

Post by NigelBennett »

We have now managed to get one project working by deleting it from TFS then re-binding it via Flare. There was a problem with mappings, as Flare said the mapping didn't exist when it did. So we used a bit of "reverse logic", deleted the mapping from TFS, and then Flare found it and everything worked fine :?:

Until we tried setting up for merging. But that's another topic... :(
Nigel
Confirmit, Oslo
siskamoens
Propeller Head
Posts: 85
Joined: Wed Mar 21, 2007 3:01 am
Location: Belgium
Contact:

Re: TFS: how to let Flare know that a project is already bound?

Post by siskamoens »

Yep, that's how I got it to work as well: I simply removed all workspace mappings that pointed to that project, removed the mappings from the version.config file as well, unbound the project in Flare (if necessary), and then bound the project via Flare project properties again.

That means that I can never work with one central workspace mapping that groups all my projects in it, but that I'll need to set up a workspace mapping for every single version of every single product...helas.
Siska Moens
Technical communicator
ADAM Software
Post Reply