Recently in Teamprise Category

Team Explorer Everywhere World TourEd Thomson from the Team Explorer Everywhere team is going to be doing a tour of the mid-west and central United States in early April.  For those of you who don’t know Ed, he is one of the original Teamprise developers that came over to Microsoft after the acquisition and now one of the core developers on Team Explorer Everywhere.  He knows more about the inner workings of our Eclipse integration than anyone else on the planet.

While he’ll be speaking at a lot of user groups and Microsoft events in various cities, places are filling up fast.  However there is still some availability in a few cities.  If you are nearby or know someone who is then I encourage you to register and come along.

Austin TX


  • Wednesday April 6 (Details soon)


  • Thursday April 7 2:00pm – 4.30pm (Register)
  • Thursday April 7 6:30pm - 8:30pm (Register)


  • Friday April 8 9:00am – 11:30am (Register)

CodePlex People using CodePlex can download Visual Studio Team Explorer to access a CodePlex hosted TFS instance free of charge, but what if you want to be a project team member and access the code from Eclipse or a non-windows machine?

Well, I’m proud to say that we’ve continued the tradition and you can now use Team Explorer Everywhere with CodePlex.  Simply download the trial edition of Team Explorer Everywhere and then enter the license key given on the CodePlex wiki.  Note that if you already have a full license to Team Explorer Everywhere (either through retail, volume licensing or MSDN) then you can obviously use this to access CodePlex as well.

Just a quick tip.  When adding the connection, be sure to hop over to the Advanced tab to ensure that you do not have “tfs” in your path.  CodePlex has it’s TFS servers at the root of the server location (as required by older TFS clients and older versions of TFS) – but the Team Explorer Everywhere client will default to the TFS 2010 convention of looking at https://servername/tfs unless you tell it differently.  Also some of SSL certificates on some of the CodePlex servers are signed by a root certification authority that is not in the Java Certificate Store in all Java Runtime Environments running today.  If you run into this problem and you are having SSL issues then you can add the root CA to your Java certificate store.  An easier way is to un-check the “Accept only trusted SSL certificates” which will disable the root certification authority check for the SSL connection to the CodePlex server – but bear in mind that reduces the security of the communication between your machine and the CodePlex server.


Advanced settings for a codeplex connection

Let me know how you get on.  I’m excited to see who takes us up on this offer.  As an encouragement, I’ll send a free copy of my book to the first person who emails me a screenshot of them contributing to a project on CodePlex using Team Explorer Everywhere.

Team Explorer Everywhere In case you missed it, as part of Bob Muglia’s keynote announcing the launch of Visual Studio 2010 last week he also announced the launch of Microsoft® Visual Studio® Team Explorer Everywhere 2010.  This is the initial release of the bits that Microsoft acquired from Teamprise back in November and this release is the result of what my team has been working very hard on since that acquisition.

Team Explorer Everywhere contains the following components:

I’ll post more about what functionality is included in this release, but first I wanted to talk about what this means to existing Teamprise customers.

Teamprise customers should have already got a couple of emails from the company. If you haven’t then head on over to the following site for more information (  Basically when Microsoft shipped it’s first release, Teamprise ceased sales of the existing products and will begin the process of wrapping up the company.  Microsoft will be the contact point from now on for all purchases and support enquiries.

Teamprise 3.0 customers are entitled to a free upgrade to the new Team Explorer Everywhere 2010 version.  You can find out the full details of eligibility and how to claim this license at the following page on the pathways site (

If you are a new customer, you’ll be please to know that Team Explorer Everywhere is now also included in the Ultimate level MSDN subscription and is also available as a standalone product for folks without the top tier MSDN Subscription (or indeed without any MSDN Subscription).

If you have any questions of feedback about all this then the pathways site has contact details.  You can also discuss things over on our MSDN Forum.

Working on Teamprise has un-doubtably been the highlight of my career prior to joining Microsoft, and I have to confess to at having a tinge of sadness that the brand we created in our little start-up is going away.  That said all the developers who worked on the product came over to Microsoft and were part of the team that got this new release under the Microsoft banner out the door.  We all worked long hours to ensure that the new version was able to take advantage of many of the TFS 2010 features and I’m very proud of what we managed to accomplish since November.  Also, we’re obviously not stopping there.  Since shipping the initial release we’ve continued development and are hoping to keep getting more functionality out the door.  In addition, now that we are part of the core Team Foundation Server team we get to influence the future direction of the product in ways that I cannot even predict at this time.  The TFS team were always very good at listening to our feedback from a cross-platform point of view – but now we’re all part of the same team we’re even harder to forget :-)

But more on all this soon.  I’ve been so busy helping get Team Explorer Everywhere 2010 shipped along-side the rest of the Visual Studio 2010 release that I’ve been neglecting my blogging and podcasting duties.  But it’s great to be back!

What’s in a Name?

When the Teamprise technology was acquired by Microsoft, one of the first non-TFS 2010 feature things that we knew we needed to do was change the name.  You’d think re-branding would be simple, just do a global search and replace for “Teamprise” and replace with the official Microsoft name – and then reformat everything because the Microsoft name is obviously going to be longer :-)  Obviously nothing is that simple.  It took a while before we decided on a name, at the moment we are Microsoft Team Explorer 2010 codename “Eaglestone” – which in the team we sometimes abbreviate to “TEE” (because it is shorter, but it is also handily a slight homage to the Teamprise logo which is the T power button).

