index > Team Foundation Server - General > VSTS and MSDN Academic Alliance

VSTS and MSDN Academic Alliance


After doing some poking, proding and rethinking, we have refined our story with respect to VSTS and MSDN AA.  Recently I posted that VSTS is included in MSDN AA but only by request.

We have decided to put the 180 day trial edition of VSTS on the MSDN AA web site and make it available to all MSDN AA members.  There will still be some TBD process to get registration keys to turn the trial edition into a "full" licensed product but we'll have 6 months to figure that part out now :)

We are investigating putting the Beta 3 Refresh of TFS on the MSDN AA site too.  Once TFS releases, the 180 day trial edition will be available through MSDN AA just like the rest of VSTS.

We hope this plan will work well of our MSDN AA members.

Brian
Brian Harry
Brian, I am really impressed that you follow up on this topic and try to make sure things work out well. Thank you!

I still have one specific and one general point left :)

1) This is just in addition to the already mentioned possibility to get full licenses by personal request, right? Or does this mean that you are rethinking completely whether to include VSTS and TFS in MSDN/AA? If this is just to bridge the time until you have found a way to make the full version available, then great!

2) I think there is a great need to simplify all this. Let me briefly describe my situation. I am a PhD student working on coupled climate/economic computer models. That whole climate research area is heavily geared towards Unix and lately Linux. My group is a bit different and I see a fantastic opportunity to use Team System to increase our productivity and do better research. The whole research community is not particularily strong on process and SCM on one side, and stuff like the DSL tools are just ideal for what we do on the other hand. I would really love to establish a small group here that does research and builds models based on .Net and Team System. But things like individual negotiations with some regional MSDN/AA representatives whether we can have the software (oh, and I wrote the guy for Germany on Friday and haven't gotten any reply so far) just don't look good compared to the tools that the guys on *nix use. They just download SVN and all the other stuff and are done... I feel that MSDN/AA has the charm that the delivery of software to researches is uncomplicated and that researchers don't have to think much about licensing, much like with the alternative open source components. Once you introduce extra negotiations with uncertain results you would spoil much of that benefit and have another barrier to entry into the Team System world. Now, I understand that the situation in the business world is different, but in research (at least the kind of stuff I am involved) there is NO one waiting for MS to make an entry. You guys are trailing behind in that area in a major way. And I believe it would be a better strategy to make it REALLY easy to get your premier tools, and in particular enable things like having a PhD student with some peers use it (who essentially has no money). Once people see how nice this works they might think again whether *nix is really the only possibility for HP research computing.

Sorry for that rant, but I have just spent WAY too much time already trying to figure out a way to get Team System for my group, while all I really want to do is use it ;)

Best,
David

PS: Oh, and one more thing. One can only enter MSDN/AA in January or June. So, it would be really nice if you could sort all of this completely out in time for people to make buying decisions for the January deadline.
David A.
1) It is still included in MSDN AA.  When I last talked to the marketing guy about this yesterday, he said there will be some way to get "official" product keys for a non-time limited version but that they need to work that out.  So I believe it is just a bridge until they have that figured out.

2) I hear your feedback and am committed to making it as easy as possible for students of all kinds to leverage our technology to do great things.  I'll forward your post to the marketing team and continue to work them on it.

I'll let the marketing team comment on timeframes.  I'll suggest they reply to this.

Brian
Brian Harry

Great! Thank you so much for looking into this.

Oh, and one last thought. I really don't think that you guys will loose any significant revenue by including Team System in MSDN/AA. At least the areas I am familiar with would never, ever buy Team System at any of the other prices quoted. For them/us/me it is really just a choice between having it in MSDN/AA or using something entirely different, like SVN and accompaning tools. I would much prefer the first option! Very different market from the corporate world, where you guys seem to have a low price compared to the competition.

At the same time including it in MSDN/AA seems a great opportunity to make many more students/researchers familiar with the MS platform.

Cheers,
David

David A.

 

