Team Foundation Server Roadmap

re: Team Foundation Server Roadmap

Jamie — Thu, 30 Nov 2006 19:27:20 GMT

(with big grin on face) I keep telling everyone in the company that not only is TFS very cool right now, but that "this is only the beginning". I'm very happy to see you guys really gaining momemtum following the v1 release. Keep it up!!!

Roadmap für den Team Foundation Server

Lars Keller ...inspired by .NET — Thu, 30 Nov 2006 20:11:46 GMT

Roadmap für den Team Foundation Server

Lars Keller ...inspired by .NET — Thu, 30 Nov 2006 20:11:56 GMT

Roadmap für den Team Foundation Server

.NET Developer BS Blogs — Thu, 30 Nov 2006 20:24:14 GMT

Wie geht es weiter mit dem TFS? Was ist alles in der Orca Version enthalten. Welche neuen Features wird

re: Team Foundation Server Roadmap

Klaus Enevoldsen — Thu, 30 Nov 2006 22:54:49 GMT

Very exciting reading, thank you for the update.

Client Remember Passwords?

onovotny — Thu, 30 Nov 2006 23:30:11 GMT

Can the outstanding issue of clients not storing credentials please be fixed for Orcas?

This is an issue for hosted scenarios where the TFS server isn't in the same domain as the developer. Currently, the user needs to enter the username/password every time they connect. There should be an option to save these and only prompt if it doesn't work...

Thanks,

--Oren

re: Team Foundation Server Roadmap

James William Dumay — Fri, 01 Dec 2006 01:44:39 GMT

Brian,

How soon is soon for the final release of TFS SP1? We really need those fixes and are going to be running SP1 Beta in production by early next week.

A rough timeframe would be nice :)

James W. Dumay

CargoWise edi

www.cargowise.com

Team Foundation Server Roadmap now available

My VSTS Blog — Fri, 01 Dec 2006 02:51:47 GMT

As promised, Brian Harry has new posted the Team Foundation Server Roadmap on his blog for all the world

re: Team Foundation Server Roadmap

bharry — Fri, 01 Dec 2006 03:24:37 GMT

I'll get back to you on the credential caching. I'm looking into the status on that.

I'd give anything to be able to give you a date for SP1 but I've been asked not to say anything until after the marketing team announces it. All I can say is that it is getting really close. We're in the final countdown now.

Brian

Team Foundation Server Roadmap

Lorenzo Barbieri @ UGIblogs! — Fri, 01 Dec 2006 08:10:15 GMT

Team Foundation Server Roadmap

寝ても覚めても.NET（？） — Fri, 01 Dec 2006 10:28:48 GMT

bharry's WebLog より Team Foundation Server Roadmap ざくっと読んでいる感じだと・Orcasに合わせてはマイナーバージョンアップを行う・次期TFSはLonghorn

Brian Harry's Team Foundation Server Roadmap

Rob Caron — Fri, 01 Dec 2006 12:12:18 GMT

Brian Harry posted the roadmap his team is following as they work on future releases of Team Foundation

re: Team Foundation Server Roadmap

Faraz Ahmed — Fri, 01 Dec 2006 13:05:41 GMT

Really appreciate the commitment… and quite happy to see the progress and the future updates but at the same time disappointed not having major improvements in WorkItem tracking and ms project integration... looks like we should start working on TFS and WF integration to achieve our goal..  Anyway keep it up man…

Roadmap de Team Foundation Server

Luis Fraile — Fri, 01 Dec 2006 13:13:47 GMT

Bueno el segundo post del día, y eso que voy liado, pero me ha parecido muy interesante publicarlo, y

Team Foundation Server roadmap

Sane Productions — Fri, 01 Dec 2006 14:29:36 GMT

Team Foundation Server roadmap

re: Team Foundation Server Roadmap

bharry — Fri, 01 Dec 2006 15:53:53 GMT

I hear you on the work item tracking improvements. You can see from the list that there isn't much there for WIT in Orcas. Don't think there's nothing - there's actually a fair amount of bug fixing/fit and finish stuff but not really any major features. We are investing heavily (already)in work item tracking for the release after Orcas and I expect we'll show some major advancements in WIT then.

Brian

re: Team Foundation Server Roadmap

Asher — Fri, 01 Dec 2006 16:22:58 GMT

Hi Brian,

What's missing for me is the ability to do operations & administration on a project level.

Things like project archive,restore,move, etc...

You currently only support deleting projects...

and in case of a single project gets corrupted (maybe due to a human error), the only options is to restore the whole server, potentially harming work on other unrelated projects.

Asher

VSTS Links - 12/01/2006

Team System News — Fri, 01 Dec 2006 17:09:56 GMT

The SRLTeam Blog on Setting TFS Notification Problem. Rob Caron on Orcas Feature Specs Online and...

bharry's WebLog : Team Foundation Server Roadmap

adamga's WebLog — Fri, 01 Dec 2006 18:51:14 GMT

Awesome. As usual, Brian has posted some great information on the roadmap for VSTS. A great read. I've

TFS Roadmap now available

Jeff Beehler's Blog — Fri, 01 Dec 2006 19:04:43 GMT

Brian Harry's been hinting for some time that he'd post the release roadmap for Team Foundation Server

More on the Orcas features for Team Build

Buck Hodges — Sat, 02 Dec 2006 08:33:26 GMT

Brian Harry posted a TFS roadmap . I'd like to expand on the portion that describes the features specific

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 15:24:32 GMT

Here is a thing not directly related to TFS, but still. What would be excellent is a new complete image of Visual Studio Team Suite for SP1 that has Team Explorer and data dude integrated. We reinstall fairly often, and it is getting more work all the time. Once SP1 and data dude are out, even a normal install of VS on a clean machine will be a lot of steps:

- VS Team Suite

- Team Explorer

- Data Dude

- SP1

Just to get started! A new, unified install DVD would be fantastic and solve a LOT of trouble for us.

Now, it would be really cool of course to also have Workflow, Office 2005 SE included :)

I do like the idea of having small add on releases all the time (like it happened with VS2005), but I still think there is a need for you guys to hand out roll up DVDs fairly regular...

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 15:26:57 GMT

"Non-default ports & web sites"

The one thing that would be great there would be the ability to run everything within one IIS web site (or two, in case you can't seperate the WSS admin stuff out). But at least the TFS web service and the WSS site should be able to run in one web site. This would ease things a lot, since essentially all trafic between the client and the server could go to 1 IP and 1 port (https, ideally).

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 15:28:58 GMT

"Collaborate with remote, distributed, disconnected and outsourced teams"

Would that include full offline support? I think that is one of the major problems for us right now, that the offline experience is very bad.

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 15:31:38 GMT

"Share Point 2007 support"

Have you thought about integrating a lot deeper than currently the case? In particular, maybe even move the work item tracking stuff to WSS lists? They seem powerful enough with WSS3 to me.

For the post Orcas release, are you in particular looking at

- Using WF for workflow?

- Infopath for work item forms (use their web and rich client package to have web and client edit capabilities)

- Store work items in WSS? They have different content types etc, which should enable that fairly easily

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 15:35:32 GMT

Another area for improvement: Authentication. Ideally I would like to have support for federated authentication. As an admin I would like to be able to say "I grant access to the individual with the Passport/Yahoo/Google account X", and then let that part deal with authentication. When such an external user wants to access a TFS, the Windows Cardspace UI could pop up, he would pick a managed card and log in with that. I believe all of that should be fairly easy if those identity providers support the WS-* stack... Not sure, for scenarios where you have one external individual work on a project it would be great if we would not have to create a new user account on our machine but just grant access to a user that is authenticated by someone else.

re: Team Foundation Server Roadmap

bharry — Sat, 02 Dec 2006 15:37:44 GMT

Whew, one at a time :)

