SourceGear Support

The problem is that once the working folder and SCC login are set in the .vco file, there doesn't seem to be a way to change them other than recreate the .vco file, which causes us to lose the developer-independent project settings that we have set in the first place (i.e., the ones we want all deve...

This is not an issue with Vault, but an issue with Microsoft Embedded Visual C++ (eMVC++). We are having a problem with eMVC++ that you may have run into already and may know of a work-around. eMVC++ seems to save SCC working folder information in the *.VCO file that it creates. This presents a prob...

Thanks Dan. Again, we'll just reflect this in our internal process notes. Are these things that you have (or can) report to Microsoft, or is this something that you would expect your customers to report?

Thanks Dan. For now, we will just tell folks to undo this working folder assocation, to avoid problems should a developer decide to relocate their root working folder in which the IDE folder resides.

While redefining our eMVC++ IDE/Vault integration to refer to a relocated Vault repository folder, I have found that the integration process fails to update the *.VCP file for Microsoft's Emdedded Visual C++ IDE, while the *.VCW file is updated appropriately. The reason for this change was that we r...

When integrating an IDE such as Microsoft's Embedded Visual C++, please add an option not to set a working folder association between the developer's local folder and the Vault repository folder that contains the IDE's workspace definintion files, if the Vault repository folder is already inheriting...

Please note that this posting has not been responded to yet.
Thanks.
Dave

Is it possible to edit an existing label's comment, like we can edit a change set or item version comment? If not, could you please add the ability to do so. Sometimes we forget to include some level of detail (or enter a comment in the first place) at the time we label a given version of our produc...

You're right. I'm now having trouble reproducing the "exact" behavior -- in any event, the behavior is flaky. The checkin button should apply to the last thing I had focus on. If I selected a folder from the left frame, than all files checked out from that folder should appear. If I select...

Try from the same folder. All of the files that I am dealing with reside in the same folder.

I see what you mean... it is a specific set of actions... try this: 1) check out several files. 2) go to the frame to the right where the file details appear. 3) click on a checked out file in the right frame. you should see the checkin button not greyed out at this point. 4) go to the change set fr...

Not totally true. If the focus of your cursor just before clicking on the checkin icon in the upper toolbar was in the change set frame, you send up seeing a dialog with all of the files present in the change set. Maybe if the last focus was the change set the checkin button acts just like the "...

In the tool bar where you see icons for create folder, add files, label, etc, there is both a checkout icon and a checkin icon. It is the checkin icon that I am referring to. You might not want to change the "Commit All" button that appears in the middle of the screen. Does this help? (if ...

Thanks. Please be sure to include in your note both the "Commit" button and the "Checkin" button, since I am guessing that they are different peices of code -- you wouldn't "Checkin" an "add file" for example.
Thanks again,
Dave

Sorry, I should have been more explicit. I was using the "Checkin" icon in the upper toolbar -- to me this should behave just like the "commit selected operations" when just a few files are selected. Sorry about that.