Search found 68 matches
- Wed Jun 24, 2009 12:23 pm
- Forum: Support (Fortress)
- Topic: Pending Add fails for DataSet code file
- Replies: 6
- Views: 7630
Re: Pending Add fails for DataSet code file
Thanks for the work-around. I tried clicking on the missing file itself, but not on the "parent" file.
- Wed Jun 24, 2009 9:52 am
- Forum: Support (Fortress)
- Topic: Pending Add fails for DataSet code file
- Replies: 6
- Views: 7630
Re: Pending Add fails for DataSet code file
I added the file manually.
Also, I'm using the enhanced client with VS 2008.
Also, I'm using the enhanced client with VS 2008.
- Wed Jun 24, 2009 8:18 am
- Forum: Support (Fortress)
- Topic: Pending Add fails for DataSet code file
- Replies: 6
- Views: 7630
Pending Add fails for DataSet code file
[6/24/2009 8:52:05 AM] Version Check: This Fortress client is version 1.1.4.18402 [6/24/2009 8:52:05 AM] Version Check: Your Fortress server is version 1.1.4.18402 [6/24/2009 8:52:05 AM] Version Check: The following information was retrieved from the SourceGear website. No information was sent to So...
- Wed Jun 03, 2009 7:42 am
- Forum: Questions (API)
- Topic: VaultFileProperties.SharedPaths
- Replies: 3
- Views: 6600
Re: VaultFileProperties.SharedPaths
Thanks, Shannon, that gave me exactly what I needed.
- Mon Jun 01, 2009 3:56 pm
- Forum: Questions (API)
- Topic: VaultFileProperties.SharedPaths
- Replies: 3
- Views: 6600
VaultFileProperties.SharedPaths
I'm trying to create an automated process using VaultClientIntegrationLib. VaultClientOperationsLib.VaultClientFile.GetProperties() returns a VaultLib.VaultFilePropeties object, but the SharedPaths array is null, even when the file in question has Share Links. Is there something extra that must be d...
- Fri May 29, 2009 7:51 am
- Forum: Support (Fortress)
- Topic: Adding functionality to Fortress/Vault
- Replies: 1
- Views: 3248
Adding functionality to Fortress/Vault
Is it possible for us to add functionality to the Fortress client?
Specifically, I'm curious if I can add a menu-item to the context menu that appears when you right-click a project (folder) in Fortress that would then run code compiled against the VaultClientIntegrationLib.
Specifically, I'm curious if I can add a menu-item to the context menu that appears when you right-click a project (folder) in Fortress that would then run code compiled against the VaultClientIntegrationLib.
- Thu May 28, 2009 1:15 pm
- Forum: Support (Fortress)
- Topic: Pin/Rollback from Command-Line Client
- Replies: 7
- Views: 7650
Re: Pin/Rollback from Command-Line Client
Thanks for the suggestions but I'd still like to encourage you to implement Rollback in the CLC. As I tried to explain above, we don't really have a convenient way to deal with Folders. Rather, we almost always are dealing with an arbitrary group of individual files that may or may not have been gro...
- Fri May 22, 2009 12:46 pm
- Forum: Support (Fortress)
- Topic: Pin/Rollback from Command-Line Client
- Replies: 7
- Views: 7650
Re: Pin/Rollback from Command-Line Client
I've read everything I could find on this, and I understand your setup, but I'm not really sure it would work well in our situation. What you describe would work well where you have well-defined, persistent units of deployment, such as Visual Studio Solutions (or even Projects). However, we have a l...
- Fri May 22, 2009 9:19 am
- Forum: Support (Fortress)
- Topic: Pin/Rollback from Command-Line Client
- Replies: 7
- Views: 7650
Re: Pin/Rollback from Command-Line Client
Please! :) We are trying to keep a "Base" folder structure in Fortress that matches our deployed scripts/programs. We share from this Base to our Dev folder structure, keeping the base Pinned to what's been deployed. When we Deploy what we've worked on in Dev, we want to be able to automat...
- Thu May 21, 2009 12:50 pm
- Forum: Support (Fortress)
- Topic: Pin/Rollback from Command-Line Client
- Replies: 7
- Views: 7650
Pin/Rollback from Command-Line Client
We're trying to automate a Deploy/Abort process using Pin and Rollback but the Command-Line Client doesn't seem to support Rollback. Are there plans to add this feature? Or have I simply over-looked it?
- Mon Feb 02, 2009 8:22 am
- Forum: Support (Fortress)
- Topic: Should pinning affect both sides of share?
- Replies: 3
- Views: 4137
Re: Should pinning affect both sides of share?
I placed the Pin at a sub-folder of the Share. I was hoping to create MyProject1, MyProject2, etc. under $/Projects, then share Projects to $/Test/Projects, and then be able to Pin MyProject2 to version 7 under $/Test/Projects while I continued working on it under $/Projects. I just did a little tes...
- Fri Jan 30, 2009 3:27 pm
- Forum: Support (Fortress)
- Topic: Should pinning affect both sides of share?
- Replies: 3
- Views: 4137
Should pinning affect both sides of share?
I just read through "Basics of using Label, Cloak, Share, Pin, Branch and Merging" ( http://support.sourcegear.com/viewtopic.php?f=13&t=9&p=9&hilit=pin#p9 ) looking for a way to promote changes up the ladder from dev to test to production. From what I read there, it sounded lik...
- Tue Oct 21, 2008 8:33 am
- Forum: Support (Fortress)
- Topic: Check-In dialog suggestion
- Replies: 1
- Views: 2507
Check-In dialog suggestion
It would be very convenient if you could make the file name column in the check-in grid fit into the column such that the file name was always visible and whatever portion of the path that couldn't be displayed would be converted to '..'.
- Wed Sep 03, 2008 2:07 pm
- Forum: Support (Fortress)
- Topic: Feature Requests - My Open (All Projects) and Label in VS
- Replies: 3
- Views: 32162
Feature Requests - My Open (All Projects) and Label in VS
I've been using Fortress for a few weeks now, and I'm very happy with it. However, there are two features that I think would make it a lot better. First, a "My Open (All Projects)" query inside the Visual Studio integrated client would be very useful. I can get to this from the web-client,...
- Fri Aug 22, 2008 6:57 am
- Forum: Support (Fortress)
- Topic: Vault to Fortress upgrade, problem re-binding
- Replies: 15
- Views: 13773