There has been some talk about re-releasing a new image with SP1 rolled in. I haven't heard of talk to rerelase with Data Professional rolled in but I've sent off mail asking for the status on our thinking. I'll try to get back to you as we see what our plans are.

Brian

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 15:45:22 GMT

And finally, it would be great to sort out licensing. Make it a LOT easier. I don't really have a good idea how to do it, but generally I feel that right now the CAL model is a real barrier to entry for some loosely managed projects that span organisations.

Some (random and not consistent) ideas:

- Don't require a CAL for read only access

- Make it cheap (or free) to let people be integrated into the WIT stuff, at least for a web access type of thing

- Make your client revenues by selling client software, but allow free access (without a CAL) for people that use third party client software

- Make it VERY easy to purchase a CAL online for individuals that is not bound to a server. So that we could tell external contributors to a project "You need a CAl, either one purchased from your organisation, or surf to www.something.com and buy it with your credit card". EASY and QUICK are the keywords

- Sell a per processor license for the server that doesn't require any CAL

Any of the above would be an improvement over the current situation. Right now the licensing really prohibits the use of TFS for any project where you don't have a very tight control over the people that could collabarate in the future. Money is one issue, but the other one is the complication of the whole process. The scenario you should enable is "A team is working on a project. All of a sudden they want to bring someone external on board. Sorting out the licensing stuff takes exactly 15 minutes" That could be achieved by offering web buy for CALs. But you need to come close to a project that is using something like Subversion, where I point an external contributor to the SVN download and give him the URL of the server and then he can start. There should maximally be one more step for TFS, buying something online.

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 15:46:18 GMT

Yes, I am on a roll ;) Thought I do them in extra posts to make it a bit easier to handle :)

re: Team Foundation Server Roadmap

bharry — Sat, 02 Dec 2006 15:47:43 GMT

Sites & Ports - Interesting, we've never really talked about trying to combine TFS, WSS and Reporting services to one IIS web site. It's an interesting idea and would simplify some connectivity things. On the other hand it may also create some dependency problems that make the system more fragile. We'll look at this idea and see if we think it is workable.

Offline - Yes. We are looking to improve the offline experience a bit in Orcas but I think we are going to have a fantastic offline experience in the release after Orcas.

WSS integration - Yes, we are looking at deeper integration with WSS. I'm not sure we'll get anything into Orcas - the only thing we're looking at right now is something around improving the relationship between SharePoint document libraries and TFS Version control. The other things you mention are on our list of things to look at but we've got a ways to go.

Authentication - Yes, that's on our list too. We're not doing anything for Orcas but it's something I hope to have in the release after Orcas. We still haven't made it far enough on our plans to know for sure if it will make it or not.

Wow - that's a lot of suggestions! Thanks a ton.

Brian

re: Team Foundation Server Roadmap

bharry — Sat, 02 Dec 2006 15:57:57 GMT

Licensing - We've gotten a lot of feedback about licensing - particularly about complexity. We've been reviewing that feedback to see what if any changes are appropriate. Interesting about the "loosely coupled team" scenario. It's not one we've spent a ton of time thinking about. I'll ponder it a bit.

I think it's unlikely we'll abandon the CAL model. We believe TFS is a platform and we see a world in which lots of people use clients implemented by others (either commercial or non-commercial). A huge amount of our cost is building the server and therefore, it's hard for us not to monetize it in some way. With all of its issues, the advantage of the CAL model is that it allows us to monetize the server in a way that the price scales with the number of users. The problem with straight CPU licenses (for us at least) is that a CPU can probably support 250 users or more. If we are going to create a price that compensates us appropriately for that, almost certainly prices it out of range for a 20 person team.

All that said, I'm very receptive to the basic issues that you are raising and agree it's worth looking at our alternatives.

Thanks again.

Brian

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 16:53:25 GMT

On offline: I think just integrating the online command that is in one of the power toys right now into the UI would be enough for Orcas. And maybe make the dialog (actually, it is two right now, at least one too many) that pops up when you open a project offline that is under source control look a bit less like "something went wrong" into more of an info.

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 17:01:26 GMT

This one is an idea for Orcas (maybe): Cut the need of the client to communicate with the admin site of WSS, instead have the client only communicate with the TFS web service and then have the app tier create the WSS site via the WSS admin web service. Once again one port less that needs to be opened in the firewall :) One barrier less for adoption in organisations where the firewall is under control of one group and the need for TFS in another.

Also, if you look at the errors that people have with TFS setup, a LOT of those happen when the client can't communicate with the WSS admin web service. I am sure things would be a lot more robust if that communication would happen between the TFS app tier and the WSS admin site.

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 17:05:48 GMT

And finally (well, maybe finally) on build. Right now builds can only be dropped at UNC locations (i.e. something like \\server\share). Such droped builds can then not be accessed by clients outside the internal network. This should somehow be changed so that one can configure things such that clients get a WebDAV address to download the builds. Maybe one could configure two address for drop locations: One \\server\share for the build server to transfer the finished build and one http://server/builds/whatever to a WebDAV share that is used by clients

re: Team Foundation Server Roadmap

bharry — Sat, 02 Dec 2006 17:34:22 GMT

WSS admin site - We are making some changes to the way we interact with WSS in Orcas (although I don't know enough details - I'll have to check). Changing the server to create the WSS site is out of scope though because it would require pretty major surgery to the Project Creation Wizard.

That said, one of the things we are trying to get done for Orcas is to separate the the PCW from the VS Shell and enable an object model level API for creating projects. We get a lot of requests from people who want to write web UIs or other tools for creating projects. This would enable that and as a side effect eliminate the dependence on people creating web sites from the client.

Build - couldn't you set it up so that the build server used a UNC share but you enable FTP or WebDav for that location. The link in the build report wouldn't be quite right - you'd have to know how to translate it but I'm having a hard time seeing how us doing something here is much better than what you can already do.

Brian

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 18:02:54 GMT

Yes, the build thing is only about the link in the build report. It is quite cumbersome if you have to translate that every time you want to look at any of the build results, isn't? It is really just a small thing, i.e. the ability to somehow change the configuration such that in the build report there are only links to WebDAV (or FTP) locations instead of the UNC paths.

re: Team Foundation Server Roadmap

davidacoder — Sat, 02 Dec 2006 18:05:25 GMT

Oh, and with that long list of mine, let me also say that I am very, very happy with the decisions you outlined in the post! I think the decision to align with the Orcas ship schedule is just the right one and I in particular think it is great that you try to achieve compatability between the v1 and Orcas release. Just the right call in both cases!

re: Team Foundation Server Roadmap

bharry — Sat, 02 Dec 2006 18:19:19 GMT

Build - OK, I hear you. We'll look at it and see if there is anything we can do.

I'm glad you are happy with those decisions. In a few months I'm probably going to start talking about some of the very early foundational decisions for the version after Orcas and compatibility is going to be a really interesting discussion because of the degree of architectural improvements we are making.

Brian

re: Team Foundation Server Roadmap

bharry — Sat, 02 Dec 2006 18:24:09 GMT

"What's missing for me is the ability to do operations & administration on a project level."

Yes, that's good feedback and we hear it fairly often - either from bigger shops or from shops that have been using TFS for a while.

We are working on step one to address that now. I'm hoping we will get a spec up on our site to lay out some thinking on this in the next couple of months. I think we are going to release an out of band solution initially and then roll it into the release after Orcas.

