SourceGear Support

I recognize that HTML Keyword expansion is implemented exactly the way that Microsoft implemented it in SourceSafe. However with just a little more thought it could be infinitely more useful. Currently $$Author:$ expands to $$Author:-->Fred<!--$ This allows HTML text such as: Last edited by: <!-- $$...

I just thought I'd add a comment about the procedure I've been using (as outlined above).

It works pretty well except for shared files within the hierarchy. I have to track down all of the shared files and make sure that there isI only one of them in my ChangeSet. This can be a real pain.

You can add my vote for this one as well.

Thanks,
Mike

Dan,
Add my vote for this feature as well. Using the IDE for file and folder diffs while offline would be very useful, and I know most of the information needed to do that is already stored locally.

Thanks,
Mike

Thanks Jeff.
I recommended that we switch to Vault from SourceSafe, and we'll be transitioning over at the end of January. I'm hoping I won't need to do this, but it's nice to know a possible solution exists.

Mike

It's interesting, because it has always seemed to me (when I was considering SourceSafe keyword expansion) that the expansion should happen when getting the file from the source control system. When the file is checked in/updated any expansion text should be removed. Since the source control system ...

Thanks, I checked with some of our developers. This is definitely going to be an issue for us at some time, as we are developing a .net application, and will want to get it working with the 2.0 framework. We're not at that point yet, but by the end of January or end of February we probably will be (...

Just thought I'd ask for an explicit clarification.

This restriction only applies to the VaultService machine, correct?

If we're doing development and testing against .NET 2.0, that won't adversely affect the Vault Client which by necessity will live on that same machine.

Mike

Hmm. I can't imagine any automated method to identify the cases where a file is renamed since it looks identical to deleting the original file and adding the renamed file as a new file. Obviously when you can identify this circumstance you want to commit it to Vault as a rename and not as a delete a...

Seems to me that you should disable any source control integration in Visual Studio, and instead just use the source control manager's client such as the Vault GUI client to perform all checkin/checkout, or edit/merge/commits. I'm fairly sure that Vault can perform the moves/renames just as well as ...

Thanks in advance for posting your findings in a followup message.
It's definitely appreciated even though I don't think I care about Shadow folders yet.

Mike

Adding that identity line to the Web.config fixed the problem.

Thanks,
Mike

Jeff, I'm set up to use impersonation. I'm going to go check out the KB article Jeremy referenced right now. If I have further issues, I'll post back. thanks, Mike what's strange is that I had just recently done an unistall of the 3.0 beta and an install of the 3.0 release, and I'd swear that I sele...

I just ran into this problem as described in this message in the Gold Support forum. http://support.sourcegear.com/viewtopic.php?t=2388 Jeff said it was being looked into on 12/2. Is there a solution yet? My random guess is that it has to do w/ a missing identity impersonation in the Web.config file...

I'd like to be able to set a new user's initial client options. Such as: Always request exclusive locks - off Store working folder data inside working folders - on Auto-commit after each operation - off Show snapshots in the folder tree - off and probably others. I'm not trying to enforce these sett...