SourceGear Support

Are you getting zero messages, or are you just not getting the list of files? If you change it to a nonworkingfolder get, do you get messages? If you already have files in the working folder, or if they are cached in the hidden state folder, then you won't see messages when they're updated. Could th...

Will it work if you change the signature of GetMessageEventHandler to object, string?

Also, try setting the user message before you log in.

The beauty of Handoff is that we don't require that you change how you access older versions. You can keep VSS around to do VSS label or history gets. Your old build scripts don't have to change at all. History is history, and you can still get it when you need it. Of course, you can still see file ...

Try this: ServerOperations.GetInstance().UserMessage += new ServerOperations.UserMessageEventHandler(GetMessageEventHandler); GetOperations.ProcessCommandGet(objectPaths.ToArray(), options); ServerOperations.GetInstance().UserMessage -= new ServerOperations.UserMessageEventHandler( GetMessageEventHa...

Hi Dave, You are correct in your assessment of the problems that you are facing. First, I would advise you to look at our Handoff feature, which can import a smaller set of history much quicker, and give you integrated access to your VSS history. As for your import, there is no regular method for al...

It's probable that those files are cached in you client cache folder, and aren't being downloaded from the server. They're just being copied from another location on disk. To force a full cache-free get latest, set a new working folder before doing the get.

This code worked for me: using System; using System.Collections.Generic; using System.Linq; using System.Text; using VaultClientIntegrationLib; namespace GetOutputer { class PrivateClass { public void Run() { string url = "http://localhost/VaultService"; string username = "admin"...

Glad to hear. Thanks.

Show History on the file, then right-click the change and choose Details.

That's odd. Is it possible that your get request is not getting any files? Are they already up to date in the working folder?

ItemPath1 should have the path you're looking for, but only for transactions that have been checked in after you upgraded to 3.5. Any transactions from before the upgrade will not have a full path.

Do you see the full path when you look at that transaction in the GUI client?

You'll need to listen to the StatusMessageEvent through the EventEngine. If you want more real-time download messages, add a listener for the ProgressChangedEvent.

I see that the VaultTxDetailHistoryItem has all of the fields that you wanted. Are they all coming back empty? Can you find that transaction in the GUI client? Here's the rest of the code from the 3.5 command line client that deals with printing transaction details. if (items.Length > 0) // and it A...

The list should be coming along with the other messages that you're getting from subscribing to the ServerOperations.GetInstance().UserMessage event that I mentioned before.

If you want to isolate just the messages from get/checkout, you'll need to use a more complicated event notification system.

SourceGear Fortress is a cross-platform Application Lifecycle Management (ALM) solution for small and midsize teams.

For the release notes for Fortress 2.0.2, see:
http://www.sourcegear.com/fortress/releases/