What studio to use?

Question

ASP.NET

It's 2015 outside, and at work we use Visual Studio 2010. I would like to know if many people have been sitting on old IDEs for years or keeping up with the times? Do you use different studios at home and at work? Is there a dependence of the studio version on the type of project (web, desktop)?

Answer 1

the main reasons for using old studios:
1 - large projects - it is difficult (or everything is stupidly scrapped) to remake, it is not uncommon also to depend on third-party projects that the authors no longer support - except for dependencies on framework versions, if there are dependencies on compilers and builders . for example, try to get acquainted with the mpir.org project - cool math for .NET, but since the community is being developed, it always lags behind one or two versions of the studio. adapting it yourself to the latest version is, to put it mildly, not at all trivial
2 - projects that are difficult to manage in express (free) studios (for example, advanced teamwork capabilities are required) + company policy does not allow the use of pirated software, and I do not allocate money for updates to professional / ultimate studios (in fact, 2013 already has advanced community studio available for free, but not everyone has it in their heads yet + global transitions by themselves, still require a lot of effort)
3 - just old hardware and not very big projects - new studios will still toss and turn, and old ones fly
and for home / for the soul - everyone decides for himself
naturally for development it is useful to work in the latest studio - working with different versions broadens one's horizons
and taking work home is in itself a sign of low efficiency and poor organization of your own work,
but in some cases you can have different versions of studios at home - in virtual machines or in different copies of Windows with multi-boot. for example, if you need 2010 for work, 2012 for using an mpir-type project, 2015 for general development, and so on ... it's
best to install different studios in different copies of Windows (virtual machines), some versions, in principle, cannot work correctly together . you can also install some versions of express to save resources, it already depends on the intended tasks for this version

Answer 2

The reason is simple: you are using old runtime/compilers/frameworks, and they are part of VS.
It is usually impossible to transfer a project to new ones because of their incompatibility.
Other IDEs do not have such problems (they are just IDEs, without frameworks, runtimes, etc.) and therefore it is customary on the web to use the latest versions of development software.

Answer 3

Of course, you can put Ultimate at home)
At work, stable 2012. At home 2012 Ultimate and a preview of 2015.
In general, I would switch to 2013 C at home, instead of 2012, but since I already installed 2015, I will have to wait for the time when the OS is covered. Downgrade is a bad thing.

Answer 4

We are still working on the 2008 studio (a large C++ project), we tried to switch to 2012 two years ago, but couldn't because of product support problems under Windows XP - there were problems with runtimes. Microsoft later sort of fixed them, but we didn’t try a second time. Now we are waiting for users to get off XP. And in 2012, we only look at dumps and profile.
It is much easier with .NET in this regard, the studio now has the ability to choose any framework as a target platform, starting from 2.0, so upgrading is not a problem in most cases.

Answer 5

It seems to me that for indie developers now such a question should not stand: VSCE .
True, I’ve been out of the subject for a long time, but in appearance everything looks very, very.

Answer 6

2013 brake crap compared to 2008. C++.

Answer 7

At work I use VS 2013 + SharpDevelop 5.1, at home I use it + Mono / Monodevelop for linux