I have installed Visual Studio 2015 Community Edition via Unity's installer and some of the options windows look like this:
Nothing fixes it; uninstalling-installing, formatting or installing on different machines. Apparently no one complains about this issue because there seems to be nothing on search results, but I'm 100% sure that everyone is experiencing this issue. When you open Visual Studio on its own, problem goes away, it works like it should. However, making Unity open Visual Studio causes it. I assume that this is caused by Unity forcing Visual Studio to load a plugin (probably Visual Studio Tools for Unity) which is actually incompatible with almost everything in Visual Studio.
Is there a solution to this problem? It drives me crazy and I don't want to use MonoDevelop.
In Visual Studio 2010 you can assign keyboard shortcuts for moving lines up and down.
I can't find these commands in 2012.
Have they been renamed or removed? Is there any way, out-of-the-box, to move lines using ALT + ↑↓? (I'm not buying ReSharper.)
This command is a part of Productivity Power Tools.
The 2012 version was released in November 2012. You can find it here:
Productivity Power Tools for Visual Studio 2012
Nothing happened to it, these commands don't exist in VS2010 either. Check what add-ins you've got installed.
Not sure what it does, but consider Edit.ScrollLineUp/Down. Default binding is Ctrl+Up/Down arrow.
I have Visual Studio 20010 Ultimate on Windows 2008 R2 machine. Last week I applied SP1 and after few days I am experiencing UI freeze for some time around 40 to 60 seconds when I save code changes to files.
I have turned off the background compilation, turned off the antivirus still this problem is not going away.
On my 2008 R2 machine I right clicked on the shorcut for VS2010 and selected properties option. In compatability tab I selected to run VS in compatability mode for Windows server 2008 SP1. There is a checkbox and dropdown for this.
For VS 2010 SP1 it is mentioned that it sets software rendering by default. I thought this might be the reason for UI freeze in some case hence I changed the compatibility setting and it seems to be working fine since then!
[With Visual Studio 2012] Try pressing ATL+TAB twice (or switch to another application then switch back to Visual Studio).
That seems to solve the problem.
For some reason, on a new computer, Visual Studio won't auto-close curled brackets.
if(Username.Text.Equals()) {
And it doesn't auto-close. Works perfectly on all other machines I've installed VS2010 on. And now it just won't.
And there doesn't seem to be a setting in the options menu to alter this behavior. What do I need to do?
I'm not sure if this is actually built in to vs2010. But you can install the MS Productivity Power Tools (Productivity Power Tools for Visual Studio 2012) Which will give you brace auto completion. this is quite a common add in so maybe the other copies of VS you have tried have it installed??
Visual Studio will auto-format matching pairs of brackets as you type, but I have never seen this on Visual Studio 'out of the box'.
According to this Microsoft Connect entry, it's officially not on VS2010, having been cut due to time priority issues vs time constraints.
However, add ons like the free Microsoft Productivity Power Tools, or the not-so-free JetBrains ReSharper will add this functionality for you. Perhaps you had one of these (or other similar) add-ons installed in the other computers you have previously worked on.
I have around 50 projects in Visual Studio 2005 that I am building a new development machine for and I'd like to slowly move those projects to VS 2008 but also have 2010 available for select new projects.
Can this work? Are there any gotchas for this sort of setup? Any general advice for running multiple versions of Visual Studio on the same system would be greatly appreciated. Specifically related to managing a controlled migration of projects to new versions but being able to selectively keep some on old versions.
I've got 7.1, 8, and 9 installed at the same time (well, and VB part of 6 as well) and I've not really had a problem opening projects file in the wrong version. The Visual Studio Solution files is "associated" with a particular version even if they all have the same extension of .sln, as you can see from its little icon. Microsoft Visual Studio Version Selector seems to handle individual project files (.vcproj) fine as well.
The only thing I've had is the individual source code files not opening up in the latest version like I want, but that's easily fixed with the click of a little button in VS Opions.
Microsoft have this to say:
Visual Studio supports the installation of Visual Studio .NET 2002, 2003, ... on the same computer.
In general, you should install the earliest release of Visual Studio first, and then install subsequent versions of Visual Studio in the order in which they were released.
Make sure when you open up the 2005 files you're doing it in 2005. To open them in another would require a conversion which would render them incompatible with the older compiler set-up. To aid this, structure whatever workspace you're using into 2005, 2008, and 2010 so as to minimize accidental chance of this.
Second, when you double click to open the projects, it will invariably attempt to open them with 2010. You'll have to start with VS#### instead of the solution/project unless you're in the 2010 workspace.
I have VC6, VB6, VS 2008, and VS2010 RC installed on Windows Vista. I cannot double click on the VC6 dsp files without VS2010 opening and asking to perform the conversion. The 2008 C# projects open in 2008 as long as I use the solution file. The 2008 project file opens in 2010 instead of 2008 even though the version selector is the default program. Most of the time I try to remember to open the desired version of Visual Studio and then open the project.
You can mitigate some of these issues by changing the default program associations in the control panel or the registry.
Update: This setup works on Windows 7 x64, with the addition of VS2013.
Yes it can work. I'm not sure if you have to install them in a particular order... but install them in order of the versions... 2005, 2008, 2010. Should be good to go.
I can't speak for 2010, but I have run 2005 and 2008 at the same time on my system without any fuss.
And I made the double-click mistake that wheaties warns about more than once :(
I have VS2005 & VS2008 running without any issues. I have had problems when working with betas, express editions & am assuming you don't have them.
I would say refrain from making too many changes to the setup of these editions, it should be fine.
I also had the same doubt. I work at my company which is still on VS 2008 and I want to personally use the VS 2010 and not risk the 2008. I installed the 2010 and it worked fine with the 2008. Just make sure you note the projects that are in 2005 and open them with the same accordingly.
The reason why it works is simple: if you open your solution file in Notepad, you'll see which version of VS is related to your project.