I've installed the Beta 1 of Visual Studio 2010, and started working a little. Even though I haven't been using CodeRush Xpress for long in Visual Studio 2008, I immediately started missing some of the neat functionality.
Is there any way to install CodeRush Xpress on Visual Studio 2010, even though it's only the Beta yet?
Now available at
Visual_Studio_Add-in_CodeRushX
I've listened to a couple of recent Mark Miller interviews and they are still working on the 2010 version. The current version will only work with 2005/8.
We are past November & still no VS2010 version, gosh, y did I get addicted to this thing
Related
I am currently using Visual Studio 2015 for programming ASP.NET Core applications. I have the following questions regarding installing Visual Studio 2017:
What is considered to be best practice and/or cleanest method?
Should I install Visual Studio 2017 beside Visual Studio 2015?
Should I first uninstall Visual Studio 2015 and all .NET Core dependencies and then install Visual Studio 2017?
Are there any tools that would ensure a clean uninstall of Visual Studio 2015?
From page Visual Studio 2017 Platform Targeting and Compatibility
Compatibility with Previous Releases Installation
You can install and use Visual Studio 2017 alongside previous versions of Visual Studio, including Visual Studio 2015, Visual Studio 2013, and Visua Studio 2012.
So yes. you can install them without any problem.
VS 2013, VS 2015, and VS 2017 all work well side-by-side. VS 2012 can be a little dodgy on Windows 10, but should also work side-by-side. In theory VS 2010 should also work side-by-side with those, but I've run into quirks in the past with them interfering with one-another.
Projects should round-trip between 2015 and 2017 generally, although there are some one-way upgrade scenarios.
Note that if you really just need the older compiler toolset for some reason, you can also install VS 2017 and select the optional component Microsoft.VisualStudio.Component.VC.140 which installs the older v140 compiler which you can still use with the VS 2017 IDE. That said, there's not a lot of reason to do this since the VS 2015 & VS 2017 C++ standard libraries are binary compatible so you can mix them in a project.
See this blog post for information on VS 2017.
It sounds like you have done some projects in 2015 already, so you will probably want to keep it.
Once you open a project in a new version, it will try to upgrade the project and then you can't go back.
However, if you have multiple versions installed at the same time, when you try to open a project, say, from Windows Explorer, it will open it with the "Visual Studio Version Checker" and will look at the project file and determine which version to open it in.
Bottom line, if you have the hard drive space, there is no reason to not install them alongside each other.
In the past, it was recommended to install them in sequential order if you are installing multiple versions, but it doesn't sound like this is an issue for you and I don't know if that is even a problem anymore as it has been several versions since I have had to deal with that.
Good luck!
Personally, I would keep both - there have been multiple times through the years where you have compatibility issues and NEED to have the prior version(s). I've also had old project that will not upgrade and I've gone back and reinstalled old VS versions.
If you have no reason to keep VS2015 in your computer I would suggest uninstalling it.
I uninstalled VS2015 after installing VS2017 and later noticing that I was still using an old taskbar shortcut to VS2015.
So I was inadvertently still using VS2015.
Maybe some special cases require keeping older versions of VS along side the new version, but for the rest of us, I say, uninstall!
VS 2015 is the last version that is supported by Installshield LE.
If you have a need for building installers in the future, it will be useful to have VS 2015
1,2,3. Visual Studio 2017 has more features over 2015 and it contains 2015's current features so you don't need 2015 alongside 2017. Just stick with 2017. And I don't think you will have any problems while opening 2013 and 2015 projects with Visual Studio 2017.
Uninstall Tool is a good tool to use. It cleanses all the leftover files and registry entries after running the original uninstallation wizard and even tells you how many files will be cleaned after the required reboot.
For people continuing to read this, I have Visual Studio Professional 2008 (For Windows Embedded 6.5), 2010, 2015, 2017 and they all work even if open at the same time.
Edit: As stated in other answers, they need to be installed from oldest version to newest.
Is it possible to make CodeRush Xpress (CodeRushXpress-11.2.13.exe) work with Visual Studio 2013 by some tweaks? I understand it is not supported for VS2013 but similar was case with VS2012 and it still worked with limited functionality. I am hoping to find some work around for this.
I cam across this question here on SE:
Can Visual Studio 2012 be installed side-by-side w/ Visual Studio 2010?
According to one comment with a good amount of upvotes, having 2010 and 2012 installed at the same time can present issues. I then came across this MSDN page about 2013:
http://msdn.microsoft.com/en-us/library/hh266747.aspx
If you use Visual Studio 2013 together with Visual Studio 2012 or Visual Studio 2010 SP1, you can [blah blah]
That suggests that 2013 can be safely installed along with VS2012. Can anyone confirm?
Take a look at Brian Harry´s Blog post announcing Visual Studio 2013.
VS 2013 can be installed side by side with previous versions of Visual Studio or, if you have a VS 2013 pre-release, it can be installed straight over top of the pre-release. TFS 2013 cannot be installed side by side but can also be installed over top of either a previous version (TFS 2012 or TFS 2010) or a pre-release.
Looks like you can, yes.
You can install this version of Visual Studio on a computer that
already has an earlier version installed.
http://msdn.microsoft.com/en-us/library/ms246609%28v=vs.120%29.aspx
Only issue I can see is during uninstallation, where the file associations may get lost.
I was having two installation on my computer. Really no problems.
From personal experience, I've come across multiple issues with using Visual Studio 2012 and prior, while a VS2013 installation exists on a machine.
Some of the issues include built executables failing to launch (double clicking .exe does nothing, but debugging them in VS launches them), and inability to compile solutions that mix C# and C++ projects.
I would avoid 2013 until these issues are resolved, as just having it installed on a machine breaks older code, even if you don't use VS2013.
There are some minor (compatibility) issues between using both VS2010 and VS2012 on the same Solution, but simply having VS2012 installed on your machine won't effect anything in VS2010.
There may be compatibility issues with 2013 Community edition. I had VS 2012 Ultimate and VS 2013 Express installed and working without any issue, but as soon as I installed VS 2013 Community, my VS 2012 Ultimate install has been behaving unusually. When I first open VS 2012 U, there is a really long load time. When I perform some action (open a file, select a menu option, anything actually) I have to minimize and maximize VS 2012 U for the screen to refresh. I am still trying to figure it out myself - so if anyone has a solution, please share.
A long while ago Scott Hanselman talked about PerfWatson. I've finally decided to install this extension in Visual Studio, but the extension no longer appears to be available for public-consumption (perform either a search or click on the appropriate link on the PerfWatson Monitor extension).
Is there an alternative to PerfWatson, or has it been completely phased out?
The PerfWatson extension is now available, and was updated on May 24th. The first paragraph says:
The Visual Studio team no longer collects PerfWatson reports for Visual Studio 2010. Your reports helped us to identify the issues affecting you most, and you can see improvements in Visual Studio 11 Beta. The PerfWatson extension is included in the VS11 Beta release. If you would like to use PerfWatson to automatically report on any responsiveness issues you are encountering, please download and try out the VS11 Beta.
Looks like it's no longer valuable.
Update July 2017
It appears that PerfWatson is available as a Visual Studio Extension for 2012, 2013, 2015, and 2017.
Paul Harrington appears to be a software engineer at Microsoft, but no idea if the extension's purpose remains the same.
I recently installed Visual Studio 2010 Premium at my work computer. I'm evaluating the installation of the VS2010 SP1 Beta to adjust many little problems that I've noted in using VS2010.
But I don't know if the SP1 Beta is rollbackable or if If'll have to reinstall all the VS2010 when the final SP1 will arrive to us.
Could anyone advise me about the opportunity to do this?
thanks a lot
rob
From Scott Hanselman's blog:
•If you install VS2010 SP1 beta, don't
uninstall it if you can avoid it.
Rather, wait for SP1 final which will
upgrade your beta cleanly and leave
you in the best state.
This is a copy from the readme file at http://go.microsoft.com/fwlink/?LinkId=207141 :
2.2. Uninstalling
2.2.1. On computers that have earlier versions of Visual Studio
2.2.1.1. Uninstalling Visual Studio 2010 SP1 Beta removes features in
Visual Studio Tools for Office and
Visual Studio Tools for SharePoint
Uninstalling Visual Studio 2010 SP1
Beta removes the Visual Studio Tools
for Office (VSTO) Design Time and some
features of Visual Studio Tools for
SharePoint. The Office and Sharepoint
features in Visual Studio 2010 SP1
Beta are major upgrades and have
different product guids than those in
the Visual Studio 2010 original
release. Therefore, when SP1 Beta is
removed, the features are removed, and
the Visual Studio 2010
original-release versions must be
reinstalled.
To resolve this issue:
In Windows Control Panel, click
Uninstall a program. In the list of
programs, right-click Microsoft Visual
Studio 2010 and then click
Uninstall/Change. In the Maintenance
Mode dialog box, click Next and then
click Add or Remove Features. Select
the following features. Microsoft
Office Developer Tools (x86) or (x64)
for Office development. Microsoft
SharePoint Developer Tools for
SharePoint development. Click Update.
2.2.1.2. Uninstalling Visual Studio 2010 SP1 Beta may not donwload all
required packages
When Visual Studio 2010 SP1 Beta is
uninstalled by using Add/Remove
Programs in the Control Panel, a
prompt for source may be displayed.
To avoid this, run setup.exe from the
original location, and uninstall by
using Setup Maintenence Mode.
To resolve this issue:
Navigate to the original installation
location for Visual Studio 2010 SP1
Beta . Run setup.exe. Select Remove.
Update
Regarding your comment below, yes, I installed VS 2010 SP1 Beta, here are the problems I got:
I couldn't install Visual Studio SDK - Fixed - I found there was newer version for VS2010SP1Beta that I didn't realize at first.
I could not install Phone Developer SDK - Fixed as unrelated - I contacted #ScottGU and they said this is test scenario, I downloaded again and it worked as a charm
Few issues about Resharper or so (can't remember exactly, but minor for sure) - Fixed - I just got a recent build of Resharper.
If this leads to the question "Should I install it?", I'd say, if you need any of the new features in it (see http://msdn.microsoft.com/en-us/library/gg442059.aspx for listing), then just install it. It's OK. If not, wait for RTM.
BTW,
If you want to discuss your specific SP1 issues instead of uninstall, no problem in that as well :)