Page 1 of 1
Namspace Conflict
Posted: Fri Feb 17, 2012 12:45 pm
by rmdavidson
It's Friday so I guess I wasn't thinking, but I tried renaming a file and named a new file the same name as the old name...and now I'm getting namespace conflicts and the file won't check in. I deleted the old file, deleted the new one, brought them both back, I've resolved multiple times, tried automerging and I keep getting "No files check in due to initial conflicts" and namespace errors resulting in Flare/TFS refusing to check in the files. Is there anything I can do?
flare_namespace_error.png
Robin
Re: Namspace Conflict
Posted: Fri Feb 17, 2012 12:58 pm
by rmdavidson
I'm not sure how, but this time telling it to undo local changes fixed it (only took me 30 mins or so)...but now I have to figure out what the Linked From and Linked To links are (I have an old copy on another drive) and get those back in the topic.
Robin
Re: Namspace Conflict
Posted: Mon Feb 20, 2012 3:51 am
by i-tietz
Interesting. Sounds very much like the problems we have since last October - only we use MS VSS 2005, not TFS.
We have trouble with link updates and sometimes Flare tells us that there's a newer version of a file or even of a list of files in the database. Sometimes looking at the files in the merge tool even shows us that the files in it are identical, though Flare says something different - marking parts deleted which are still there, marking other parts as new that are also in the old version, and so on ...
We're using Win 7 Pro and Flare 7.2 - what do you use?
Sorry - I forgot:
For the wrong status commuinication, the errors in the merge tool and the error-prone link update I reported bugs. Only for the link update I received a patch so far - I installed it last week and I'm testing it this week. I will report back if this patch helps at least against the link update bug.
Re: Namspace Conflict
Posted: Mon Feb 20, 2012 11:24 am
by rmdavidson
Thanks, i-tietz.
Robin