Vault Update

Posted by Jeff Clausius Sat, 27 Aug 2011 21:59:00 GMT

As I sit down to this entry, Hurricane Irene is 90 miles from Cape Hatteras. For those of you on the East Coast, heed all evacuation orders, and please take all precautions to remain safe.

It’s been busy for us on the Vault Dev team since my last post, and I wanted to update you on our work. We’ve made excellent progress on the cornerstone features for Vault 6. The foundational framework has been coded for both Find in Files as well as Vault Notifications, and we are now working on the UI.

For those unaware, Find in Files allows searching for a string of text within text based files stored within the repository. As a file’s data will be indexed in its own database, searches will be more efficient than keeping or GETting files to disk and running recursive greps against those files. In regards to Vault Notifications, this feature will provide a central location for you to see various source code and work item events generated by your team’s activity. Need to know when when a file has its lock released? No problem. Set a notification. Need to know when a change set is committed or a change made to a bug in a project, set a notification. Like before, the Notification service can also be configured to send email for these events.

Oh, there is also one other HUGE announcement. (OK, at least I think it’s huge.) However, I don’t want to ruin the surprise. We’ll be updating the Vault 6 road map with this info very, very soon. Please stay tuned!

Let’s switch gears a bit and talk Vault 5. We haven’t been idle here these past few months, and are tentatively planning a Vault 5.1.2 release sometime this September. Coding is just about complete, and early builds are already in the hands of our QA department as well as a few select customers. In this maintenance release we’ve addressed some nuisances as well as tried to streamline a few areas. Some highlights of this release include:

  • A new option named “Use check box as selection.” This option allows users to control the check box selection for items in the Pending Change Set list as well as items in the Search Results. When the option is unchecked, check boxes are not used, and operations are based on the selected items. When the option is checked, check boxes are visible, but the behavior of the check box is used to select the item. This behavior is similar to the Windows Explorer option of the same name found in Windows Vista/7. Also, this change allowed the “Commit” command to be placed back in the context menu for the Pending Change Set.
  • Changes in the OnTime Integration Component to account for Axosoft’s change in authentication for OnTime 2011. Axosoft made a slight change with OnTime 2011 that broke compatibility with Vault’s Integration Component. Vault 5.1.2 addresses this problem as well as allow access for OnTime user’s configured with Windows Authentication to access Defects from within the Vault GUI client.
  • A new option in the Vault Import tool which allows user’s to skip importing labels and/or keep the import running after a label error. The VSS Import tool needed to take certain liberties with the restrictions on labels when creating VSS data within the Vault repository. Unfortunately, these labels would not allow VSS imported repositories to be exported/imported correctly to other Vault repositories. This option within the Vault Import tool allows the export/import of VSS created repositories to other Vault repositories.

That about wraps up this entry, and you’re now up to date. We appreciate everyone’s enthusiasm around Vault, and as always, if you have any questions, please don’t hesitate to ask.

-Jeff Clausius Vault Dev Team

Posted in  | 2 comments

An update on Vault 6.0

Posted by Jeff Clausius Mon, 24 Jan 2011 13:23:00 GMT

Over the last month or so, we’ve been working on the planned features for Vault 6.0. There has been great internal discussion on which new features and customer requests to include in this release.

The official Vault 6 feature page can be found here at Vault 6 feature outline - http://www.sourcegear.com/vaultpro/documentation/Vault6featureoutline.html

Here are some of the more noteworthy features that are tentatively planned for Vault 6:

    Content Searching - Vault 6 will have an index on repository file content. Clients will be able to search for files containing a given text string.
    Event Notification - A new event notification system in which users will be notified directly within the client of changes to the repository or a work item.
    Classic Client - Vault 6’s Classic Client will implement the latest specification for Microsoft Source Code Control Interface (MSSCCI).

For the Vault Professional users:

    Time Tracking - Functionality for time allocation within a work item to let you manage and track the time users spent working on a feature or bug.
    Work Item Audit Trail - Vault 6 will improve functionality around capturing and displaying modifications made to a work item’s details.

Some really cool stuff!

We’re excited about this release, and are tentatively planning a Beta program for Summer 2011.

Jeff Clausius Vault 6 Dev Team

Posted in  | Tags  | 5 comments

Vault Standard/Professional

Posted by Jeff Clausius Mon, 01 Nov 2010 18:18:00 GMT

In case you haven’t heard, SourceGear Fortress underwent some changes and is now SourceGear Vault Professional 5.1.

