visual studio 2010 - VS2010 - How can two or more people edit a use-case file at the same time? -


i have solution written in vs2010. have modeling project in solution use case. want allow 2 or more people able edit file @ same time. also, don't want people overwrite each other. instead, i'd vs2010 merge changes. possible in vs2010?

it's not advisable multiple people work on same file @ same time, if use team foundation server version control, take @ topic managing models , graphs under version control:

merging changes in model files , diagrams

after more 1 user has worked on model concurrently, team foundation version control prompt merge changes in model files. working on separate projects described in previous preceding sections avoid of merges. ordinarily, remaining conflicts can safely merged automatically. following kinds of changes should cause no difficulty:

  • types of lifelines. when add lifeline interaction (sequence diagram), type stored in root model, unless have created lifeline existing type.

  • new activities , interactions stored in root model.

  • adding elements , relationships.

  • renaming or deleting elements referenced within own package.

working on shared modeling projects

to minimize conflicts between concurrent work on different parts of project:

  • divide modeling project packages representing different areas of work. move entire model packages, instead of leaving in root model. more information, see defining packages , namespaces.

  • different users should not work on same package or diagram @ same time.

  • if using profiles, make sure has installed same profiles. see customizing model profiles , stereotypes.

to ensure change package working on:

  • set linkedpackage property of uml class, component, or use case diagram.

  • in uml model explorer, drag activity or interaction package have created it. element appear in uml model explorer when create first node in activity or sequence diagram.

  • to keep track of packages, rename package files reflect actual package names.

  • in team foundation version control, perform check in , latest version operations on complete modeling project, never on individual files.

  • always perform operation before check in modeling project.

  • always close diagrams before perform operation.

note if file open when perform get, , operation results in local changes, prompted reload file. in case, click no, , reload complete project. in solution explorer, right-click modeling project node, click unload project, , click reload project.


Comments

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

fortran - Function return type mismatch -

queue - mq_receive: message too long -