Bruce Curling
Hi Bruce,

 Bruce Curling wrote:

 

David A.
Have there been any updates on the situation?
zian

Hello Everyone,

My name is Bruce and I would like to give you the real story on what we are going with VSTS and TFS in MSDN AA.  IMPORTANT - PLEASE READ ALL TEXT BELOW CAREFULLY BEFORE SENDING AN EMAIL: 

TFS

1)      The 180 day Trial version of TFS is available to MSDN AA Administrators on the MSDN AA subscriber download site and should be regarded as nothing more than an FPP version of TFS that happens to function prior to the addition of a key.  Additonally, all students are welcome to download the trial of TFS from the public site regardless of their affilaition with MSDN AA. 

2)      We have distributed a TFS key for each MSDN AA member on the MSDN AA subscriber download site.  Each key can be used by all eligible students in the MSDN AA department.  Students and faculty can use TFS in trial format and upgrade to the permanent version by entering a key the key whenever they wish.  The keys required for this upgrade process can only be accessed by MSDN AA Administrators and distributed to eligible students within the MSDN AA Department.  

3)      Existing Trial versions of TFS can be turned into permanent versions with the following process: 1) go to the control panel 2) double click ??dd/Remove Programs??3) double click TFS 4) Enter Key when prompted via the wizard.  

4)      Please bear in mind that we have had quite a bit of success using this process, in other words - It works.

 VSTS

1)      VSTS is different.  The ??rial to Permanent??upgrade process WILL NOT WORK FOR VSTS.     

2)      The commercial bits and license keys are available to MSDN AA Administrators on the MSDN AA subscriber download site.   VSTS Keys and bits can be accessed by MSDN AA Administrators and distributed to eligible students within the MSDN AA Department.  Students within an MSDN AA department will still have access to non-expiring licenses of VSTS.  

 




MSDN AA/Software Access Guy
Bruce Curling
reply 8

You can use google to search for other answers

 

More Articles

Team Foundation Server
Adding users to Team Foundation Server
I really miss the report "Work Items By Owner". How can...
How to use workspace.checkin with workitem, example needed
Team system RC vesrion with Studio 2005 release
how do I change team foundation server configuration
Project file sync for closed tasks
Team Build status not refreshing when executed on remote build se...
Report "Remaining Work" does not show all Work Items
Carriage returns removed when saving a work item
Welcome to Bokebb   New Update   Joins the collection  
 

New Articles

Re: Web Access to Version Control
Programatically Creating WorkItems
CI and Team systems
Permission to make branch
How do I add web site (web project) to s…
build type and permission error
TF82001: MS Project can't connect to Tea…
Source Control Explorer "No Command…
VSSConverter for TFS Beta3
Multiple TFS Projects
TFS backup
How to switch the source control tool fr…
Team Build Ignores Conditional Compilati…
Chage File System Web Site to HTTP Web S…
TF30076 error ....

Hot Articles

TFS Version Control outside MS environme…
System.Web.Services.Protocols.SoapExcept…
COMEXception (0x8007203a): The server is…
Chage File System Web Site to HTTP Web S…
TF GET docs confusing
Source Control Explorer
Team Build: matching assembly version nu…
Can't create team project... then check …
Connection to VSTS from Report Services …
HOWTO delete a work item in UI
Problems with versions of code in Visual…
TFS Crash
Product Studio to VSTS Work Item Migration
Hot spare app tier
How to find "days left" before…

Recommend Articles

Automatic Document Generation from Work …
Can someone try this quick test, please?
Writing (refining) a Build Project - Goo…
MSBuild vs. TFSBuild
Project Management in VSTS
Team Build Desktop Build problems
Can't change WIT field from String ->…
Task gap - From Add Existing Team Projec…
Version Control Events
.runconfig not picked up when excuting t…
Snapin VersionControl.Common.Integration…
How to assign state transition to certai…
Work Item field with multiple dependencies
related work items- hierarchy
Creating project bombs due to lack of ad…