I'm having this question since a month and I'm not able to test it, so i want to ask here if someone have met this situation. Since there is no official release of the new Visual Studio 2015 and it's on RC now ,I'm interested in does someone know if VS 2015 and VS 2013 could work together? Will be the code "infected" if both sides commit something together? Thanks in advance!
In theory yes, in practice no (or at least your results may vary). VS is designed for side by side installations. For consultants it is very common to have multiple versions of VS installed to match the environment of the client.
That being said, RC is pre release software and bugs are to be expected. Nobody can guarantee you won't have problems. VS is a huge and complex codebase. Throw in the number of permutations of possible plugins and extensions as well as environment conditions and there is always a chance of breaking. Just because it didn't blow up on someone else's system doesn't mean you won't have problems.
When I installed VS 2015 CTP6 a few months ago it broke an install of VS 2013 on the same machine. VS 2015 CTP6 installed without error but trying to "login" (Microsoft's new annoying way to infect all software with a user login) hung and became unresponsive. Upon restart devenv.exe complained about corrupted user settings and even before I tried I had a bad feeling that VS 2013 blew up as well. I was right and it took a reinstall to get it working.
Now on the other hand I installed VS 2015 RC side by side on a machine with VS 2010, 2012 and 2013 without any issue. Does that mean you are guaranteed to not have a problem? Of course not. It is pre-release software. If this is a mission critical machine and you don't have the time to potentially spend a few hours reinstalling VS 2013 I would install it in a VM. If it isn't mission critical or you have the time to reinstall if necessary then roll the dice. Honestly you "should" be fine, the RC is pretty stable but you never know.
You should be fine - you'll be using an existing code-base and as long as you don't change the .NET version in the properties, it will compile the same.
However, if you do want to check out the new vNext solutions, you'd have to specifically select the project template in the new project wizard.
These projects are run on the new DNX runtime (which is still evolving and subject to change)
Side by Side. Visual Studio 2015 (even RC) works seamlessly side-by-side with Visual Studio 2013.
See BUILD 2015 News: Visual Studio Code, Visual Studio 2015 RC, Team Foundation Server 2015 RC, Visual Studio 2013 Update 5
or the official guide in the documentation
you might follow the links inside for details about how to configure the target language specific frameworks.
On several PC's in my environment when Visual Studio 2013 saves files Visual Studio will lockup for a minute or more. I ran process monitor and it appears to make the same call over an over again from lsass.exe. This same call happens on other PCs. I am trying to figure out how to resolve this issue and would appreciate any help from the community.
Thanks,
John Ruf
I am at a total loss when it comes to WPI and the continous reinstallation of Visual Studio 2010 SP1. I have even went as far as creating a virgin machine and installed VS2010 and then immediatly installed the tools from WPI. After completion (which shows success) I reboot the machine and then load the WPI again to add on secondary tools. At which point, the WPI triggers an installation of the SP1 -- 90 minutes later, the list shows up as successful, and other tools are listed for installation.
Every time you run WPI, it wants to go through the VS2010 setup over and over. Is there any way to fix this behaviour?
Thanks in advance.
Yesterday I installed SP1 on my Visual Studio 2010 Ultimate, and I'm not sure if this is cause or correlation, but since then VS takes forever to open a solution. The "Preparing solution" dialogue has been showing for about 15 minutes now. Last night, after SP1, it wasn't as long, but it did take about 5 minutes to 'prepare the solution'. Anyone know anything about such issues with SP1?
Works for me : Try CTRL-ALT-SHIFT J twice. It calls the garbadge collector of the CLR gfx interface.
Does Visual Studio 2010 RC play nicely with Visual Studio 2008?
I am wondering if I need to setup a Virtual Machine to play with VS 2010 or if I can just install it on my Dev machine.
If it messes up VS 2010 then that is sad but ok. If it messed up VS 2008 then I would be in trouble.
Has anyone tried this out? Does it work well? Poorly?
Thanks for any answers.
I've had no problems. Microsoft has designed the last several versions of Visual Studio to be able to co-exist side-by-side.
That said, VS 2010 is an RC, so it is still a pre-release. And even after it goes RTM, it's still a complex product and like any complex software install there can be bugs. I wouldn't expect serious problems, but there's always the fraction of a percent that do run into issues. So I'd still plan to install it on a day when you'd have cycles to deal with potential issues (if nothing else, installing it on my machine that hadn't had OS updates installed in a while required at least 2 reboots).
Yes this works and is a supported scenario. My advice is to install 2008 first then 2010. This is the setup i have on multiple computers.
has worked for me without any issues so far. I would follow JaredPar's advice though, install 2008 first, then 2010.
I never trust the "plays nice with others" claims because I've been bit by it before. They supposedly co-exist, but I still put it in a VM.
See this blog post.
Visual Studio 2010 / .NET Framework 4 RC Ready for General Download
I haven't installed it on my machine but my manager has and after we looked at it we decided it's best not to go there yet for two reasons:
1) We have to go through the whole conversion process again, which after our experience with 1.1 -> 2.0 wasn't very enticing.
2) We caused an error within the first couple minutes of playing around that worked fine on VS2008 leading us to believe it's not quite ready for primetime yet anyways. (It was adding a method in the class diagram that caused VS to crash for some reason).
Just my two cents though.
edit: I just found another great example, fifth one down: http://thedailywtf.com/Articles/Tell-a-programmer.aspx
I've had no problems either. And I didn't with VS2010 beta 2 and VS2008 either.
I have both of them on my machine, so far no problems
I havent go into too much testing with my VS 2008 projects in 2010, but it does look like it works fine with VS 2010 RC.
Also, both versions seem to run fine on my machine. (I have also VS 2003 on my local as well)
Bearing in mind its the Release Candidate version, is should be very reliable in this area.
I've run into an error with IIS and VS2010 -- it's solved by re-running the .NET 3.5 version of aspnet_regiis.
http://social.msdn.microsoft.com/Forums/en-US/vsprereleaseannouncements/thread/44dfcf76-bede-4f96-a556-b219a18b6116
I installed 2010 with 2008 already installed. I had tons of hangs, crashes and general malfunctions. Reinstalling 2008 didn't help until I removed every trace of 2010 from registry.
I've installed 2010 with 2008 on this machine for silverlight development.. I haven't noticed any problems except for file associations all goto the 2010 version rather than what I'd prefer opened in 2008 by default. (2010 to me is much slower than 2008)