Visual Studio Community Edition now?
-
In the world of free VS, first there was the Express edition, which lacked things like a resource editor (for unmanaged code), etc. Anyone know what the deal is with the Community edition? Is it still gimped somehow? The sales pitch says it has more to it than the Express edition, but doesn't say what exactly. I won't install it since I have 2013 Ultimate, but my MSDN sub expired and I really don't feel like getting a new one when VS 2015 hits the scene.
Jeremy Falcon
Sounds like something liberals have cooked up...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
In the world of free VS, first there was the Express edition, which lacked things like a resource editor (for unmanaged code), etc. Anyone know what the deal is with the Community edition? Is it still gimped somehow? The sales pitch says it has more to it than the Express edition, but doesn't say what exactly. I won't install it since I have 2013 Ultimate, but my MSDN sub expired and I really don't feel like getting a new one when VS 2015 hits the scene.
Jeremy Falcon
I can't help but wonder if this is an attempt to lure developers over to a monthly fee service. Though its not required to use TFS/VSOL it certainly makes it seem a lot more palatable to spend $20 or $45 (US) per month when you feel you are saving the hefty fee that VS Pro used to be. Nothing malicious here (that I can see) but the pay as you go model is where they want to be heading with many of their products (Azure, Office, possibly Windows)
-
It's VS2013 Pro with a limited license:
http://www.visualstudio.com/products/visual-studio-community-vs[^]:
- Any individual developer can use Visual Studio Community to create their own free or paid apps.
- 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 5 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.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Is it just me, or is there a huge gap between companies that have ~250 PCs, and companies that make in the neighborhood of $1 million in yearly revenue? Or to put it another way... what company has 249 PCs but makes less than $1 million a year? Pretty sure there should be an extra 0 or 2 on that revenue amount for the comparison to be relevant.
-
I can't help but wonder if this is an attempt to lure developers over to a monthly fee service. Though its not required to use TFS/VSOL it certainly makes it seem a lot more palatable to spend $20 or $45 (US) per month when you feel you are saving the hefty fee that VS Pro used to be. Nothing malicious here (that I can see) but the pay as you go model is where they want to be heading with many of their products (Azure, Office, possibly Windows)
That wouldn't surprise me at all. But at least we can use other tools for code repos, so at least it's win-win ya know.
Jeremy Falcon
-
Is it just me, or is there a huge gap between companies that have ~250 PCs, and companies that make in the neighborhood of $1 million in yearly revenue? Or to put it another way... what company has 249 PCs but makes less than $1 million a year? Pretty sure there should be an extra 0 or 2 on that revenue amount for the comparison to be relevant.
I think they intended that as a catch-all, to prevent someone from using it for free in a large corporation that did not yet have sales, or never would. I suppose a research subsidiary of a for-profit corporation? A million in revenue is a pretty low target too. Product sales company on a 5% net margin, still only $50K a year net income.
-
I think they intended that as a catch-all, to prevent someone from using it for free in a large corporation that did not yet have sales, or never would. I suppose a research subsidiary of a for-profit corporation? A million in revenue is a pretty low target too. Product sales company on a 5% net margin, still only $50K a year net income.
I think revenue is a company's gross income, not their net. Even non-profit organizations require revenue to pay the salaries of their employees. How many employees can a company afford to have if they are making less than $1 million a year?
-
One important difference in it - you can use extensions in it. Express didn't let you.
And... Resharper works with Community Edition! :-D
-
I think revenue is a company's gross income, not their net. Even non-profit organizations require revenue to pay the salaries of their employees. How many employees can a company afford to have if they are making less than $1 million a year?
Yes, I was pointing out that as it applies to for-profit companies, the license restricts it to probably 1 or 2 employees. They're aiming at making it free for start-ups, students, and lone programmers, probably on the theory that if you write enough of your code in it, you'll pay to use it rather than switch.
-
Yes, I was pointing out that as it applies to for-profit companies, the license restricts it to probably 1 or 2 employees. They're aiming at making it free for start-ups, students, and lone programmers, probably on the theory that if you write enough of your code in it, you'll pay to use it rather than switch.
The problem is that MS doesn't currently offer a viable solution for "small" software development companies anymore. In "ye olden tymes", it was simple, you just bought a MSDN subscription for every in-house developer and they were legal to create software for every MS OS using any/every Microsoft tool available. Now you have to purchase separate licenses for the particular version of Visual Studio you want to use/support, so you end up with situations like ours: a small handful of people doing "new" work in Visual Studio 2012 while the rest do their maintenance work using VS2005. I had hoped that the new Community Edition might provide a solution, but MS's odd definition of "Enterprise Organization" leaves us out.
-
The problem is that MS doesn't currently offer a viable solution for "small" software development companies anymore. In "ye olden tymes", it was simple, you just bought a MSDN subscription for every in-house developer and they were legal to create software for every MS OS using any/every Microsoft tool available. Now you have to purchase separate licenses for the particular version of Visual Studio you want to use/support, so you end up with situations like ours: a small handful of people doing "new" work in Visual Studio 2012 while the rest do their maintenance work using VS2005. I had hoped that the new Community Edition might provide a solution, but MS's odd definition of "Enterprise Organization" leaves us out.
Perhaps the Microsoft definition of 'Enterprise Organization' should read 'Possibly Viable Business'. Once a startup has a few paying customers, Microsoft wants a piece of the action. Probably someone tallied up their net revenue from educational licences and realized that it would be far cheaper to give the software away.