Brian

Team Foundation Server Roadmap

Brian Keller: Technical Evangelist for Team System — Sun, 03 Dec 2006 00:32:28 GMT

Brian Harry published a must-read roadmap which should give you a good idea of what's coming in future

re: Team Foundation Server Roadmap

G.T. — Sun, 03 Dec 2006 02:12:52 GMT

Al what I’ve seen here is nice, I live TFS, the old source safe was terrible, but I can’t see anything about handling large projects on the server side in the new release.

I see in the replays people demanding meaningless things, or things with very low value to the real world large projects.

We have a solution with tons of projects with tons of code, everything is C#, there are many developers on the project, and each one of them has a copy of the code on his machine, all the code!

It takes time to compile, it takes time to debug, it takes time to refactor and update, VS.net 2005 was not designed to handle large projects, there is no easy way to share development settings between multiple developers, there is mo easy way to share precompiled dlls between the developers, etc, etc, etc.

I know that I can split the project into independent projects, but then I will gain some benefits in the performance, and I will make things like moving a class from project a to project b a project by itself, instead of a simple drag and drop.

Someone at Microsoft in the server department must take care of this, if you don’t provide anything on the server side that takes the care of that you will end up using TFS and VS.NET for small projects.

For example, what should every developer recompile every dll when he/she gets the latest version; you are asking every machine to do the same thing over and over and over.

I don’t know how it will be fixed, but people, the server must help VS.NET too, it is a team server, it must support the developer coding too, not just the business side of thing.

re: Team Foundation Server Roadmap

bharry — Sun, 03 Dec 2006 16:23:14 GMT

I agree with you that VS is not optimized for extremely large projects. As you might expect we also have some extremely large projects. Internally we've developed some techniques for managing this - including ways of sharing settings across all of the projects/developers while also providing ways for per developer customization.

You raise some issues which we haven't dealt with yet - like sharing compilation results (although we've talked a bit about the problem).

The truth is that really big individual projects hasn't been a top priority for us as it's not something we here lots of customers asking for. My current thinking is that we'll try to take some of our internal stuff and get it into the release after Orcas and that additional stuff will come later.

I'm certainly interested in feedback on how important this is to people.

Brian

re: Team Foundation Server Roadmap

davidacoder — Sun, 03 Dec 2006 19:13:00 GMT

By the way, could you elaborate a bit more on the planned integration between Sharepoint document libraries and TFS source control? I have a bit of a hard time imagining anyhtinb by that... Aren't these just two completly seperated stores for files?

re: Team Foundation Server Roadmap

Brian Harry — Sun, 03 Dec 2006 19:30:27 GMT

Yes, they are separate stores. What we are looking at in the short term is building a solution based on the migration tool kit we are working on. This would be a bi-directional mirror that would replicate all document changes between TFS and Sharepoint document libraries in both directions. It's not something we are committed to yet but we are experimenting with it to see how well it will work.

Brian

re: Team Foundation Server Roadmap

davidacoder — Sun, 03 Dec 2006 21:22:56 GMT

Ah, thanks. It would be quite ironic to have web access to the source code depot before we got web access to work items :)

Also, I imagine interesting problems when you look at the different ideas of versioning in the two systems. Sharepoint does have versioning based on a major/minor versioning scheme which I would be surprised could be mappend easily to TFS... Other way around at first looks equally daunting. But even if it isn't 100%, it would be nice to be able to put Word files into source code and access them via Sharepoint, thus not even letting those non-dev people that might work with those know about TFS.

Submit Your Questions for the Upcoming Channel 9 Interviews of the Team Foundation Server Team

Brian Keller: Technical Evangelist for Team System — Mon, 04 Dec 2006 08:57:50 GMT

On Dec. 14 & 15 I will be filming more Visual Studio Team System Channel 9 interviews on-site with

re: Team Foundation Server Roadmap

davidacoder — Mon, 04 Dec 2006 12:52:42 GMT

Ah, and another one: What about Powershell support? It seems both the admin as well as the dev scenario could be quite cool with Powershell commandlets.

Submit questions for the Channel 9 interviews of the NC TFS team

Buck Hodges — Mon, 04 Dec 2006 16:16:52 GMT

Brian Keller , technical evangelist for VSTS, is coming to the North Carolina office to interview Brian

re: Team Foundation Server Roadmap

MJones — Mon, 04 Dec 2006 16:25:26 GMT

Relatively speaking there is going to be less in the Orcas release than was originally expected. This pushes a lot of the functionality that we would like to see post Orcas. Based on my understanding, this pushes things like a requirement accountability matrix out until next year at least.

We've been trying to get off the Rational toolset, but there's still alot that it does better than TFS. The ability to track a line in a requirments document that maps to a series of work items and finally to a test case with results is a big deal for us.

Is a GUI test tool in the post Orcas release scope?

What about the ability to use Source Control without creating a TFS project?

[DNIC] Coder's Corner #1 (December 4, 2006)

Canadian Developers — Mon, 04 Dec 2006 18:07:25 GMT

News & Highlights 2007 Microsoft Office System - Top Ten List of Resources for Developers and Architects

re: Team Foundation Server Roadmap

Burton — Mon, 04 Dec 2006 20:40:13 GMT

i second what Jamie (very first poster) said. Whenever I brief someone on TFS, somewhere in my shpeal is a comment to the effect of "and this is only version 1!"

Good Job guys!

[TFS] Team Foundation Server Roadmap

Visual Studio Team System Blog : VSTS — Mon, 04 Dec 2006 21:50:12 GMT

[TFS] Team Foundation Server Roadmap

Visual Studio Team System Blog : VSTS — Mon, 04 Dec 2006 21:50:43 GMT

VSTS Roadmap

Lazy Coder — Tue, 05 Dec 2006 00:19:51 GMT

This is the roadmap for Visual Studio Team Server.I got my first impression of VSTS today and I think...

re: Team Foundation Server Roadmap

G.T. — Tue, 05 Dec 2006 03:36:49 GMT

Thank you for the response about the large projects, I know that there is limited number of customers with large projects, and one of them is the financial sector, most of the multi million projects we have are in java, and a small amount of them are in .net, but in the past 3 years we are struggling with the performance of VS.NET, I know it is not a lot of customers with large projects, but if Microsoft really wants to have .net in the banking sector, it must handle large projects :-)

It is maybe 10 or 20 developers / project that are building the software, but there are 50,000 PC’s that are running it, and Java can simply run on Linux you know :-)

re: Team Foundation Server Roadmap

DaveS — Tue, 05 Dec 2006 05:30:31 GMT

