Visual Studio 2005, can I replace it?

Question

I have a machine in the company that has a version of Visual Studio 2005, for a kind of web system.

The machine had to go through a format and on the network not to a copy VS2005.

I can replace Visual Studio 2005 with some version, maybe Visual Studio Community?

My general concern is for some kind of incompatibility

Answer 1

The versions of Visual Studio 2002, 2003, 2005 and 2008 generate independent projects, that is when you open the most advanced version it converts to the new version. As of 2010, projects are computable, you can open in 2012 and then open in 2010 and so on.

As for the framework. Net it will maintain compatibility with the project, but some components will have to be updated like Reportserver and Crystalreports, and others if you are using.

Yes, you can replace, will have to make small adaptations, but nothing too laborious.

I recommend making a copy first if you need or wish to return.

Answer 2

There is some incompatibility, but it is small, certainly will have to make some adaptations, has even converter in it for the project files that have changed (think automatic wheel).

Now, a lot of things aren’t really incompatibility, it’s a different way of doing it. As you’re used to one thing, change can be scary, it can seem like you have problems and in fact it’s just lack of knowledge. You will have to decide whether to start using newer versions of the compiler and . Net, which I strongly advise, or if you will configure everything to work with old versions.

Some things that I have done in the project may be more incompatible than others, but I doubt that I find big problems, it is rare that someone does something very different. Of course it might be your case.

VS extensions may not be compatible, you may have to pick up a newer version or there is no new compatible version.

I could tell you that staying in 2005 is safer, but in practice it is the post, to keep such old software and as far as I know not more supported is that it is not safe. Go to 2015 now and pay the price of having to adapt. If you had made the updates over time it would be less traumatic. But don’t expect anything tragic. You must be a developer, then you must find solutions. If you have specific difficulties post here.

It is not something that is just install and will work, but it is perfectly feasible. At worst if it doesn’t work out even you could try coming back for VS 2005, which I wouldn’t advise at all.