Author Topic: Source Control: EA Fails to map TFS working folder  (Read 3537 times)

youssef

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Source Control: EA Fails to map TFS working folder
« on: September 26, 2006, 07:37:42 am »
I have been using TFS and VS.NET without a problem. We purchased EA 6.5 and tried to use its Source Control features with TFS. I have spent several hours and have not been able to connect to TFS. I have checked the Web, Help file, etc but nothing helpful there. The Error that I get is:
"The workspace XYZ does not map to your local working folder C:\Projects\Designs" where XYZ is my workspace name in TFS and C:\Projects\Designs is mapped correctly in TFS. I can see it in Team Explorer and I can add files, checkin/checkout OK, but EA is not working with it. I tried other folders, roots folders, and nothing worked. Anyone able to use TFS with EA? Any help would be greatly appreciated. Thanks

rriopel

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Source Control: EA Fails to map TFS working fo
« Reply #1 on: September 26, 2006, 11:11:50 am »
We were running into this problem when a user had more than one workspace.  If you have another workspace, try that name.  I was able to get it work when I tried the other workspace names.

youssef

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Source Control: EA Fails to map TFS working fo
« Reply #2 on: September 26, 2006, 01:03:56 pm »
That was a good suggestion. But, unfortunately, it did not work for me. I tried the other workspace name and that did not work. I deleted the other workspace and tried with only one workspace, ditto. I deleted all workspaces, then created a new one and named it something different than before (I called it Mylaptop) and that did not work either. If I supply a bogus workspace name, it tells me the workspace does not exist, so it is authenticating fine and finding the workspace, but for some odd reason says that the workspace does not map to the directory supplied. I have even removed all mapped projects/directories in my workspace and left only one mapped folder and that did not work. I have tried changing directory names to a single level directory, short names, long names, you name it.
If you have any other suggestions, it would be greaty approciated. Thanks.

Is there any SPARX admins or support who can shed some light on this issue. Thanks again.

Robert de Wolff

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Source Control: EA Fails to map TFS working fo
« Reply #3 on: September 27, 2006, 03:08:12 am »
We have the same problems on more than 1 machine. I'm desperataly seeking for the solution. Is there anybody who has EA working with TFS?

CapJo

  • EA Novice
  • *
  • Posts: 15
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Source Control: EA Fails to map TFS working fo
« Reply #4 on: September 27, 2006, 03:31:04 am »
Changes and fixes for the Current Build - Version 6.5 Build 798 ( Posted 27-September-2006 )  

Added ability for UI Control elements to own other UI Control elements
Added ability for Requirement elements to own Feature elements
Fixed UML Profile import to tolerate blank version number
Improved importing of XML Schemas and Schemas spanning multiple XSD files
Stopped generation of implementation file for C++ typedef classes
Corrected some parsing errors for code importing
Added support of operation behavior to transformations
Added commands for code engineering and transformation functions automation interface.
Corrected issue with tree style connectors where both horizontal and vertical styles could be activated at the same time.
Corrected issue with displaying labels with wrapped Japanese characters.
Improved RoundRect shapescript command by preventing the rounded corners from overlapping.
Improved TFS version control configuration to query TFS for Server and Workspace names associated with the specified Working Copy folder.
Corrected TFS "add" operation to add the package file to the repository, rather than create only a pending changeset.
Improved version control initialisation when loading model, to verify existence of all working copy folders specified in VC configurations.
Improved filename generation/checking when adding files to version control - remove illegal chars from package names when creating filename.
Corrected the link for the Help button on the version control "Get Shared Files" dialog.
Improved reporting of version control status when package is "Checked Out Offline" in a shared model.
Improved version control status reporting through Automation Interface.
Improved handling of packages associated with Version Control Configurations that are incomplete - no longer handled as though VC Offline.
Added ability to create connections to elements off screen by scrolling the view.
Added ability to create a selection rectangle to elements off screen by scrolling the view.
Corrected issue of triggers not loading correctly with old data.
Added ability for ExpansionRegion elements to own Object, ExceptionHandler and ExpansionRegion elements.
Corrected issue saving Requirements when locale is set to Bulgarian.
Added Swimlane support to automation interface.
Prohibited the creation of non-creatable automation classes.
Resolved issue where creating automation elements using invalid types returned corrupted elements.
Modified code templates for C++ to not generate constructors for unions
Modified the DDL transformation to copy attribute notes to the column notes
Transitions with multiple Triggers now display correctly.
Fixed OCL validation error on collection iterations.




youssef

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Source Control: EA Fails to map TFS working fo
« Reply #5 on: September 27, 2006, 04:39:09 am »
Thanks a million. :)
I just downloaded build 798 and it works like a charm with TFS.
Thank you.

Robert de Wolff

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: Source Control: EA Fails to map TFS working fo
« Reply #6 on: September 27, 2006, 12:45:05 pm »
IT WORKS with 6.5.798

My compliments for the quick response of Sparx Systems!