Very good info - interesting to see others comments on how they are using TFS - have any thoughts been made on improving the project server integration with TFS? While I know Project Server is targeted to projects beyond software development, but better integration with project server would be big for us (and others I'm sure). I hope the Sharepoint 2007 support will include Office Sharepoint Services?!

Dave

Why you should upgrade TFS V1 to WSS 3.0

Mike's Blog — Tue, 05 Dec 2006 11:01:19 GMT

Before you read this post I must warn you, this solution is as is. I'm trained professional so don't

re: Team Foundation Server Roadmap

bharry — Tue, 05 Dec 2006 16:04:03 GMT

MJones - I'm sorry we're not delivering what you had hoped for in Orcas. It sounds like you are looking for enhanced tracability and dependency management. You can do it some now with the relationships that we have and reporting allows you to view the information but we can make it a lot better. That's coming but you're right it's not in Orcas.

GUI testing is something we are looking at but as it's not my product unit I don't feel like I'm in a position to say too much about it.

We haven't done anything to address version control without a team project. I'm still struggling to understand why this is important to people (don't get me wrong - you're not the only one to ask for it). Worst case, you end up with a Sharepoint site you don't use and some reports you don't use. What is the compelling reason to elimiate the other Team Project artifacts?

Lazy Coder - That's a strong statement. I'd be very interested in more specifics as to why you feel that way - what do you feel is lacking?

Large Projects - I hear you. Again, it's not that we don't handle large projects - we handle projects with hundreds of thousands or millions of files. It's an issue of what practices you have to use. We can make it better though. I'll forward your comments to the IDE team and see what they have to say about their part of the problem.

Project Server integration - It's something we very much want to do. We recently worked with Avenade to put out an update Project Server integration tool kit. I am expecting that we will be providing an "out of the box" solution at some point in the future but I don't have a timeframe just yet.

Mike - I made some comments on your blog about this.

Thanks for all of the feedback. I'm always interested - good and bad. The good feels great and the bad is something I can work on fixing.

Brian

re: Team Foundation Server Roadmap

MJones — Tue, 05 Dec 2006 16:52:27 GMT

Brian,

There simply are times where you wish to have a version control project without the need of a sharepoint site or any of the other overhead of creating a TFS project. We don't believe in creating unused Sharepoint bloat. It's simply sloppy.

A prime example are DBA scripts. We have a project in Source Safe where DBAs keep scripts and other code snippets. We would like to consolidate all version control to one system. There really is no reason to create a TFS project for something like this as nothing here is really tracked for managment purposes in a way that would really require a Sharepoint site. To create a sharepoint site just so we can create this project in version control just seems pointless.

Quer saber mais sobre o time do Team Foundation Server?

Igor "T-Shooter" Abade Leite — Tue, 05 Dec 2006 20:34:46 GMT

Brian Keller, Technical Evangelist do Team System, vai fazer uma entrevista para o Channel 9 com o time...

re: Team Foundation Server Roadmap

GertCh — Wed, 06 Dec 2006 01:38:57 GMT

Hi Brian, the roadmap looks great, the Operations tools is promising, we are having, erhhh, 'challenges' in trying to handover TFS to our Operations guys, so that they can put it into Production, so anything that can help our Operations guys with TFS is greatly appreciated

Are there any plans for a server side way to get a WorkItemStore object a la the BuildStore object?

Cheers,

GertCh

re: Team Foundation Server Roadmap

bharry — Wed, 06 Dec 2006 02:05:13 GMT

MJones - Let me digest that a bit and we'll see what we can come up with.

Gertch - Yeah, we know management is an area for improvement. We are making some great progress in Orcas and it will also be an area of focus for the release after Orcas.

I'm not sure about your question on the server side WorkItemStore object. You can (and we do) use our client OM (and the WorkItemStore object) on the server.

Brian

Visual Studio Team System Resources (VSTS)

Sean McBreen's WebLog — Wed, 06 Dec 2006 06:27:06 GMT

I'm very proud of Visual Studio Team System and what Microsoft have done here - I've blogged about it

re: Team Foundation Server Roadmap

Murali Medisetti — Wed, 06 Dec 2006 07:51:43 GMT

Can you include sorting capabilities on Work Item ID when checking-in the file with Work Item Policy enabled.

Team Foundation Server Roadmap

Willy-Peter Schaub — Wed, 06 Dec 2006 13:39:24 GMT

Explore the TFS Roadmap as outlined by Brian Harry's in http://blogs.msdn.com/bharry/archive/2006/11/30/team-foundation-server-roadmap.aspx

Team Foundation Server Roadmap

B³: Beto Borbolla Blog — Wed, 06 Dec 2006 15:28:15 GMT

Brian Harry publicó el Roadmap de Team Foundation Server, muy interesante ya que nos permite hacia donde...

re: Team Foundation Server Roadmap

bharry — Wed, 06 Dec 2006 23:06:44 GMT

G.T. - I forwarded on our thread about large projects to a few people. I'm pleased to say that the PUM of the C++ team was very passionate about it and relayed to me quite of few efforts they have going on with other VS teams (including VB & C#) to improve the handling of large projects. I don't know when it will all come to fruition but it sounds like there's some good activity going on.

Brian

re: Team Foundation Server Roadmap

bharry — Wed, 06 Dec 2006 23:14:14 GMT

Murali - We'll make note of your suggestion. In the mean time, there are a couple of things that might help you. We sort the work items in that list according to the sort order defined in the query. If you don't like the sort order, you can use the Team Explorer window to open the query, then change the sort order and save the query.

Further, if you are looking for a specific work item id, you can type it into the search box in that tool window and hit the search button and it will locate that work item.

Brian

re: Team Foundation Server Roadmap

Paul Verrone — Wed, 06 Dec 2006 23:45:36 GMT

One of the things I was a bit shocked at when evaluating foundation server was the lack of any out of the box rollup for projects at the different management levels.

It hasn't dissuaded us from beginning to adopt it, and I realize we can fairly easily create our own sharepoint portal dashboards for our managers and execs, but since one of your major points is ease of adoption, executive dashboard portals would have gone a long way towards that.

We're mving ahead and we will be creating our own dashboards, but it is slowing down our adoption process. For us specifically, we're moving to a much more structured SDLC process along with Team Foundation Server, so it's not like we have portals to just port over. I'm also surprised to see sharepoint vendors like CorasWorks haven't jumped into this space to offer a packaged solution yet.

The other thing I would like to see is improvements in the code analysis rules engine (FxCop) to make it easier to add our own custom rules and to choose which rules will be enforced across projects as part of the process methodology templates.

Good work on the base product, though! Looking forward to future versions.

Technology Readiness - 200612 Summary

Willy-Peter Schaub — Thu, 07 Dec 2006 09:24:12 GMT

Team Foundation Server We published the new build poster … see http://dotnet.org.za/willy/archive/2006/12/04/New-Team-Foundation-Build-Server-Quick-Reference-Poster.aspx

Team Foundation Server (TFS) Roadmap

TheSaib .NET blog — Thu, 07 Dec 2006 13:48:06 GMT

La RoadMap de Team Foundation Server dévoilé il y a quelques jours par Brian Harry : On y sous entend

re: Team Foundation Server Roadmap

G.T — Thu, 07 Dec 2006 15:21:27 GMT

Hi Brian, thank you the answer, that is good news, as long as it will be solved, waiting a bit is not a problem :-)

re: Team Foundation Server Roadmap

bharry — Mon, 11 Dec 2006 17:44:01 GMT

Paul,

We are working on plans for out of the box rollup reports. I was discussing your feedback with someone on my team and he'd like to get more details from you. Could you send mail to sbhatia@microsoft.com to exchange more thoughts on this topic?

Brian

Using TFS for CI: Gotchas

Dave Donaldson's Blog — Mon, 11 Dec 2006 20:44:06 GMT

Using TFS for CI: Gotchas

Brian Harry's TFS Roadmap

marcus's Team System motivation and experience — Wed, 13 Dec 2006 18:22:24 GMT

As many customer questions always tend around the roadmap topic, I wanted to be sure, that everyone has

re: Team Foundation Server Roadmap

Dilip M — Wed, 13 Dec 2006 21:00:40 GMT

we have had issues working with the tf command line utility across untrusted domains. There is no option to supply the required credentials. The posted workarounds like first authenticating with VS2005 do not work for me.

Nice to have some ideas of the features potentially included with Orcas...thanks for sharing.

