Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I am looking for advice on the most appropriate MSDN license (without overpaying) for the following development team.
We are essentially a (3-5 developers) SharePoint/.Net development team that will be developing to SharePoint 2010. We also want to integrate with Team Foundation Server so any advice on the appropriate license for that product is also welcome.
My thinking is that we can benefit from VS Premium but hope to be able to get away with VS Professional. It seems that VS Ultimate is overkill and at $11,899 per seat is a nutty price.
All thoughts welcome!
Thanks
If you're a startup making less than $1 million per year I'd suggest you take a look at BizSpark. It essentially is MSDN free for three years and at the end you pay $100.
If you're a company making more than $1 million a year then you'll probably have to pay for one of the standard MSDN licenses. I think Ultimate is overkill in most cases as well. It is there because there are some companies that will buy ultimate no matter what the price is.
You'll get a TFS license that includes SQL Server Standard and 5 limited use (only can be used against one TFS server) CAL's with a VS Pro subscription or higher. In my opinion, Professional is a pretty good deal at $1200 a seat considering what you get.
You get a TFS license with each level of a MSDN subscription now.
Expression Studio is included with Premium and Ultimate, if that is useful to you. Same for production licenses of Office, Project, and Visio. If these are not important, or if you have other arrangements for them, perhaps MSDN w/ VS Professional would be best.
Premium seems to strike a good balance between the two extremes - most if not all of the useful tools, but at a lower cost than Ultimate.
Related
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 currently use express version of Visual Studio 2013, and I am quite satisfied with it. But I now feel the need to use visual studio ultimate version (too big expectations as it is out of my budget)
So, I came across a dealer who claims that he can give me a pirated version of visual studio ultimate 2013 for considerably low price and now I consider what will be the disadvantages of it? In my country (India) this type of thing is popular. So, my question is does microsoft use some kind of system with which it will recognize if the software or product which is developed with visual studio using a pirated copy of visual studio?
My decision totally depends from the answers which I get from you.
Again: Is it recognizable if I use pirated visual studio for developing applications? Be specific.
Thanks, in advance.
While there are no shortage of people who will lecture you on the evils of pirated software... from the unknown quality (you don't know if it contains viruses or malware) to the ethical and legal issues (yes, its illegal, even if you are unlikely to get "caught" even in your country).
There are better alternatives, however. Microsoft has a number of programs in which you can get very cheap or even free software if you meet certain conditions. For instance, the DreamSpark program gives you access to commercial versions of Visual Studio and other software for free if you are a student. It's not the Ultimate version, but it's the Professional Version.
There is also the Microsoft Student Developer Program.
If you own your own business, and meet certain requirements, there is also the BizSpark and WebsiteSpark programs. This does give you Ultimate access, and if you have your own business (or know someone who does and is willing to foster your membership) then this is a great program. You get it all for 3 years for no cost.
Finally, there are discounts you can get as well from various sources, and you might check with your local Microsoft offices. There is also the ActionPack and ActionPack Development & Design programs, again you have to have a business.. but you can probably find a way to make that work if you're creative, and legal and ethical, and its software you can trust.
And of course, there is the Community Edition of Visual Studio, which is a fully featured version of VS and free for anyone who isn't a large business.
microsoft sells licenses to use their software; to be legitimate, U should purchase a license from them. If, OTOH, U want software for which U don't have to pay (and U want to be legitimate), try an open source compiler, like the MinGW compiler, or the C# scripting engine CS-Script, which works with the CLR of .NET, and which can also generate executables. i'm not wild about the MS licensing model, because if there's an error in their code, i can't do anything about it, but i think it's best to respect it, if for no other reason than to keep them off your back.
if U want to violate the model, which, while admittedly stupid, is their choice and also backed up by the law in my country, U'll get no help from me.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Now that Microsoft has released VS 2010 I went to the product page here. To my amazement I found out that IntelliTrace(Historical Debugger) is supported only on the Ultimate Edition of VS 2010. This mean that you have to spend almost $4000 for renewal and almost $12000 for a new license. Does someone have any idea how can we change this decision? Especially make them add this feature to VS 2010 Professional Edition.
This is of course fundamentally a question to Product Management at Microsoft. They will have profiles of the intended market segments they're targetting. Willingness ot part with cash is one of those things, yes. But on the linked page, there's a small 2 line blurb that's also telling. The cheaper editions are expected to be used by individuals on small projects, the more expensive by teams on larger projects. Therefore many of the distinguishing features support those larger projects.
So, to answer the title question, you need to explain to MS Product Management that IntelliTrace is not a reason for you to choose VS 2010 Ultimate Edition, but it would be a reason for you to upgrade from 2005/2008 to VS 2010 Professional Edition. Since Vista, MS Product Management certainly understands version skipping, so this can be a convincing argument.
While I would love to have both static analysis of code contracts, intellitrace, and the new sequence diagram stuff built into Premium and Ultimate, I understand that there are multiple SKUs for different prices.
I don't think there is much we can do to change this at this point, so expect to either live with the missing features, or live with the missing money.
If you want to use superior stuff, you are expected to shell out some cash.
More Features= More Money. And this is universal principal.
Besides you can always look for add-ons which have similar functionality and which cost less than the Ultimate Edition.
IntelliTrace is the killer feature of VS2010 (for some, at least), so Microsoft marketing is simply trying to get a high ROI specifically on this feature by getting people to convert.
Although Intellitrace qualifies as a premium feature, there are lots of other features both in Visual Studio and other Microsoft products that at one time were treated as "premium". Eventually, adoption-through-the-grassroots prevailed and those features became part of lower-priced product editions.
Here are two distinctly different approaches to making the case:
Microsoft stands to make more money via grassroots-adoption - its traditional strength - than by premium editions that are way outside the budgets of most developers and organizations.
If Intellitrace were to be packaged separately (for a price), it would be considerably more affordable. It would be very difficult for Microsoft to claim that it couldn't do this because it has already unbundled Internet Explorer - a considerably more difficult challenge. Unbundling Intellitrace and selling it separately would basically result in a windfall for Microsoft. They'd sell fewer copies of VS Ultimate, but they'd more than make up for that in Intellitrace sales.
As with any product with 'premium' packages, some features will need to be kept for those willing to pay the price.
Much as I'd love to start a revolution I can't see this one moving. Maybe in future versions this feature will filter down.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 8 years ago.
Improve this question
So - this is a question to all the Visual Studio users out there - what addons do you use, and can't live without - and why ?
Just one: ReSharper!
Can't live without it.
Resharper or devexpress refactor (pro or express )
.NET Reflector
AnkhSvn
Microsoft StyleCop
VisualSVN if you're using Subversion. It works amazingly well, and it doesn't mess with Visual Studio's brain-damaged source control bindings.
I use VisualSVN but I heard since v2.0 AnkhSVN is pretty solid, personally for $49 dollars it is a solution I already bought into and has always been stable.
Resharper is a must.
Aside from those two VS2008 provides everything I need. On VS2005 I use CoolCommands to get some things like 'Open Folder in Explorer' from solution explorer too.
I forget... I use Test-Driven.Net plugin to get the right click 'Reflector' and test coverage with NCoverExplorer for the rare times I use it, and the even more rare times when JetBrains implementation of NUnit via their Test runner doesnt work.
First and foremost: CodeRush - absolutely the best and greatest addon there is - even in a FREE FOR ALL version (CodeRush Xpress).
Next: PowerCommands for Visual Studio 2008 - free as well
Others: Only for specific topics, e.g. VisualSVN for Subversion access etc.
Marc
Visual Assist X - Whole Tomato
I don't use any addons. VS is good enough.
I knew someone would beat me to R#, without a doubt the best productivity add-on.
Other than that, AnkhSVN as an SVN client and that's pretty much it. IMHO VS2008 is an excellent IDE that doesn't need to many add-ons.
Not an addon but it's manually installed like an addon and overlooked by a lot of developers: SP1 for VS2008. Finally adds background compilation! Also greatly improved Javascript editing.
These tool are very useful
Outliner Power Toy
Power Commands
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I developed a small winforms application for myself in Microsoft Visual Studio 2008 Professional Edition at my workplace, the Visual Studio is licensed to the firm I work at.
If I want to sell that application, what are my license options?
EDIT:
The issue here is not my relationship with my employer (the code was written after hours, we have an understanding) but my relationship with Microsoft.
Ex. if I continue developing in Visual Studio Express can I keep my old code? Is there a way to verify if some assemblies were written using a Visual Studio Professional?
I would say that depended more on your contract with your employer rather than the licensing of Visual Studio itself. If it's a properly licensed copy, then the issue lies solely with your employer.
A lot of developer's contracts do state that any code written whilst at work, or on the employer's equipment, or even at any time whilst employed, belongs to the employer.
If that is not the case, I'd download a copy of Visual Studio Express, and do any further development on your own system, just to cover yourself.
I'm not a lawyer, but generally if you develop something at work, using your employer's tools, then they own it, not you.
If you have an "understanding" get it in writing. If your product turns out to be a money maker then you'll be glad you did.
As for Visual Studio, you should be fine distributing the application with whatever license you choose. If you want to keep developing at home, move it over to Express (you can keep your code, but may have to deal with the lower level of functionality in Express) or buy a license for Pro.
I'm having trouble seeing what the issue here is. Assuming your employer has a properly licensed copy of Visual Studio, they have the right to let you use it for any purpose they choose. It's no business of Microsoft's whether or not they let you use company resources for your own project.
The EULA that you agreed to when you installed Visual Studio is quite explicit. Not only do you own the rights to the code you develop using VS, you are required to explicitly claim copyright on your code.
One file you should review is redist.txt, it is copied to the installation directory. It lists the files that are owned by Microsoft that you are allowed to redistribute freely. All the essentials are there, like the .NET framework. Anything that is not in that list is not yours to use.
There is one specific exclusion in the EULA, you are not allowed to develop a product that can be used to allow your customers to access Internet resources for a fee. A bit of an odd-ball exclusion, I assume it is meant to suppress competition for a business segment that MSFT doesn't control.
Finally, as others have alluded, an "understanding" with your employer means squat when it is crunch time. Carefully review the employee contract you signed. It's been quite a while since I last saw one that didn't claim ownership of after-hours work. As well as "related" works produced after the end of the agreement for a certain period. IP is big, your brain is pwned.
Microsoft's DreamSpark ( https://www.dreamspark.com/default.aspx ) program might be a good option. Basically a three-year MSDN subscription for free (with some requirements about building an actual product, etc. - sounds perfect)
Edit: It's "BizSpark": http://www.microsoft.com/BizSpark/
Try if the project works in Visual Studio Express Edition.
It it does, the problem is solved.
If not, return to step 1.
Don't know about the bytecode itself, but first check the assembly file properties. On my vista box I right click -> properties then select the details tab. Then run ILDASM and check the properties on the assembly.
Also double check the EULA on the express editions, the web page specifies it targets "hobbyist" and "enthusiasts". My paranoid side thinks there might be identifiable stuff.
Finally if you want to be really careful, just download the SDK compile your code on the command line before distributing your code.
Explore the EULA on VS Professional. You should be able to discern what you can and can't do from there. Compare this to the EULA for Express. It's tedious, but it's the right place to start.