MSDN Universal subscription changes (level and pricing)

[Guest]

:

I do appreciate the help that the MVP's provide for programming issues in
these newsgroups. I consider this issue to be a "programming" issue as
well. VSTS can make us better programmers and promote MS at the same time.
It's win-win to include it (single developer version) in Universal. It's
lose-lose to not include it. It's that simple.

I agree, it is that simple! I won't be renewing whatever my universal
subscription will now be called. Even though I can upgrade to whatever
version of TS I choose, I think I will be going from enterprise architect
down to pro. Maybe it's time to look closer at Mono!

Cheers,
Dave

 

[Cowboy \(Gregory A. Beamer\)]

Here is a question. Answer true or false:

I am willing to wait until 2006 or 2007, if I can have Visual Studio with
basic Team System templates?

If the answer is no, then the direction MS is heading is correct, at least
for the present. If no, then it is wrong.

As a developer, I can understand the feelings here. VSTS will make us better
at our jobs. I also realize that the product is currently being developed
with the scenario of having VSTS as a "complete package". The problem is the
tools, today, are tied into the Team Foundation, which requires a server. It
is not a simple matter of adding the tools into Visual Studio at this time.
Could it be changed later? Sure. Will it be? The market will help decide
that.

Here is what I see is the biggest problem

Today Tomorrow
Standard Express
Professional Standard
Enterprise Professional
N/A Team System

In the naming, it appears you are losing functionality. What is actually
happening is the product is getting better on all levels.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think outside the box!
***********************************************