SourceGear Support

I believe you need to be more clear about installation on Microsoft Server 2003. Your "Knowledge Base" is confusing. It talks about installation of IIS/ASP.NET before .NET Framework 1.1, yet on 2003, .NET Framework 1.1 is already part of the OS. You have documented how to turn on IIS and A...

As far as I can see, there is no way to "uninstall" .NET Framework 1.1 in Windows Server 2003. It looks like it is now an integrated component of the OS. You can't go to Add/Remove Programs and find a "Microsoft .NET Framework 1.1" component to remove. As a result, it seems like ...

I wish to install the latest version of VAULT server on a fresh Windows Server 2003 machine. I notice that .NET Framework 1.1 is already installed yet the installation instructions talk about needing to install IIS/ASP.NET before .NET Framework is installed. Is this the case for Windows Server 2003....

If we can trust developers/users to branch, pin, merge, label, etc. --- all functions which require a decent understanding of what's going on, then I believe we can trust them to know the difference between destroying something forever and deleting something for the purpose of preserving version his...

After thinking about your comments and discussing this issue more with users of VAULT, it is not reasonable to visit an "obliteration user interface" (no matter how good) to perform permanent deletion of files later in time. The user generally knows if they wish to permanently remove a fil...

Hi All, It's been a while since I posted the original item that started this thread. After reading Mike's comments, I think that improving the obliterate user interface (and its response time) would solve my issue. What is the plan to improve this? The last posting mentions 4.0... when is that relea...

Hi Folks, Currently using VAULT 3.0.7. Our engineers would really like to be able to mark a set of files for obliteration, not simply deletion (like you could do with SOS Collab). We are finding that a huge number of files get mistakenly added to VAULT over time, then they are deleted, contributing ...

I understand how the new "feature" in Dragnet of specifying an issue type (features, discussion, bugs, etc) has introduced a change to the Assignee list contents. It seems like the Assignee list should become a security specification where you have Read/Write/Modify/Assignee. Under Assigne...

Yes. The import is being performed on the same machine as the SQL server database and the SOSCE database.

You have changed the meaning of the "Development" group in Dragnet from what it was in SOSCE as it pertains to the Assignee list. Why have a "Development" group at all? The bug is that only members of the Development group should be listed in the Assignee list. That is what shoul...

In SOSCE bug tracking, the Assignee in the bug form contained a list of all users who belonged to the "Development" group of the project. If you wanted people to read/write to bugs but not be someone who could appear in the Assignee list then you had to create a group with read/write privi...

I am trying to import 3 projects from SOSCE 1.1.2 into Dragnet 1.0.2 using the 1.0.2 collab import utility. As reported by others under this topic, the tool hangs when it comes to importing attachments. I do have a fair number of attachments connected to various bugs in these projects. What is the s...

Deletion of the cache files for the user that sees this problem fixes the issue. Thanks.

Vault 3.0.0 and 3.0.1 Repository has folder security enabled. All users have R/W access to the repository. Files were added to a directory, then deleted, then obliterated, then added again. The result is that some users (other than the user that performed the actions) see two versions of the same fi...

I found a way to uninstall Vault Client 3.0. If you select the "Change" button in the Add/Remove Programs dialog instead of the "Remove" button, then a dialog prompts you to "Repair" or "Remove". When you select "Remove", the application gets removed...