However, in the past we used “Teamprise” to mean different things.  For example we have “Teamprise” views in Eclipse.  When you whent to import a project from Team Foundation Server you selected “Teamprise”.  Sometimes we used Teamprise as a product name, sometimes as a metaphor for accessing TFS. Sometimes we used it under the covers as well – for example as the name of an annotation in version control when storing check-in polices or as the layout type when doing work item forms. 

Montage of Teamprise screens showing branding choices

This was a deliberate decision at Teamprise.  When we started we were just a plucky start-up convinced that we were one of many working to put TFS into Eclipse.  We wanted to make our name synonymous with accessing TFS from Eclipse so that people would think of us instead of a competitor.  But we also wanted to allow competing products to exist in the same Eclipse installation so that users had choice as to which TFS connector they used and it wasn’t too confusing for them.  Largely this was a success.  We got a solution to market at the right time and managed to keep improving the technology and a competing product never really appeared.  To people who know Team Foundation Server, Teamprise == TFS in Eclipse and Teamprise == TFS cross-platform.

But, there was a whole world of people that we didn’t reach.  People would always need to know to ask “How do I connect to TFS from Eclipse, or How do I connect to TFS from the Mac” and be given the answer of Teamprise (either by a person or a search engine).

Now that we are part of the Team Foundation Server team, it doesn’t make sense to be as “visible” anymore as a brand in the UI.  When you are connecting to Team Foundation Server in Eclipse or want to see Team Foundation Server resources – you should look for Team Foundation Server.  When looking for how to connect to TFS from Eclipse, you should look for the product that contains a “Team Foundation Server plug-in for Eclipse”.  It is now Team Foundation Server we want you to connect with (both literally, and from a branding perspective).  All this means that it is more complicated than just doing a search/replace in the UI as now we need to figure out when we were using Teamprise to talk about TFS and when we were using it to talk about the software that you plug-in to Eclipse.

Montage of screens taken from the new Microsoft release

And then there was package renaming.  All of our code used to be in com.teamprise packages.  Some classes were called things like “TeampriseLogConfiguration” etc etc.  In each case decisions had to be made on individual merit rather than being able to come up with a simple automated cookie cutter approach.

The following is what we ended up with:

  • In the UI, when talking about connecting to Team Foundation Server use that name and the TFS icon.
  • Packages moved from com.teamprise.* to*.
  • Class names sometimes went from Teamprise* to TFS* or TEE* depending on use, or got a different name entirely.
  • Eclipse plug-ins moved from com.teamprise.* to*.   We also took the chance to do some refactoring here to make the plug-in names more sensible now that the codebase is much more mature and the roles and responsibilities of each plug-in is better defined than it was back at V1.0 of Teamprise when some of them were originally created.
  • Extension points moved from com.teamprise.* to the appropriate plug-in* based name.  This is important if you were previously using the Teamprise extension points to add integration into our plug-in from yours.  I’ve spoken to the customers and partners that I knew of that were doing this – however I expect more will want to once we make the initial Microsoft release and so we wanted to get the naming right now.
  • Check-in policies keep their Teamprise based annotation names in version control.  This fact is totally transparent to end users, but means that we retain backwards compatibility with older Teamprise client defined check-in policies.  It also means that partners like JetBrains who have their own check-in policy implementation in the IntelliJ IDE that uses the “Teamprise” scoped mechanism for check-in policy storage need not change their code.
  • The .tpattributes file lives on as the file that is used to store unix execute bit permissions etc, the .tpignore file lives on as the file you can use to specify resources that Eclipse should ignore.  Again this was for backwards compatibility.  We could have gone down a route where we searched for “.tfsignore” first etc but we’re hoping to be able to reduce the need for these files at some point in the future by making use of the new properties capabilities in TFS 2010 so we decided to leave alone.
  • In the work item layout target names, “Teamprise” used to be the name of a layout target that was for the Teamprise client.  “Teamprise” is still accepted (for back-compat) but a layout with the target name “JavaSWT” now takes preference.  Therefore when we are looking for a layout target in Eclipse we look for one called:
    1. “JavaSWT”, followed by
    2. “Teamprise” followed by
    3. “WinForms”, followed by
    4. the last unspecified layout. 