re: Team Foundation Server Roadmap

bharry — Thu, 14 Dec 2006 16:05:24 GMT

Have you tried the /login:username[,password] option?

I'm not sure why it wouldn't be picking up your cached credentials.

Brian

Where TFS is heading

The Wonderful World of TFS Version Control, by KWelton — Thu, 14 Dec 2006 17:54:16 GMT

Brian Harry recently posted on his blog about the roadmap for TFS. For the next "major" release (Orcas),

The Triumphant Return?

Aaron Hallberg — Thu, 14 Dec 2006 18:26:55 GMT

Wow - it's been a long time. Sorry for the insanely long delay between posts, loyal reader(s). A lot

re: Team Foundation Server Roadmap

Richard Berg — Fri, 15 Dec 2006 05:47:35 GMT

MJones,

You can create a source-control-only Team Project using the CreateTeamProjectFolder() method of the client API. http://msdn2.microsoft.com/en-us/library/microsoft.teamfoundation.versioncontrol.client.versioncontrolserver.createteamprojectfolder(VS.80).aspx

re: Team Foundation Server Roadmap

Dilip M — Fri, 15 Dec 2006 22:58:00 GMT

The /login option worked...that's what I was looking for all along. Thanks much!

re: Team Foundation Server Roadmap

MJones — Mon, 18 Dec 2006 16:53:15 GMT

Richard,

Thanks for the link. Now if we can only get that integrated into the Microsoft tools we'd be set.

If you have any interest in TFS

Ahmed Salijee — Mon, 18 Dec 2006 17:13:35 GMT

Then you need to check out these posts that details the TFS Roadmap. TFS Roadmap by Brian Harry Team

Deployment procedures

Chris Lively — Tue, 19 Dec 2006 03:51:25 GMT

One area that I think you guys are really missing on is controlling project deployment.

What use are the Distributed System Designers if I can't give it the machine names and say "Go Forth and Install It!" After all, if it knows what software is necessary and where it is then it should be able to push the install similiar to WSUS.

Also, please spend some time integrating this stuff with your existing product line. You have no idea how difficult it makes things when we use Biztalk and the VS2005 deployment designers have no clue what that is.

re: Team Foundation Server Roadmap

bharry — Tue, 19 Dec 2006 14:17:24 GMT

You won't get any argument from me on deployment. I agree that it would be a really valuable feature. There's a team at MS that is looking at tackling this problem and we plan to integrate TFS with it when it is available. In the mean time we've been batting around some ideas for tactical approaches. Nothing concrete at this point but it's definitely something we care about.

I have to be honest and say that I've never really looked at Biztalk and VS2005 together. I'll keep my ears open and see if anyone is looking into that.

Brian

Team System RoadMap

Deep Dive In .NET — Thu, 28 Dec 2006 12:53:01 GMT

Team System RoadMap

Pedro Rosa — Thu, 28 Dec 2006 15:19:12 GMT

Team System RoadMap

Talking About Microsoft Developer Tecnologies — Thu, 28 Dec 2006 15:19:12 GMT

Great post about Team system RoadMap http://blogs.msdn.com/bharry/archive/2006/11/30/team-foundation-server-roadmap.asp

Orcas Workspace Mapping Improvements

Team Foundation - Version Control Server Team — Fri, 29 Dec 2006 00:25:42 GMT

I thought I would give you an overview of the workspace mapping improvements which Brian Harry mentioned

Orcas Team Build Continuous Integration spec is now available

Buck Hodges — Sun, 07 Jan 2007 05:09:09 GMT

Back in early December, I wrote the post, More on the Orcas features for Team Build , that described

TFS Version Control Server Team blog is alive

Buck Hodges — Wed, 10 Jan 2007 07:32:08 GMT

Chandru, a developer on the TFS version control server, has written the first post on the Version Control

re: Team Foundation Server Roadmap

Darren T — Wed, 10 Jan 2007 19:03:20 GMT

I'm very interested in you mentioning a "Checkin policy pack". In particular I'm confused as to why you can't set a checkin policy on a subfolder (at a branch level) within a project. For my case (and many others that I have read on various forums), I'd like a checkin policy for my main branch, and a different, or even no policy, for my work branches.

When a user checks some code into the main branch, through a merge from their work branch, I want to force them to associate that work with a work item and supply the name of the person who code reviewed the merge. However, while their working on their own branch, there's no need for them to create a work item for each checkin. This will discourage regular checkins, which is our current policy.

Is this possible with a bug fix or future SP?

re: Team Foundation Server Roadmap

bharry — Thu, 11 Jan 2007 17:17:46 GMT

We're working on getting the checkin policy pack wrapped up now. I agree whole heartedly that we need to be able to scope different policies to different branches. The policy pack will include support for that and I expect that a future release will provide it in a more elegant way.

Brian

По дороге к “Orcas”

Константин Косинский — Fri, 12 Jan 2007 14:10:27 GMT

У меня сложилось такое чувство, что разработчики новой студии работали даже в новогоднюю ночь, или, проснувшись

re: Team Foundation Server Roadmap

Murali — Sat, 13 Jan 2007 21:15:08 GMT

Posting this comment when I am looking around out of frustration when my TFS server gave up partially over the weekend. Checkins and checkouts hang both from commandline and from VS. My hands are tied now, and I feel that I do not have any productivity over this weekend. I would suggest to put in some solution around this - such as batch my basic source control ops (like checkout to start with) locally and make 'em online when server connects...

I relaly do not want to take chances by over-writing files on my own.

re: Team Foundation Server Roadmap

bharry — Sun, 14 Jan 2007 16:16:29 GMT

I'm sorry to hear you had a problem. We are working on better offline support in future versions. However, you should not feel concerned about changing your local files - I do it all of the time when I am offline. TFS remembers what versions of files you had and you can retroactively check out the proper file versions when you get back online. The hard part is remembering what files you modified. To help with this, there is a "tfpt online" command in the Team Foundation Power Toys. You can read more about them here: http://blogs.msdn.com/bharry/archive/2006/09/07/744993.aspx

Brian

re: Team Foundation Server Roadmap

Antony Clark — Wed, 17 Jan 2007 19:04:39 GMT

Is the issue of restricted access Sharepoint Document Libraries causing a Red X in team explorer Documents node, (effectively removing access to all doc libs from Team explorer), fixed for orcas?

See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1020079&SiteID=1

Thanks

re: Team Foundation Server Roadmap

Tony Fabian — Wed, 17 Jan 2007 23:42:04 GMT

Do you have any plans do include deployment- test of asp.net Web Applications?

We are using TFS for the development of MCMS 2002 and MOSS based solutions and a mission critical task is to very that the solution can be deployed.

A nice scenario to support would be if a build is completed successfully the TFS will compile the msi installer associated with the solution (or wsp file for MOSS based solutions) and execute/install that on a test server(s).

When the package has been installed an event gets fired that allows me to start a web test to verify that the deployment was successfully.

/tony

PS: Thank you for a really really great piece of software that has made my life a lot easier!!

re: Team Foundation Server Roadmap

bharry — Sun, 21 Jan 2007 03:46:13 GMT

Yes, the issue with lack of access to one doc library preventing access to all of them is fixed in Orcas. In fact we are working a hotfix through the pipeline for TFS2005.

Today you can implement what you describe yourself using WIX installer authoring and custom MSBuild tasks. However, we recognize this is a lot of work for a common scenario. It is a scenario we are looking to make much easier in future versions.

Brian

re: Team Foundation Server Roadmap

David A — Thu, 25 Jan 2007 23:41:52 GMT

