I was under the impression that Microsoft Test Manager 2010 was included in Microsoft Visual Studio 2010 Premium. Is this not the case?
I can't seem to find anywhere online where it tells you which versions have the Test Manager included.
I'd really like to take advantage of the functionality of the Test Manager if possible, and MSDN's documentation on testing generally uses the Test Manager for just about everything it seems. So any information on the following would be much appreciated:
Is Microsoft Test Manager 2010 included in VS2010 Premium?
If so, where can it be found?
If not, which versions do include it?
Or is it a separate download in itself, in which case where can that download be found?
Microsoft has an article that runs down the testing in the new Visual Studio 2010 SKUs. It looks like Test Manager is only included in VS2010 Ultimate. The other SKUs can create tests that can be consumed by Test Manager, but the Ulitmate seems to be the only version with Test Manager.
It looks like it can be purchased separately from VS as part of the Visual Studio Test Professional 2010. There is a stand alone trial that can be downloaded.
Bottom line: If you need Test Manager, take a hard look at Ultimate not because it has more features ... the perverse pricing and promotion policies of Microsoft's various channels might mean that Ultimate is actually cheaper than a product with fewer features like Premium Get the CURRENT market price -- do not pay any attention to Microsoft list prices.
.
VS2010 Ultimate gives you Test Manager [and a lot of other benefits] ... you could add Visual Studio Test Professional 2010 with MSDN to Premium to just get Test Manager, but right now [as of early 12/19/2010] the best current market price for the full Ultimate version is significantly less than the Premium version through one of the merchants selling through Amazon. The CURRENT Amazon listings are as follows:
Visual Studio 2010 Premium with MSDN List price $5469 Offered price $4,989.99
Visual Studio 2010 Ultimate with MSDN List price $11899 Offered price $2,789.00
Visual Studio Test Professional 2010 with MSDN List price $2169 Offered price $1,925.99
Realize these prices were already out-of-date when I hit the [SAVE] button.
If you needed any proof, hopefully this example demonstrates that you cannot ever lazily assume that a better product with more features is going to cost more. It's not just Microsoft -- this is routine. The old adage "you get what pay for" does not work anywhere anymore -- you need to check market prices and haggle as you see fit.*
Related
This link provide us a comparison about three versions. Apparently only TFS features is the different. here
I guess that is more than that.Technically, Is it full featured ?
Otherwise why would we pay $45/month for professional version. Products
Per this link
VS Community Usage terms
For individuals
Any individual developer can use Visual Studio Community to create their own free or paid apps.
For organizations
An unlimited number of users within an organization can use Visual Studio Community for the following scenarios: in a classroom learning environment, for academic research, or for contributing to open source projects.
For all other usage scenarios:
In non-enterprise organizations, up to five users can use Visual Studio Community. In enterprise organizations (meaning those with >250 PCs or >$1 Million US Dollars in annual revenue), no use is permitted beyond the open source, academic research, and classroom learning environment scenarios described above.
For more information, see the Visual Studio Community license terms.
Licensing is the critical point.
If you develop in the contest of an organization, you must be within limits not buying Pro license (full details), e.g. classrooms, academic, open source projects plus some.
Technically they are the same and Team Explorer is built-in. My understanding (I can be wrong) regards the licensing: the features listed are almost all accessible via web interface, so there is no technical blocker as I see it.
BTW I contribute to an open source TFS plugin using Community edition and found no problems.
Then you have to consider the free tier of VSTS which is a separate license. For TFS on prem, you need some CAL (Client Access License) but there is some free tier also.
What's missing in Visual Studio Community 2015? They say it's full-featured and free, but if that's the case, then why do/will they still sell Visual Studio Ultimate 2015 or Visual Studio Enterprise 2015 for 6 grand?
Something is missing in the Community preview, right? And why is it called 'Community'? My code won't be synced across your devices like the new Windows 10 update system is, will it? (Kind of joking about that last part, and kind of not, too).
There are 2 major differences.
Technical
Licensing
Technical, there are 3 major differences:
First and foremost, Community doesn't have TFS support.
You'll just have to use git (arguable whether this constitutes a disadvantage or whether this actually is a good thing).
Note: This is what MS wrote. Actually, you can check-in&out with TFS as normal, if you have a TFS server in the network. You just cannot use Visual Studio as TFS SERVER.
Second, VS Community is severely limited in its testing capability.
Only unit tests. No Performance tests, no load tests, no performance profiling.
Third, VS Community's ability to create Virtual Environments has been severely cut.
On the other hand, syntax highlighting, IntelliSense, Step-Through debugging, GoTo-Definition, Git-Integration and Build/Publish are really all the features I need, and I guess that applies to a lot of developers.
For all other things, there are tools that do the same job faster, better and cheaper.
If you, like me, anyway use git, do unit testing with NUnit, and use Java-Tools to do Load-Testing on Linux plus TeamCity for CI, VS Community is more than sufficient, technically speaking.
Licensing:
A) If you're an individual developer (no enterprise, no organization), no difference (AFAIK), you can use CommunityEdition like you'd use the paid edition (as long as you don't do subcontracting)
B) You can use CommunityEdition freely for OpenSource (OSI) projects
C) If you're an educational insitution, you can use CommunityEdition freely (for education/classroom use)
D) If you're an enterprise with 250 PCs or users or more than one million US dollars in revenue (including subsidiaries), you are NOT ALLOWED to use CommunityEdition.
E) If you're not an enterprise as defined above, and don't do OSI or education, but are an "enterprise"/organization, with 5 or less concurrent (VS) developers, you can use VS Community freely (but only if you're the owner of the software and sell it, not if you're a subcontractor creating software for a larger enterprise, software which in the end the enterprise will own), otherwise you need a paid edition.
The above does not consitute legal advise.
See also:
https://softwareengineering.stackexchange.com/questions/262916/understanding-visual-studio-community-edition-license
Check the following: https://www.visualstudio.com/vs/compare/
Visual studio community is free version for students and other academics, individual developers, open-source projects, and small non-enterprise teams (see "Usage" section at bottom of linked page). While VSUltimate is for companies. You also get more things with paid versions!
Visual Studio Community is same (almost) as professional edition. What differs is that VS community do not have TFS features, and the licensing is different. As stated by #Stefan.
The different versions on VS are compared here -
https://www.visualstudio.com/en-us/products/compare-visual-studio-2015-products-vs
All these answers are partially wrong.
Microsoft has clarified that Community is for ANY USE as long as your revenue is under $1 Million US dollars. That is literally the only difference between Pro and Community. Corporate or free or not, irrelevant.
Even the lack of TFS support is not true. I can verify it is present and works perfectly.
EDIT: Here is an MSDN post regarding the $1M limit: MSDN (hint: it's in the VS 2017 license)
EDIT: Even over the revenue limit, open source is still free.
I am the sole .net developer for a small company. My projects span many .net technologies including WinForms, WPF, SQL, XNA, Linq, WCF, WTF?, and others.
I struggle staying on top of all these projects so I'm looking to make my life easier with the release of VS2010. Without a mentor I rely heavily on StackOverflow and whatever else Google comes up with. Should I convince my company to get an edition with an MSDN subscription? Is it one of those things where once you have it, you can't imagine life without it?
What about the source control that comes with VS2010, do you all find it better than an SVN server?
We're looking to hire another programmer this year, would I be best off getting a Team edition of VS2010 to be best prepared for that hire?
Thanks!
If you want "Intellitrace" (aka "historical debugging") you'll need Ultimate.
Similarly Premium and Professional incrementally have fewer features. Any other these, or some combination could be the deciding factor. There is a comparison on the product pages.
Also, consider the value of an MSDN Subscription, getting you access to OSs, servers and tools for development and test (and one instance of Office for general use).
Even as a sole developer you should still be using source control (unless it is VSS :-)), whether SVN, GIT, TFS, ... all the paid editions will give you integration. ALM (application lifecycle management) like TFS will do source code control (SCM or VCS) as well as work item tracking (defects, feastrues) and much more. VS paid editions + MSDN include TFS (and you can run it on a Workstation -- server OS only no longer).
In my opinion if you are being employed professionally as a developer in the MS platform, VS Pro + MSDN is a minimum (otherwise ask yourself about the standard of employment), and really it should be VS Ultimate + MSDN. Compare the cost of employing you with the cost of the subscription (especially once on a VL program -- and you only need a single MSDN subscription to qualify for VL).
Visual Studio is a great product and I use it daily. Our level of MSDN subscription is Premium. This opens most of the doors in the MSDN library and I can't say I'm missing Ultimate. When Visual Studio was still RC and Beta we were developing in it (Ultimate) and things like IntelliTrace were nice to have features but were definitely not make or break.
I would advise against getting Visual Studio Premium because it is lacking in some of the features that I use extensively such as Code Coverage and static code analysis.
I'd have to say I can't imagine life without an MSDN subscription. It would be impossible to develop (and test) on the range of platforms necessary.
As for the source repositories we have been using TFS 2010 for the last few months and found that the seamless integration with Visual Studio is the huge selling point. The ability to check-in and out is only one aspect of the system. The ability to create build definitions, view build history and manage work items, all through the IDE, saves so much time.
If price becomes a problem there are always alternatives to Microsoft. If you want to use SVN there are SVN plugins such as VisualSVN and ankhsvn. You could then use something like CruiseControl.Net for builds.
Working as a single developer or in a small team I've usually found that any version of VS (except for Express) is ok, the Ultimate version do have some interesting things, but not anything essential for many developers.
I'd suggest that you (or your boss) look at the Microsoft Action Pack. They've got a new one for developers where you'll get 3 VS Pro licenses plus a bunch of OS and Server licenses (some of them only for development but some of them are valid for any employee I think).
In England it seems to be about £290 per year with the 15% discount that's on right now, so very cheap for what you get. There are some requirements, but if you develop software using MS Software you probably have a fairly high chance of qualifying:
https://partner.microsoft.com/40132997
Friend of mine just established own coding company. They wanted create professional application written in .NET.
Now he on the stage buying software. We have discussed what VS version is absolutely minimum for this purposes.
There are lot of different version Professional / Team Suite / Team Developer ...
I wonder what you recommend?
Ideally: less (possible) cost but not short-sightedness? Would be possible base on only VS Professional Edition?
I forgot to add that friend's company is partially refunded by EU. So it would be better to him spend more money at start then pay for upgrade in future. So, looking rather for target solution.
We have looked at comparison matrix obviously. We couldn't find strong arguments for "Team" edition. Believe most of "Team" features can be supplemented by 3rd parity tools (nUnit, Subversion, Resharper) what he used to use anyway...
If VS Professional would be selected - GDR will be the one think we noticed really missing in that approach.
Definitely check out Microsoft BizSpark. For next to nothing Microsoft will provide a software startup with Visual Studio, SQL Server, and other dev tools. I would also say that the edition doesn't matter as much as what comes with it. Look at the feature matrices of the various VS packages and figure out what you need. You can always upgrade later. I've done a lot of contract work with VS Express and there are no licensing restrictions on what you do with the software you build. Start small, and buy as necessary.
I suggest a look at the Visual Studio Editions comparison sheet and just check what you need. Note that from a technical perspective, you are not locked if you choose to start with a smaller edition.
At least Pro - given the description above you want to look at the BizSpark programme. If you don't/can't go down that route then you should be looking at an MSDN sub to at least the VS Pro level.
I would start with the Express Editions and upgrade to another edition if you miss functionallity (e.g. Add-Ins like Resharper; they cannot be used in the express edition). Upgrading is no problem since you can use your projects in all editions.
Already have MSDN with Team System Test Edition, how do I go about getting Developer Edition? Can't find it on MSDN.
Do I need to buy a whole other MSDN license for this?
Can you add just another SKU into the Team System family, in other words, can you have 2 Team System Versions, or does it have to be the Team $uite MegaVersion or single versions?
Also, can you use FxCop with the nice VS shell integration inside of VS Test Edition?
Any URLs/hints would be greatly appreciated. Seems to me that there's very little documentation on how to mix and match VS versions. Would be great if MSFT had a "Visual Studio store" MENU ITEM in VS where you could go and just buy/download the different SKUs automatically. I mean it takes me just a few clicks to download extra states into TurboTax, but MSFT makes that very hard to do.
P.S. Same set of questions for Visual Studio Database Edition.....yes I'm a dev that wears many hats.
There are 3 common levels of licensing that you see:
Visual Studio Pro - Doesn't include any of the team system features
Visual Studio Team System xxxxx Edition - Where xxxx is either Developer, Tester, Architect or DBPro. Includes all the functionality of VS Pro + the functionality associated with the role you chose.
Visual Studio Team Suite - Includes the functionality of all the different role editions.
If you have the VSTS Developer Edition and you want some of the functionality from the other roles, you either have to buy a 2nd VSTS license for the other role, or upgrade to VSTS Team Suite. If I remember correctly VSTS Team Suite is about twice the cost of a specific role version of VSTS, so rather than purchasing multiple role editions most people just opt to upgrade to Team Suite since the cost is approx. the same.
You can compare the list prices here: http://www.microsoft.com/visualstudio/en-us/howtobuy/compare-price.mspx
First, once you logon to the MSDN site, make sure you've clicked the "Downloads" tab at the top of the page, and then near the lower-right click on "MSDN Subscriber Downloads". Software that you have access to at your level of subscription will appear in the list.
Second, you may consider reviewing the details of your level of MSDN subscription if you still don't see what you're looking for.
I hope this helps!
If you will really be using all the different products, then it is best to have the full System license. I think 2 of the products make the price of the full, if you are using 3 ...