If all this talk of layouts doesn’t mean anything to you then do not worry.  Neno has a good post here where he talks about using separate layouts for Web Access and Visual Studio where you will get the idea.

Hope that makes sense, we will have a beta out soon where you can take a look for yourself.  The moral of this story is that if you have to re-brand your codebase due to acquisition then be prepared that it will take more thought and effort than you might have originally estimated.

We are Hiring!

Since joining Microsoft it has been fantastic to see how committed everyone is to the technology that was acquired from Teamprise.  When Microsoft purchased the Teamprise technology, they also hired all the developers (including me) and are investing heavily not just in the 2010 release but more importantly the long-term future of heterogeneous development using Team Foundation Server.  Since joining Microsoft we’ve grown the team with some fantastic developers (both Software Development Engineers and Software Development Engineers in Test) who we poached from others parts of the company.

We are now after one more person to join our little family. We need someone to help us with our User Education work.  If you know of a technical writer that might be interested in working with us then please send them over to this job posting at Microsoft Careers ( This role is based in Raleigh, North Carolina, USA

I promise you, it is a very exciting time to be joining our team.  I am looking forward to showing you a bit more of what we have been working on soon!

Four years ago this month, I joined a small start-up being created called Teamprise after reading about it on Eric Sink's blog. Our mission was to bring the benefits of application lifecycle management (ALM) with Microsoft Team Foundation Server to everyone. After all, your customers and requirements do not care about the artificial technological borders inside your organisation - so why should your ALM tools?

Today we start a new chapter in the story of accessing Team Foundation Server from Eclipse and non-Windows platforms with the announcement that Microsoft has acquired the Teamprise technology and will be releasing a new TFS 2010 targeted version next year.

As part of the deal, I was lucky enough to get offered a position as the Program Manager for this product in Microsoft - a role that I start properly today. As a (now former) Visual Studio MVP I've had a great relationship with the team behind Visual Studio and Team Foundation Server, and I am incredibly excited to move into that very same group. I'm joining a team of people that I consider my friends - a team that consists of some of the smartest people I have ever had the pleasure of working with.

Microsoft has always been committed to creating an ALM solution that was ready to support the entire enterprise and I think this commitment is demonstrated in their decision to support cross-platform and Eclipse clients under their own name. It is also a sign of how clearly the Visual Studio team listens to their customers.

There are obviously going to be some changes along the way, however we're trying to do the best we can to minimise negative impacts. The same core team of developers behind Teamprise is moving to Microsoft to carry on what was going to be Teamprise 4.0. Until Microsoft ships its version, Teamprise 3.3 will continue to be sold and supported by the Teamprise division of SourceGear. If you are an existing Teamprise customer, you will be contacted shortly to help understand what the deal means for you – but the short version is that people with a valid Teamprise 3.3 license and a TFS CAL should be eligible for an upgrade to the new version that will come from Microsoft. That said, feel free to take a look at the FAQ to see if this helps, head over to the Teamprise Support forums, or drop me a line at if you have any questions or concerns that are not being answered and I'll do my best to help.

From a personal point of view, I'll continue to live in rural Northern Ireland as a remote member of the team. I also intend to continue to blog and tweet. I'll try to minimize the number of the "wow what a crazy awesome place Microsoft is to work" type posts that you see from new hires - but I probably won't be able to resist the odd one or two.

I'm very excited about all that we will be able to do with the resources of Microsoft behind us. While I officially have the job title of Program Manager, I’ll be heads-down coding for the next few weeks and months and looking forward to seeing what my new team and company come up with next year.

I'll be posting more here as this particular chapter continues, stay tuned – I’m pretty sure the next 12 months are going to be an exciting time!  For more information don’t forget to take a look at Brian Harry’s blog post on the topic.

One of the features in Teamprise 3.3 is the ability to connect to a Team Foundation Server 2010 Beta 2 project collection.  The support for TFS 2010 Beta 2 in Teamprise is very similar to the support you will find in a patched Visual Studio 2008 instance – you can connect and work correctly, however some of the new TFS 2010 features will not be available.

The URL syntax in TFS has changed slightly with the 2010 release.  Previously, all URL’s were relative to the root of a server, but with the introduction of project collections you have a longer URL in the form of


Where “servername” is the name of your TFS instance, “8080” is the port, “/tfs” is the virtual directory that TFS is installed in and “DefaultCollection” is the name of the project collection you want to connect to.  Like Visual Studio 2008, Teamprise 3.3 cannot connect to the application instance to determine which project collections are available – you have to be provided the name or URL from your TFS administrator.


However you can connect now using one of the new URL formats, and if you have a Sharepoint site or a reports site configured their correct locations will be used in Team Explorer.  If you have performed a basic installation of TFS (i.e. with no Sharepoint or Reports services configured) then the Documents and Reports nodes in Team Explorer will just not display.


Creative Commons License
This blog is licensed under a Creative Commons License.