While the release fixes some minor annoyances with Visual Studio integration, the biggest change comes in working with integrated Work Items from the Windows GUI client. Integrated work items are now center stage sharing the spotlight right within your change set. We will continue to explore new interoperability and improve our integration in future releases.

If you haven’t had a chance to see it, I invite you to download the Vault Professional client (http://www.sourcegear.com/vaultpro/downloads.html), and take a look around.

-Jeff

no comments

Veracity 0.5 Released

Posted by Paul Roub Tue, 19 Oct 2010 09:07:00 GMT

The 0.5 source release is available here.

The latest nightly build is always available here

Veracity 0.5 Release Notes:

  • Full 64-bit support
  • Core performance improvements:
    • More efficient changeset format
    • Better caching of working folder status
    • Massive DAG-walking speedup, affecting update, push, pull, etc.
  • Repository instance revision numbers (like hg’s)
  • Web UI improvements:
    • Lots of performance improvements, particularly the activity stream
    • Improved burndown chart accuracy
    • Friendlier layout for adding and editing bugs
    • Graphical DAG for source history
    • Layout improvements viewing changesets
    • Improved progress indicators throughout
    • Bug relationships: blocks, depends on, duplicates
    • Internet Explorer 8+ compatibility
  • Merge improvements
    • Default integration with SourceGear Diffmerge
    • Resolve handles additional divergent move/rename/delete cases
  • Building from source, particularly on Windows, has gotten easier.
  • In progress:
    • Integration with other diff/merge tools
    • Repository packing
    • REST API port to server-side Javascript

Compatibility Notes:

Since the 0.3 release in July, most everything has changed.

  • The repository format has changed.
  • The layout of .sgdrawer in working copies has changed.
  • The contents of ~/.sgcloset has changed.
  • REST APIs, including those used by push/pull/clone, have changed.

  • Repositories created with 0.3 will not work with 0.5, and vice versa.

  • Settings saved in .sgcloset by older builds may not show up 0.5.
  • Working copies should be recreated with the new version.
  • Clients and servers must be the same version to play nice together.

Posted in  | no comments

Vault 5.0.4 / Fortress 2.0.4

Posted by Jeff Clausius Mon, 14 Jun 2010 11:32:00 GMT

The bits have settled down for Visual Studio 2010, and we’ve been hard at work these last weeks fixing and testing issues that were either not discovered or introduced after the pre-release version of VS 2010.

Without further ado, I’m pleased to announce the fruits of our labor with the general availability of Vault 5.0.4 and Fortress 2.0.4. If you are using the Vault 5.0 - Vault 5.0.3 and/or Fortress 2.0 - Fortress 2.0.3 Enhanced Clients with Visual Studio 2010, I strongly urge you to upgrade as a couple of fixes will make integration that much better.

If you are using a previous version of Vault and/or Fortress to integrate with Visual Studio 2010, I’m glad you have it running, but as a gentle reminder, that configuration is not necessarily supported as we do not plan on testing/supporting that configuration for VS 2010.

In any case, grab the latest update and let us know how things are going.

Jeff Clausius SourceGear

2 comments

SourceOffSite 5.0.2

Posted by Jeff Clausius Mon, 22 Feb 2010 15:59:00 GMT

You can plan on a SourceOffSite 5.0.2 release very soon. Some of the items addressed:

  • Fix where IDE client will crash its host when the timers are active.
  • Fix in IDE when a GET PROJECT command is executed and client displays “Response for No Message Sent”
  • “View” changes for the GUI client’s working folder and pending changes displays for certain operations.
  • Fixed GUI client status search resizing issue

I don’t have a fixed release date just yet, but it should be out in the very near future.

Jeff

no comments

Vault 5.0.3 / Fortress 2.0.3

Posted by Jeff Clausius Thu, 04 Feb 2010 10:23:00 GMT

We just pushed Vault 5.0.3 and Fortress 2.0.3 out the door. This release addresses some of our most common issues as reported by Tech Support.

One of the more interesting changes was a logical change of how Undo is executed from the Pending Change Set. Before an UNDO would always revert the file back to its original baseline version. However, if you were working in “Check Out, Edit, and Commit” mode and were to Undo the locked file from the “File View”, users would encounter a different behavior.

For this release, we changed things so the behavior was synchronized between the File View and Pending Changes. If you have the file locked, and Undo a Check Out from either location, the Undo Check Out action is used. If you have the file just edited (and are working in “Modify, Merge, and Commit”), the file uses the old “revert” method.

There are additional changes we’ve made. You can get up to speed on the rest of the release at Vault 5.0.3 Release Notes or Fortress 2.0.3 Notes.

Jeff

no comments

Feb. 2010 Activity

Posted by Jeff Clausius Thu, 28 Jan 2010 11:30:00 GMT

We’ve been busy over the last few months. Early February, 2010, we will be posting maintenance releases:

  • Vault 5.0.3 - Notable fixes:
    • Undo Checkout of Files from Pending Change Set when file is Checked Out (vs. Modified)
    • Deleting linked files from Enhanced Client
    • Window placement adjusts for task bar on “top” or “left”
    • Restoring backups in Admin Web
    • Line History when integrated with Handoff

  • Fortress 2.0.3 - Notable fixes:
    • Email notification on attachments

  • SourceOffSite 5.0.2 - Notable fixes:
    • IDE Client handling of network disconnects
    • Sharing folder structure creation
    • Folder History Query allow ONLY Floor/Ceiling
    • Deleting a folder will clean up working folder tab

The releases are just around the corner. Stay tuned.

Tags , , ,  | 4 comments

SourceGear - Behind the Scenes

Posted by Jeff Clausius Thu, 29 Oct 2009 09:04:00 GMT

My name is Jeff Clausius, one of the developers at SourceGear. I would like to give you guys a “behind the scenes” look at issues encountered during the development of SourceGear products. The topics here may be very narrowly defined, focusing solely on subject matter that may not appeal to everyone. But having products based in C/C++, C#, Java, MFC, and SQL Server, we should have enough variety to cover a broad range of subjects.

With out further ado, today I present -

SourceOffSite 5 : Command Routing for CDockablePane (MFC)

One of the more challenging development pieces of SourceOffSite 5 (SOS) was to provide Document-View (Doc-View) functionality with classes inherited from the CDockablePane class. CDockablePane is great for providing a small window that can either be docked in a dock site or included in a tabbed pane. However, the class itself does not participate in the Doc-View architecture and does not handle messages for ON_COMMAND(), ON_COMMAND_RANGE(), ON_UPDATE_COMMAND_UI() and ON_UPDATE_COMMAND_UI_RANGE() generated from other areas of your MFC application. This presented a problem since we wanted the “Folder View” of SOS to reside in exactly that type of window.

At first it was thought we could create a class using multiple inheritance of CView and CDockablePane, but since each class derives from CWnd, it was undefined what would happen with messaging having two classes both deriving from CWnd, and this idea was quickly abandoned.

Creating a class derived from CView and then implementing the features of CDockablePane was another option, but we decided against this as the time it would take (and bugs we could possibly introduce) would be too great implementing CDockablePane functionality.

In the end, we went back to the drawing board looking for an easy way to get messages over to the CDockablePane classes. We finally turned to one of the slickest features of MFC - Command Routing.

With command routing, “windows messages are usually sent to the main frame window, but command messages are then routed to other objects. The framework routes commands through a standard sequence of command-target objects, one of which is expected to have a handler for the command. Each command-target object checks its message map to see if it can handle the incoming message.” This would be perfect for the needs of SOS.

Since SourceOffSite’s MDI windows consisted of one class for CMDIFrameWnd and one base class of CMDIChildWnd for the other SOS MDI children, we were able to interject our own routing handler into the base classes of these windows at ::OnCmdMsg(). The code first sent the message to any dockable panes which registered themselves with the main application within their own OnCreate(). The CMDI*Wnd::OnCmdMsg() would then send the message onto the base classes if the message was un-handled by any Pane. In regards to the classes inherited from CDockablePane, a m_pDocument member and GetDocument() method were added similar to any CView derived class, and the ::OnCmdMsg() methods ended up routing messages directly to the document’s OnCmdMsg().

I’m not sure this was the most elegant solution to the problem, but in the end we ended up with a framework of classes (with some interdependencies) that was able to use Document-View message handling with CDockablePane based classes.

no comments

SourceOffSite 5 Release

Posted by Jeff Clausius Wed, 28 Oct 2009 16:28:00 GMT

We’re done! SourceOffSite 5 has been pushed out the door!

A special thank you to the developers, Q/A, Artists, and everyone else involved. SourceGear has worked hard to make sure this release addresses the needs of those users who want faster access to their VSS databases.

Thanks again to all involved who made SOS 5 a reality!

Jeff

no comments

Older posts: 1 2 3 4 ... 6