As a non-developer who is charged with supporting and administering TFS at a number of clients, I have one thought. The process to move/migrate TFS is, frankly, awful. There are just too many moving parts to feel confident about doing a TFS move, especially for paying clients. Please, please consider a backup/restore Power Tool that gets EVERYTHING required for TFS to function, including SQL, Reporting Services, and Sharepoint (don't get me started on Sharepoint).

Since most TFS installations begin on some ratty workstation under a developer's desk as a trial, it would seem to me that migration and move scenarios (cross-domain, especially!!) would be relatively common. Simplifying this process would be a god-send.

I do like what you've said regarding the use of non-standard ports, and the use of accounts like NetworkService...please keep moving toward a more configurable and flexible setup.

Gracias,

re: Team Foundation Server Roadmap

bharry — Fri, 26 Jan 2007 00:08:38 GMT

Thanks for the feedback. I think you've got a really good point. There are alot of parts and it is hard to get this kind of thing right.

Brian

Team Foundation Server - hva skjer videre fremover

Geir Morten Allum's MS application platform hvor, hva, når, hvorfor, osv... — Fri, 26 Jan 2007 18:15:13 GMT

I og for seg ikke noen nyhet dette da det har ligget ute en stund, men har i det siste fått en del spørsmål

re: Team Foundation Server Roadmap

Darren T — Tue, 30 Jan 2007 12:43:57 GMT

Not stricly related to the roadmap, but I have a problem. After creating a new project, which creates a sharepoint site, there's no "quick launch bar" shown on the left hand side. So everytime I create a new document folder and I'm asked if I want to show it on the quick launch bar, which I do, I can't. Is there a setting to show the quick launch bar?

re: Team Foundation Server Roadmap

bharry — Wed, 31 Jan 2007 15:37:13 GMT

Here's and answer I got back from our Sharepoint portal Program Manager:

Sounds like he needs to tweak his sharepoint site template.

http://office.microsoft.com/en-us/frontpage/HP010971461033.aspx

More help here: http://www.microsoft.com/technet/community/newsgroups/server/sharepoint.mspx

re: Team Foundation Server Roadmap

Paul — Thu, 01 Feb 2007 06:13:49 GMT

Brian,

Thanks for the terrific main post and answers.

I echo all of the other comments calling for deep integration with SharePoint 3.0, InfoPath and Project Server; and multi-project management and reporting, among other things.

Here's my unique contribution (some might say bizarre):

I'd like very much to be able to create team projects that span multiple geographic locations in a single enterprise (across the Internet) and even multiple enterprises, with all the snycing (SQL Server replication or whatever) taking place in the background automatically.

And another weird idea (more like a fantasy): consider licensing the VS IDE and TFS to 3rd party developers who want to build team process ecosystems for projects other than software development.

There, I said it.

re: Team Foundation Server Roadmap

Paul — Thu, 01 Feb 2007 06:21:20 GMT

...(clarifying my "fantasy" comment above:

When I suggest that Microsoft "consider licensing the VS IDE and TFS to 3rd party developers who want to build team process ecosystems for projects other than software development," of course I mean without all the software development tools ("packages" in VS and "services" in TFS) that pertain specifically to software development.

I mean specifically that you include the VS IDE and TFS core services, reporting, etc and corresponding client objects, but not build or even, perhaps, version control.

Yeah, I know this idea probably sounds crazy to most members of your group, but take it up the line if you can. I strongly believe that other vertical industries besides sofware development (I can think of one such industry in my own case...) would like to develop deeply extensible, integrated platforms for hosting their own types of processess and tools.

ALM using VSTS / TFS - More links than you shake a stick at !

The Liquidator — Thu, 01 Feb 2007 09:01:37 GMT

Configuration and Management of Team Foundation Server http://msdn.microsoft.com/vstudio/teamsystem/team/quickstarts/configure/default.aspx

re: Team Foundation Server Roadmap

Gian Piero Anselmi — Thu, 01 Feb 2007 22:25:30 GMT

You are doing a wonderfull job. Please consider a backup/restore tool for a single project that allows to move one (or more)project on different TFS servers.

re: Team Foundation Server Roadmap

bharry — Fri, 02 Feb 2007 01:51:24 GMT

Yep, we've got such a tool (project backup/restore) in the works. It's no small job so I'm expecting it to take several months but it's on the way.

Brian

re: Team Foundation Server Roadmap

bharry — Fri, 02 Feb 2007 15:22:26 GMT

Paul, a couple of comments on your suggestions...

Distributed team projects - we are committed to making distributed team successful - particularly as this is becoming an increasingly common practice. Today, our solution to this problem is to provide a Team Foundation Server proxy that can be installed at remote locations and cache data to substantially improve remote performance. We continue to look at ways to increase the amount of data cached and deal with connectivity issues. We've shied away so far from a genuine multi-master replication solution. Some of our competitors have them and customer satisfaction with them is generally very low. They are extremely hard to configure and to manage. A proxy solution is much simpler and more robust.

Non development projects - Interesting thought. You're right that today we focus on software projects. There's nothing that prevents you from using TFS for anything else. In fact, we provide Team Explorer as a separate interface from VS to enable this kind of scenario. We generally think of it as being for the "non-developer" participants in software development projects but it can be used in any context. I agree that the build functionality is out of place in non-software projects and there's really not any way to "hide" it. I'll think about that scenario a bit more.

In addition to Team Explorer, VS has a SKU called Premier Partner Edition (or PPE for short) which actually is the VS shell without all of the development tools in it and can be used for other applications. In fact, Team Exploer is built on it. So is SQL Management Studio and quite a few third party solutions.

Thanks for the feedback - it's definitely thought provoking.

Brian

re: Team Foundation Server Roadmap

Brandon — Sat, 03 Feb 2007 09:57:35 GMT

Brian, First I would like to say kudos to your team for a great v1 product. It has helped us to have more structure and control over our development and build process over Visual Source Safe which is the product we used to use.

Two scenarios that come to mind that would real1ly help out my development team would be:

1. Provide an inexpensive license that would allow customers to access the work item data and reports so that they could check up on the progress of a submitted bug or feature request. We develop software that is used by 100s of on-site users (internal product). Right now they submit an email to a developer who then enters the work item in for them and then the requestor must rely on verbal communication or if he's lucky an email notifying him if the bug has been fixed. Since this support doesn't currently exist we're looking at adding a new contact or customer field to the various work items and events that will trigger an email to be sent to the customer when a project item's state changes. Out of the box support for this would be awesome including a license that would allow end users to submit bugs directly to the work item database.

2. The automated build seems very restrictive for what type of tests it allows. For example, our application has a built-in VBA object model similar to VS or the Office products. We would like to be able to write automated tests against this object model to excersise functionality. Of course, this requires the UI. Unfortunately, in VSTS current state Team build will not run the tests correctly due to the fact that it runs in a service so all UI and events do not occur properly in that instance. I'm not asking necessarily for support for UI testing but I'm asking for the ability to run automated tests that require a GUI or a GUI appliction to be present while the unit tests run. Thanks again for a great product. I look forward to hearing your response.

Brandon

re: Team Foundation Server Roadmap

Paul — Sat, 03 Feb 2007 19:12:25 GMT

Brian,

Thanks for your response regarding my crazy proposal to use the VS IDE and some "generic" version of TFS for non-development projects. In fact, my company just spent several months considering exactly what you proposed, namely, hosting our front end tools inside of Premier Partner Edition and building our own services/dbs/object model on top of TFS for linking, event sharing, etc.

I think it would have worked technically, but in the end, we decided not go go ahead because of business reasons. Specifically, we realized that it would not be possible to convince our (100 pretty big) clients to spend about $2k/user on TFS CALs to a product designed for software development -- when they're not in the business of software development at all.

Of course, a stripped down version of TFS that doesn't include build and all the other specifically software-focused functionality shouldn't be selling for the same price as the full product anyway.

If MS were to lower the price on such a product and market it in such a way that ISVs like me can sell it to a wider client base, I think, everyone could come out a winner.

re: Team Foundation Server Roadmap

buckh — Sat, 03 Feb 2007 19:16:56 GMT

Brandon, we just recently changed the build service in Orcas so that it can be run either as a Windows service, as in v1, or on a desktop command line, providing access to the Windows desktop. You also have the option of running it both ways on the same machine, where the Windows service uses port 9191 and the interactive service uses port 9192 (both ports can be changed).

I'll be blogging about this and some other recent changes to Team Build in Orcas shortly.

Buck

re: Team Foundation Server Roadmap

bharry — Sat, 03 Feb 2007 19:41:34 GMT

Paul,

How did it add up to $2K per user? TFS CALs are $500 per user list price and substantially less at volume discounts. We also provide a way for ISVs to resell them (providing a discount to the ISVs, with some volume guarantee).

That said, we have gotten feedback that even that price is too high for certain scenarios and we are looking at alternatives for lower price and reduced function. Keep your eyes open for more on that in the future.

Brian

re: Team Foundation Server Roadmap

bharry — Sat, 03 Feb 2007 20:30:29 GMT

Brandon,

We are looking into #1. There's a difficult balance between enabling this and not undercutting the value to developers. We don't have a final proposal but we have some ideas and (I at least) hope we can do something to address this by the time we ship Orcas.

Brian

re: Team Foundation Server Roadmap

Paul — Sat, 03 Feb 2007 21:15:02 GMT

Brian. $2k was going to be the average total cost per user for our product, including the $500/user for each TFS CAL. Sorry I expressed myself incorrectly above. Great product and great blog. Best regards.

What “main” features are coming to us with Orcas?

Willy-Peter Schaub — Sat, 03 Feb 2007 23:33:12 GMT

We are continuously being asked what Orcas has in store for the solution teams, the architect, the developer

re: Team Foundation Server Roadmap

Gabriel Lozano-Moran — Mon, 05 Feb 2007 18:54:30 GMT

Hello Brian

If there is going to be support in TFS for SharePoint Server 2007 does this implicitly state that WSS 3.0 will be supported as well? How abount licensing when using SharePoint Server 2007? I mean does TFS come with a license for the SharePoint Server 2007 Standard Edition and will we need seperate CAL's for SPS 2007?

Cheers

re: Team Foundation Server Roadmap

Brandon — Mon, 05 Feb 2007 23:51:35 GMT

Brian, Thanks for your response. I have another request that would improve branching and merging and that would be to have better visibility into the work items and changesets that a branch includes when it is merged from another branch. Right now when you merge 2 branches, you check in a new changeset with all of the merged changes. It seems to me it would be better if there was a way to have visibility into those changes when they get merged. Any thoughts or features to handle this better on the horizon?

re: Team Foundation Server Roadmap

bharry — Tue, 06 Feb 2007 05:12:06 GMT

Gabriel - WSS 3.0 is SharePoint 2007. Yes, we will support it in our Orcas release. We are looking at how to support it in limited ways before then. TFS does not come with a SharePoint license. I believe the SharePoint license comes with Windows Server. If you use SharePoint Portal Server, then you need separate CALs for that.

Brandon - Yes, this is something we are looking at for a future version. Actually the V1 server didn't have the support to enable this. We added it to SP1 so that third parties could build UI around it in the short term. We will enable it in our UI down the road.

Brian

re: Team Foundation Server Roadmap

Gabriel Lozano-Moran — Wed, 07 Feb 2007 12:34:37 GMT

I didn't know that SPS 2007 was also based on WSS thanks for enlighten me :-)

I have another, important question. According to the TFS installation guide, the installation of the business tier on a 64-bit version of the Windows Server 2003 platform is not supported. When can we expect this support?

re: Team Foundation Server Roadmap

bharry — Wed, 07 Feb 2007 15:50:22 GMT

I wish I could say the answer was "soon" but it is not :(. For now, we are recommending people to either run a 32 bit OS or to run a 32 bit virtual server on their 64-bit server. This is the way I have my TFS at home configured and it works pretty well :)

Brian

re: Team Foundation Server Roadmap

Gabriel Lozano-Moran — Wed, 07 Feb 2007 17:53:06 GMT

I am asking this because for TFS deployments companies order new servers and on these servers nowadays they come by default with 64-bit Windows Server 2003.

re: Team Foundation Server Roadmap

Darren T — Wed, 14 Feb 2007 12:02:34 GMT

Is there going to be a "Changsets" view? Currently to see any previous check-ins, you have to do so as part of another operation. e.g. do a get latest on a specific version, then click the elipsis to get the "Find Changesets" dialog. Often, it's useful to just browse a list of all changesets. I imagine this'd be an easy addition (famous last words), as the dialog is already there. We just need a menu item?

re: Team Foundation Server Roadmap

bharry — Wed, 14 Feb 2007 14:05:06 GMT

There are a couple of way to do this. First, the history window gives you a change sets view. You can use the History menu option either from the Source Control Explorer or the Solution Explorer and it will give you a scoped list of change sets.

Secondly, you can use "Find change sets" by selecting Edit->Go to while in the Source Control Explorer.

Brian

re: Team Foundation Server Roadmap

cbenmichael — Wed, 14 Feb 2007 17:34:46 GMT

The "install on a domain controller" feature is important, especially to small companies (like mine) looking at the workgroup version. The only 2 servers we have that i would trust to install a source control app are both domain controllers.

Short of waiting for Orcas, is there a work-around today for installing TFS workgroup on a domain controller?

-cbenmichael

p.s. I hope the workgroup version will still be around in orcas.

re: Team Foundation Server Roadmap

bharry — Wed, 14 Feb 2007 18:14:52 GMT

There's really not anything you can do today to get it to work on a domain controller. Yes, we plan on continuing the workgroup edition or something very close to it in Orcas.

Brian

Team Foundation Server Roadmap

Javier Romero — Thu, 22 Feb 2007 19:47:50 GMT

Brian Harry ha publicado el Roadmap de Team Foundation server en su blog y si quieres conocer qué se

TFS Version Control support in Orcas

Mike's Blog — Sat, 03 Mar 2007 05:29:44 GMT

Who isn't interested in the new features of Orcas. I really am and especially all the features of TFS.

TFS Team Build support in Orcas

Mike's Blog — Sat, 03 Mar 2007 06:22:38 GMT

Who isn't interested in the new features of Orcas. I really am and especially all the features of TFS.

re: Team Foundation Server Roadmap

Niko — Mon, 12 Mar 2007 17:58:38 GMT

Hi all,

Could someone tell me when I will be able to configure the Get latest version on check out, i.e. when the sp2 will be released or first on beta ?

Tkx all

re: Team Foundation Server Roadmap

bharry — Mon, 12 Mar 2007 19:25:50 GMT

Get latest on checkout is in Orcas. It's in the March CTP and will be in Beta 1 in the coming months. It won't be available before Orcas.

I'm going to publish an updated Orcas Roadmap in the next couple of months and then the first draft of a more detailed roadmap for the following release soon after that.

Brian

re: Team Foundation Server Roadmap

Mike — Mon, 12 Mar 2007 23:32:46 GMT

Feature request (or is it already there somehow?).

It would be cool if when you craated a Team Query (or My Query I guess) it showed up on the Sharepoint site as a report.

re: Team Foundation Server Roadmap

bharry — Mon, 12 Mar 2007 23:40:59 GMT

We've done some experimentation on creating reports from queries. We haven't looked at automatically publishing them to the portal. That's an interesting idea. We'll look at it.

Brian

Happy Anniversary TFS!

Jeff Beehler's Blog — Sat, 17 Mar 2007 15:36:07 GMT

It's been exactly 1 year since we released the golden version of Team Foundation Server v1! This post

Team Foundation Server Roadmap information offentliggjort

Martin Pamdeth's blog om Microsofts Application Lifecycle Management værktøjer — Mon, 19 Mar 2007 19:17:10 GMT

Nu har Brian Harry fra Visual Studio Team System teamet publiceret en del information om Team Foundation

re: Team Foundation Server Roadmap

Venky krishnan — Fri, 23 Mar 2007 18:45:44 GMT

One of the big thinsg that is broken is how to do workitem tracking using ms project. All the reference material in msdn seems to refer to beta content. The final release of TFS has a lot more fields that are not readily visible with mucking around with so many of the xml files.

Destroy: A new feature for Orcas

Team Foundation - Version Control Server Team — Tue, 27 Mar 2007 19:10:12 GMT

Brian Harry mentioned the new Destroy feature in his TFS roadmap post. I thought I would go into a little

How about one Team Foundation Server portal? I had a dream!

Mike's Blog — Fri, 30 Mar 2007 08:48:30 GMT

Last night I had a dream about the future of TFS. Wouldn't it be nice if we had one single portal on

re: Team Foundation Server Roadmap

mkurtbas — Mon, 16 Apr 2007 00:14:16 GMT

Thank you!

Mutlu Kurtbas

MCPD : Enterprise Application Developer

http://tfsgunlugu.blogspot.com

re: Team Foundation Server Roadmap

gauravmangla — Wed, 02 May 2007 11:05:41 GMT

Hi Brian,

I was going through your blog earlier where I saw the need for a Backup/Restore ability in TFS as one of the questions by a lot of people just like myself. However - I got my question answered by a suite of products from Kyrosoft @ http://www.kyrosoft.com/products/SourceControlBackup.htm

These guys offer pretty interesting products and services too for migration of various source controls like CVS, SVN to TFS Source control. Check out, http://www.kyrosoft.com/products/SVN-2-TFS.htm

re: Team Foundation Server Roadmap

bharry — Wed, 02 May 2007 13:19:46 GMT

Thank you, that looks very interesting. We'll look into it further.

Brian

MSSCCI and Oracle Toad

Rolf Szomor — Fri, 25 May 2007 12:50:25 GMT

Hi Brian!

I would like to know, when will be the support for Oracle Toad in MSSCCI released.

Thank You!

Rolf

re: Team Foundation Server Roadmap

bharry — Tue, 29 May 2007 14:00:11 GMT

It's been in for a while now. Download the latest MSSCCI provider drop and you will have it.

Brian

re: Team Foundation Server Roadmap

nathan.wells — Tue, 12 Jun 2007 12:25:51 GMT

I just read about Kyrosoft's SVN-2-TFS in the blog. It's a fraud company; I tried to purchase their product and the buggers gave me a crappy product, for an hefty amount which was good for nothing.

Even their website doesn't work today!

re: Team Foundation Server Roadmap

bharry — Wed, 13 Jun 2007 14:45:06 GMT

I appreciate the comment. I've been interested in hearing some customer experiences around their products. When we first learned about them, we contacted them to understand the approach they were taking.

We discovered that they were taking an approach (at least in some of their products) of directly manipulating the database schema. We strongly recommend against this approach as the schema is very complicated and provides to semantic integrity checking. That doesn't mean it can't be made to work and I was hopeful that their products are good. I'm sorry to hear that you had such a bad experience with them.

Are there any other experiences around them?

Brian

re: Team Foundation Server Roadmap

Sanjay Garg — Fri, 15 Jun 2007 14:00:22 GMT

Nathan: I am the owner of kyrosoft and I HAVE NOT sold our product to any one yet as we are a new start up and are in the process of acquiring an export license. Please FURNISH THE PROOF of processing of payment by Kyrosoft. This is very disgusting that you are spreading untrue rumors about a fledgling company. We have received a few orders, but have not processed any order due to us not being authorized to export yet. If any one still has any question's please contact me info@kyrosoft.com.

Team Foundation Server Roadmap

Javier Romero — Mon, 18 Jun 2007 18:21:10 GMT

Team Foundation Server Roadmap

re: Team Foundation Server Roadmap

NathanD — Wed, 15 Aug 2007 09:09:49 GMT

I recently purchased Krysoft's SVN-2-TFS product, and it works as advertised. I used it to move our production source control from SVN to TFS, which consisted of roughly 4000 files and 2500 check-ins.

It has the marks of a new product, with minimal options or configurability, but it handled the task that I most needed -- moving all of the code and check-in comments from SVN to TFS. The few issues that arose were quickly resolved by Krysoft, which was a welcome change considering my experience with numerous other software companies.

I'm not the Nathan who responded above, and I'm not associated with Krysoft in any way other than being a satisfied customer.

NathanD

re: Team Foundation Server Roadmap

bharry — Wed, 15 Aug 2007 14:22:38 GMT

Thank you Nathan. That's really good to hear.

Brian

re: Team Foundation Server Roadmap

Newport Group — Fri, 21 Sep 2007 18:16:05 GMT

We use Team Foundation for version control and team build and are very happy with it. We do not use the work item component because our QA team plans to implement Mercury Quality Center instead. They like QC because of its requirements management features, including the ability auto-generate documentation in Microsoft Word. My #1 request is to enhance the work item tracking piece to be on par with QC in terms of its requirements management abilities.

RoadMap de Team Foundation Server

Oscar Berroteran — Tue, 25 Sep 2007 01:11:03 GMT

Hola.... Desde la semana pasada he estado trabajando en un proyecto de implementación de Team Foundation

RoadMap de Team Foundation Server

Oscar J. Berroterán — Tue, 25 Sep 2007 01:11:09 GMT

Hola.... Desde la semana pasada he estado trabajando en un proyecto de implementaci&#xF3;n de Team

RoadMap de Team Foundation Server

Oscar Berroteran — Tue, 25 Sep 2007 01:11:09 GMT

Hola.... Desde la semana pasada he estado trabajando en un proyecto de implementaci&#xF3;n de Team

re: Team Foundation Server Roadmap

OC — Thu, 25 Oct 2007 16:55:29 GMT

Hello everybody,

Its really interesting to hear about an SVN-TFS migration tool.

But I need a CVS-TFS migration ..

So can I migrate CVS-SVN & then SVN-TFS...

Is that possible

btw thanks for all your comments

Cheers

re: Team Foundation Server Roadmap

bharry — Mon, 29 Oct 2007 23:41:35 GMT

I can't see why that wouldn't work. Also, I believe http://www.componentsoftware.com has a tool to migrate from cvs -> TFS.

Brian

Team Foundation Server Roadmap

Javier-Romero — Wed, 14 Nov 2007 04:13:53 GMT

Team Foundation Server Roadmap

Team Foundation Server Roadmap posted

Bryan Hinton's Blog — Thu, 17 Apr 2008 00:49:51 GMT

This is a little old news now - but I wanted to link to this for those that watch my blog for TFS news