|
Welcome to the VS ship.
The only difference Community has compared to Professional is licensing. Basically you can only ise it if you're in academics or open-source or in a team with less than 5(?) devs, I can't remember the exact license. So if you're solo, you're good.
|
|
|
|
|
Sometimes your sort of forced to upgrade to be able to code the next version of windows and mobile devices.
I'm happy with VS2012, but I do use VS2013 for Windows Apps.
And I didn't care for the licensing model of VS2013 MSDN subscription, where if you didn't fire it up every 30 days, the 1 year license expires.
|
|
|
|
|
Wait what?!?!
A bit of Googling[^] suggests you should be able to make the 30 day signon to the MS cloud for license verification go away by manually installing the product key from MSDN.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I had a MSDN subscription along with an action pack.
The MSDN subscription allows for 3 users to use software for 1 year.
so if yo u don't' fire up VS2013 every 28 days, the license expires, and you have to use another user to reactivate it.
I had to call MSDN tech support and use a tech support incident to figure it out.
Now I use the community version of VS2013
|
|
|
|
|
I will definitely update to VS 2015 for home use. When I have time (I also run a ranch), I play with the VS, creating and updating the programs I use to keep ranch records. Every year, it seems like either the DoA (Department of Agriculture) or the State of Texas introduce some new record keeping requirement.
At work (I work for a .org) is a different story. We will have to upgrade eventually, but I am not sure when. The biggest issue is the budget, most of which pays for the services to our clients, mostly in the form of the salary of our clinicians. Not much is left over for niceties, such as new office furniture, new software tools, new servers, et al.
Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now.
© 2009, Rex Hammock
|
|
|
|
|
At work we try to stay up-to-date, and because most of my time at work is spent with SSIS, that makes sense. But all versions of VS are overkill for the small amount of "real" development I do.
At home I'm still using 2010 (when I use VS at all), and bemoaning the problems it has. Would rather use VS2008.
|
|
|
|
|
I have been waiting for Visual Studio's next version. Not because it is the next big thing... But instead because I have been waiting for Visual C#'s 6th version and also for ASP.NET's 5th version.
I have been waiting to host it in Console application also. Secondly, I want to try the new Dictionary objects and their value passing etc.
Also I have install the technical preview in my brother's laptop to teach him about programming... I have loved the new debugging tools, memory snap shots and all of the new content. I am loving it! Visual Studio 2015 has amazed me in many ways... One of them is the Blend. Which enables you to design the XAML user-interface just the way you did in Windows Forms.
Cross-platform using Xamarin didn't catch my eye. But, cross-platform programming in C++ did catch my eye and I am waiting for that (eagerly)!
So, I would definitely upgrade to Visual Studio 2015.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Well - I've been busy . . .
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
...this is a Microsoft product, so I'll probably wait for SP1 - or as the rest of the world calls it "Releasable product" instead of "Still in Beta". 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Sad, but so true
My plan is to live forever ... so far so good
|
|
|
|
|
Personally there's no reason not to switch as I have only a few projects, none which are very big. And it's free with the Community Edition!
Professionally we're still in VS2010, but we'll switch to 2015, skipping 2012 and 2013.
As far as I know you can just run .NET 4.0 projects (without upgrading) in 2015 without any problems whatsoever?
|
|
|
|
|
still needing to pass to 2008 but we'll skip, maybe, to 2012. We don't and can't use .NET so little difference is made, we still have to support win2k and XP so no big deal, but... in the time VS 2008 boots up I have already opened several VS6.
Also we'd need a hardware upgrade to run Win7 and that powerful stuff, we still go on with 1GB of ram (I have 2 because I robbed a PC that I requested as "extra"... until they ask it back I have taken also the 250 GB disk instead of the 80 GB built in. Yes it's stone age, no the management doesn't care).
Geek code v 3.12
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
I use 1TBS
|
|
|
|
|
...but as we already started a development cycle before it, we will finish it using 2013...
To update all the development team in the middle of such cycle is too disturbing...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Almost Each year I am up-grading my Visual studio, I agree that there are many new features implemented in each version and it will helpful for development but while understanding whole new features list, MS again introduce new Visual studio, eventually I need to upgrade that new version and Sometimes I think ....I am Wasting my time in up gradation rather than development
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
"Not immediately" seems awfully similar to "eventually". Perhaps the survey intended to offer these choices?
- Yes, we'll upgrade from a previous version of Visual Studio
- Yes, but we don't use Visual Studio at the moment.
- Yes, soon.
- Yes, eventually.
- Probably not.
- Definitely not.
/ravi
|
|
|
|
|
Well, VS2015 C++ does support Resumable Functions.. (just kidding)
|
|
|
|
|
I like to stay a couple of years behind. Currently, I am upgrading a lot of our stuff to 4.5 framework and solutions to VS 2013. I don't like getting too far ahead so I don't waste time with things like WF and Silverlight.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
