I've updated Visual Studio several times since release but occasionally it seems to act like it's creating a duplicate (as you would with a duplicate file/folder) and post-fixing a number to it e.g. Visual Studio Professional 2022 (3)
Anyone know how to fix or correct this? I've gone through the start menu, short cuts, etc. which also had the duplicate indicator but they were the only entries in their respective locations. I corrected the name which fixes it in Windows itself but the Installer still has the (3) in it.
Related
I'm trying to compare two versions of a VBA file which are placed on a TFS. The Diff Tool shows several changes, but there actually are none.
♪And they don't stop coming...
In fact, VS tries to beautify the code by changing it's case despite the fact that I turned the Pretty Listing feature off.
Example
Well, I've disabled literally EVERYTHING here
Note: VS does not change the files either on disk or TFS.
The question is how to make it stop. I can't find real changes when comparing files.
Microsoft Visual Studio Community 2019
Version 16.4.6
I am running Visual Studio 2017 on my laptop. I usually work on several different projects/solutions everyday, and there are one project and one solution "pinned" on the MRU list of start screen and file list (the Explorer one).
The problem is, they are both quite old (~2 months since last opened), and I have never pinned them. They just stuck there. So now when I open Visual Studio, the third item is actually the real most recently used one.
I tried to remove the two entries from start screen and file list, they would just automatically pop up the next time I launch Visual Studio. I also tried to stop synchronizing settings via cloud, but it does not help (so it seems like a local issue). I cannot stand it anymore. I did not encounter this problem in previous versions.
What is the possible cause? Is this a bug that I should report to Microsoft (well, it may be recognized as an unimportant one though)? And how can it be solved?
I've encountered the same issue under VS2017 and after few attempts I figured out a solution that may fix your problem.
First of all, after having closed all VS instances, delete the hex keys in your system registry that contains the path of your undesired projects.
In order to do that I've exported all the keys in a backup file, then searched for the occurences with a text editor.
Just for reference, in my case the path was:
Computer\HKEY_USERS\S-1-5-21-2840329424-3192507804-1387616012-2346\Software\Microsoft\Windows\CurrentVersion\Search\RecentApps{0D6B9660-F302-4C2A-82E4-FF89D03814E0}\RecentItems{AC7C50DF-34F3-4DA3-A6ED-45A6CF489220}
Then you have to remove from "ApplicationPrivateSettings.xml" file, the occurences of your projects that you want to remove.
The file is located here:
C:\Users{Username}\AppData\Local\Microsoft\VisualStudio\15.0_0dae6c36
At last, update your visual studio to the latest version with all those tricks done. You shouldn't see all your annoying projects anymore.
Every time I open a solution visual studio creates an extra folder "Visual Studio 2013" in the root directory of the solution.
How do I stop this from happening?
I've had this happen too a couple times (for me, it was because the VS settings etc. were all stored on a network drive that went down while VS was running, which messed up the config).
You'll need to:
Close all instances of Visual Studio
Open Visual Studio. In the options pages, go to Environment->Import and Export Settings and make sure the path there is correct. It should look something like c:\users\[user]\Documents\Visual Studio 2013\Settings\CurrentSettings.vssettings. Do the same for the three paths in Projects and Solutions->General. Save the options.
Close VS, and repeat step 2 if necessary (now that the settings are being saved in the appropriate location).
With VS closed, look in the registry at the immediate values under the key HKCU\Software\Microsoft\VisualStudio\12.0 for any other file paths that still aren't correct (they should all be full paths), and fix them. Be careful not to remove trailing slashes where present, they matter.
Some of these steps may not be completely necessary, or may need to be repeated (I'm not entirely sure which since I didn't have the time to debug this thoroughly the last time it happened -- I just brute-force fixed all the broken paths I found until it worked). This should be enough to get you on the right track, however.
You can safely delete the spurious Visual Studio 2013 folders that got created.
I have VS 2008, 2010, and 2012 installed.
Initially, VS2013 Team Explorer was installed (Shell only). I uninstalled that.
Now, the Visual Studio Version Selector shows an empty list when executing a .sln file. Nothing shows.
How can I repopulate this list? Where is it stored? Registry? I tried to find entries, but since it doesn't actually have any items in the list, I couldn't search for a specific string.
I just encountered the same issue after installing Visual Studio 2015 parallel to an existing 2013 installation. In my case it turned out that that the problem was related to the solution file itself: It seems that the version selector does not like BOMs etc. (don't know how the solution got crippled, though). Make sure that the solution starts with
Microsoft Visual Studio Solution File, Format Version 12.00
and has no space, non-printable character etc. before that. After saving the file, the effect should be immediately visible with the correct icon returning.
I just ran into a similar problem where this dialog started popping up after a recent Windows Update (Win10) on 1/6/2018. That update caused all sorts of havoc in terms of broken file associations.
I tried searching for solutions and trying a few things but everything was overly complicated and messy.
My solution was to run the Visual Studio (2013) repair.
After the repair, I did receive a warning (from vs installer) about update 3 failing to update but I restarted the computer and sln files can now open without needing that version dialog. Everything seems to be compiling and running fine as well.
Just ran into this situation for VS2017 then I realized I have unfinished updates for Visual Studio when checking Visual Studio Installer.
The installer displayed a hint that I should restart my computer to complete the update and after doing so, the version selector works again.
For a couple of weeks now I have been unable to merge Views within Visual Studio 2013 in response to conflicts when getting Source Code from Visual Studio Team Services. I am sure I used to be able to this (we recently moved from Visual Studio Professional 2012 so I cannot be one hundred percent certain - automerging may have been sufficient in the early days of the project).
The "Accept Merge" and move to next change/conflict buttons are all greyed out and inoperable. See screenshot snippet-
This originally only happened with Views, but now seems to affect some other classes. Changes are highlighted and indicated on the scroll bar so the diff tool otherwise appears to be functioning. This only originally affected me, but now affects a new colleague into the team.
I can still either Keep Local Version or Take Server Version but this is rarely sufficient. This leaves me manually altering the local copy to apply changes highlighted by the merge tool. (Edit - See a better workaround in "Second Update" below).
Has anyone come across this before?
Visual Studio 2013 Premium (patch RTM/Update 1/Update 2 - all with the same problem), with Resharper 8.2 (originally 8.0.2) C# and Web Essentials installed. Running on Windows 7 Professional x64.
Project is ASP.NET 4.5 using MVC 5.1.2 (now additionally updated from MVC 5 where the problem first occurred) (upgraded from MVC 4 following the upgrade instructions on the ASP.NET website) in C#, using latest versions of Razor (3.1.2) and Entity Framework (6.1.0 RTM).
Edit: Initially a repair install of Visual Studio 2013 appeared to have fixed the issue. It has now however returned exactly as it was before. Since it took an hour to do the repair I cannot repeatedly do this in order to merge views. I am currently able to round trip the solution between Visual Studio 2012 Update 4 and Visual Studio 2013 in order to do merges in Visual Studio 2012 where it is working normally.
Second Edit: I am currently manually resolving conflicts by selecting the desired code (local/server), saving the merge window and then closing it which will prompt to accept the merge result. This seems to function but is obviously sub-optimal. It may however be helpful for other users.
In the event, installing Resharper 8.1 on top of 8.02 appears to have fixed it fixed it briefly before the problem returned yet again. I had previously completed a repair install of Visual Studio Premium 2013 as well - which briefly seemed to have fixed it before it broke again. I only mention it in case the fix is cumulative.
I am unclear if it was a bug in Resharper that was somehow preventing the merge, or a persistent problem with the installation that the upgrade cleaned up (Resharper removes previous versions and then installs updates, rather than attempting to install over the top). Update - I am extremely confident that this is not related to ReSharper and that it was the configuration of Visual Studio as a result of re-installing the extension and not the extension itself that fixed the issue.
In either case, the issue (for now) seems to have disappeared and this seems to be related to the upgrade, or is an extremely strong co-incidence.
Colleagues with the same versions of Visual Studio and Resharper, working on the same project, the same version of Windows and (in one case) the same hardware were not affected, so it seems likely it is an edge case niche issue caused by corrupted data somewhere.
I have a current working theory that this is related to different patch versions of Visual Studio (for example Visual Studio 2012 Update 2, Visual Studio 2013 RTM, Visual Studio 2013 Update 1, Visual Studio 2013 Update 2. This only affects Visual Studio 2013 for us.
Simple solution I use is carry on with your manual merge process once you are done simply Close the Merge-* tab (the one you are using to merge files) this will bring up a prompt for confirming if you want to Save the changes made (this is the merge changes you made to your local file) click 'yes' Now it comes back to Resolve Conflicts tab and brings up another prompt asking if you want to Accept Merge Result, click 'yes'(this is same as the button Accept Merge)
Since you have VS2012 installed and merge is working there, you can create a link to its TF.exe in VS2013, similar to one on the picture below, and fix the issues there. Set Command to c:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe and Arguments to resolve.
You do that in Tools->External Tools.