I have VS 2015 Community full pack installed (44 as far as I saw) and I have to do a project in VS 2010 C# Express (I have to make a video about using that interface for my classmates at high-school, so I can explain them how to implement a database).
The idea is that I want to know if I can install VS 2010 and still keep the VS 2015 and then after I finish, uninstall 2010 safely (I have spent 4 hours installing VS 2015 and I don't want to waste that time again).
I've searched before posting this but one source of information I saw indicated that I can't do it, and somewhere else I saw that I can do it -- so I don't know what to believe. (sorry for my poor english)
I've been installing a half dozen versions of visual studio side by side for years. I've never had a problem, with any version of VS or express. I install them in any order I choose. I've even uninstalled them, although I do that far less frequently and can't vouch for its absolute reliability. Naturally it isn't tested as well as the side by side installation. I would recommend leaving vs2010 til youve run out of disk space, at least.
Related
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.
Ok, I have looked around on SO and haven't been able to find an answer to this question, but forgive me if I missed one out there. It's difficult to refine the search terms for this one.
But anyways, I have VS 2010 C# Express. I'm planning on doing some collaboration in my code (that was made entirely in Express) with someone who owns VS 2010 Ultimate. I have been putting off upgrading to the paid version of VS 2010 because of the price - if at all possible I would rather not upgrade. We are going to collaborate using Tortoise SVN as our version control software.
Will it be an issue for me to continue to work with the Express version while my collaborator works on VS 2010 Ultimate? To what degree will it be an issue, etc?
Follow-up question: If I have to upgrade to a paid version, would I have to upgrade to Ultimate, or would Professional be sufficient?
I have no experience with VS 2010 yet, but can offer observations based on VS 2008, using svn for source control.
I have only had one minor issue with using both the VB Express edition and VS2008 Standard and Professional versions on the same project. The express version does not support solution folders. I use a solution folder to allow quick access to some configuration files from the ide. The express version does not display the solution folder, but the remainser of the solution loads sucessfully, including all the included projects.
Well, my collaborator and I have started work, and no issues so far. Visual Studio 2010 Ultimate and Visual Studio Express are pretty much compatible, except for the Solutions folders, as described by B Pete.
Just curious how many people are actually running 2010 and what's your feedback so far?
Can I run 2010 concurrently with 2008 without issues?
Also, are 2008 projects 100% compatible with 2010 and if so should I just uninstall 2008?
Thanks for any feedback.
I've moved the whole development group for our project to VS2010 3 days after it came out. Before this I've been trying out the beta versions on my machine with some side projects.
From the experience I got I can say:
VS 2010 can easily run alongside VS
2008 on the same machine without any
issues whatsoever.
The projects
created in VS 2008 can be opened in
VS 2010. But when they are opened -
they will be updated to the new
format, and cannot be reopened in VS 2008. The changes aren't critical, so if it's necessary it is possible to
revert these changes. Possible, bt
not straightforward :)
This means that if you're working on a collaborative project, either the whole team moves to 2010, or you all stay with VS 2008. That doesn't mean you can't write your own projects in VS 2010 in parallel ^_^
UPD: I haven't met any projects that I wasn't able to convert using the conversion wizard. but just in case you can install VS 2010, convert your project, and see if it's all fine. If it is - work on it for a couple of days.. If you're completely satisfied - uninstall VS 2008 and feel good about it :D
Yes you can run 2010 concurrently with 2008. I wouldn't bet that every 2008 project can be opened/converted to a 2010 project otherwise Microsoft would have never spent so much time making the conversion wizard. The conversion wizard also mentions you should back up the files prior to conversion.
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)
Is Haskell for Visual Studio 2005 compatible with VS2008 SP1 ?
The answer to your original question is a No. The code for visual haskell is written in Haskell and talks via COM to visual studio. Now the problem is, that even if you update the com wrappers to be compatible with the new visual studios you'd still be stuck using a ghc 6.6 simply because it relied on internal structures of the compiler to work, some of which have already been removed from 6.8 going forward.
So any effort on this part will require a complete rewrite of plugin.
Now the good new is I am busy writing a version for visual studio 2010 (sorry no 2008) but supposedly I could release it as a standalone isolated shell for those who don't have vs 2010 (need to check the license more closely).
I only have time to work on it in the weekends, So I project (no promises) that I'll have a first version out around july.
I actually had just tried to install it from the link you provided (yesterday), but the installer complained that it couldn't find an existing installation of Visual Studio 2005. (I also have Visual Studio 2008 installed.) I'm guessing it's hard-coded to look for a specific directory or installed application version number? So... from what I've seen, I'd answer "no".
Hopefully someone else has had better luck?
I was told at a conference in 2007 that the Russian student who had been working on Visual Studio support for GHC never quite finished the job. The person most likely to know the true status is Simon Marlow at Microsoft Research.