星队快捷方式文件
是否可以创建 StarTeam 快捷方式、打开项目并覆盖工作目录？
是否可以创建一个 StarTeam 快捷方式，一次打开多个项目？
问题是：我有几个解决方案，它们使用相同的 StarTeam 项目，并且我必须经常手动更改工作文件夹（查看 -> 属性 -> 工作文件夹）。解决方案之间无法共享数据：每个解决方案的本地视图应位于不同的位置。
Is it possible to create StarTeam shortcut, opening project and overriding working directory?
Is it possible to create one StarTeam shortcut, opening several projects at a time?
Problem is: I have several solutions, which use the same StarTeam project, and I have to manually change working folder very often (View -> Properties -> Working folder). It is not possible to share data between solutions: local view should be located in separate place for each solution.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以为每个项目创建不同的视图。不同的视图可以有不同的工作文件夹；事实上，他们默认这样做。请记住，就您看到的文件修订版本而言，视图可以设置为与默认视图几乎相同的行为。但他们可以拥有自己的工作文件夹。此技术的缺点是更改请求等也将“在视图中”，因此移动它们不一定会影响其他视图。但考虑到您正在开发一个完全独立的项目，这可能并不是一件坏事。像往常一样，您应该在测试项目中对此进行试验，并确保您对这种行为感到满意，然后再在您的“生活”存储库中使用它。
You could create different views for each project. Different views can have different working folders; in fact, they do by default. Keep in mind, a view can be set to behave pretty much the same as the default view, with regards to which revisions of files you see. But they can have their own working folders. The downside of this technique is that Change Requests and the like will also be "in the view," so moving them will not necessarily affect other views. But given that you are working on an entirely separate projects, that might not be all such a bad thing. As usual, you should experiment with this in a test project, and make sure you're happy with the behavior, before using it on your "life" repository.
每个项目和文件夹的覆盖/备用目录都保存在本地文件中 - 而不是在服务器上。默认工作文件夹保留在服务器上，每当您更新它时，更改都会传播到所有其他用户。
快捷方式 xml 没有地方指定工作文件夹。
如果您不需要 StarTeam GUI，stcmd 允许您使用 -rp 和 -fp 标志为大多数操作指定新的工作文件夹。
如果需要此公共库代码的项目位于其自己的视图中，您还可以将公共项目共享到这些其他项目中的新子文件夹中。您可以使用此新子文件夹的相对路径（包含 ..）将其移至包含项目的文件夹之外。这使您可以在许多项目中使用通用代码，同时允许您指定每个项目的通用代码的位置。
共享会产生一些开销，因此请注意，但除此之外，它可能适合您想要做的事情。
The override/alternate directory for each project and folder is maintained inside a local file - not on the server. The default working folder is kept on the server, and any time you update it the changes are propigating to all other users.
The shortcut xml has no place to specify a working folder.
If you don't need the StarTeam GUI, stcmd allows you to specify a new working folder for most operations with the -rp and -fp flags.
If the projects that need this common library code are in their own views, you could also share the common project into a new subfolder within those other projects. You can use a relative path for this new subfolder that includes .. to move it outside the containing project's folder. This lets you use common code in many projects while allowing you to specify the location of that common code per project.
Shares come with some overhead, so be aware, but other than that it would probably work for what you're trying to do.