To see alternate images or drop in your own proposed image see the
Announcement - I personally am halting activity in this project and have been meaning to make such an announcement for months. When I saw my first look into this functionality in Rosario I decided that efforts to address the same were not of value compared
to waiting for the Roasrio release. Also I realzed I should have looked around a little better at some alternate presentation ideas versus in this case a lot of the idea coming from the SVN approach. Roasrio I expect to provide this functionality and do it
If someone else would like to take ownership of this project and feel they'd like to move foward with it please let me know. I suspect not but let me know. I might even continue to be a contributor but think that this specific effort is best left to
If you disagree let's hear from you!
Announcement - Vertigo Beta 0.30 March 24, 2007- Released.
Vertigo Beta Minus (really an Alpha) is released. This functions as a plugin only for VSTx.
Table of Contents
Special thanks to MindFusion for going above and beyond in the support of this community coding project. I provide high praise not only in their actual product but in their special support. See
the News Feed related to MindFusion's support of this project.
Welcome to project Vertigo.
Jump into the
discussion groups; development and continued iteration
envisioning is continually underway and we want all the input we can gather.
CodePlex and a TFS Project
Project Vertigo is a project for the creation of a Team Foundation Server Source Code Version Tree Browser. If you are familiar with Tortoise SVN version tree browser or Rational's version tree browser in either BaseCase or ClearCase UCM then you know what
this is all about. Team foundation server does not provide a visual browser of the version tree around files or projects.
Definately see the
for what this is all about.
In speaking with the VSTS/TFS team this tool is known to be needed, but is not slated to be in the Orca's release. Thus the earliest we can expect the functionality in release version is following Orcas. Thus this community project is in place to begin
to fill that gap.
This is a project to fill not only a gap in TFS functionality but also to experiment with added collaborative community development. The CodePlex site with its wiki access on the front and Team Foundation Server on the back are an ideal mechanism.
If you are interested in the project and want to get in on the ground floor things are just starting to come together. The task list will continue to grow. A vision statement in an open wiki format for accepted contributors and with a comment section for encouraged
participation by the casual passer by is one of the first tasks.
Here are the basics on Vertigo:
- Check out the Table of Contents for the
Design. Whatever state these documents may be in can be made more valuable with the contribution of your thoughts.
- This project will be performed under some nature of quick iteration and for lack of a better term - Agile (as best as Agile can be performed in a virtual development team).
- The project will be targeting the 1.0 release version of Visual Studio 2005 and will also be geared toward SP1 as it is released.
- The scope for 1.0 will be strictly limited to provide the minimal set of functionality to make the tool of some value. Then we'll move on to the next rev of the tool.
- The licensing terms will be in accordance with the Microsoft Shared Source Pemissive License- so it's about as free a license as you can find.
- All of this product is not open source. There is a third party diagraming component in use with free runtime distribution and through a special agreement, an open model so that any developers on this project can develop with the tool without any licensing
fees. See the
SCM Policies and
News Feed Post related to such.
- The project will in future iterations utilize .NET 3.0 (the programmtic section formerly known as WinFX) targeted first for XP and meant to be also targeted for Vista in parallel. And you never know, you might even see an SVG based version.
As you can see from the last bullet point it would be encouraged for folks with desires to work in any number of presentation areas, or alternate technologies to join in and we'll create alternate branches for various technological implementations.
Jump in. Get involved. Technical guidance and designs are always in a state of flux. If you like what you see contribute. If you don't like what you see then definately contribute to fix it.