This might seem the very definition of a 1st World Problem but it's driving me nuts!
So the right-hand icon is my opened Visual Studio project, and to its left is the icon for Visual Studio 2022. In previous versions of Windows (10) and VS (2019) there was a single Visual Studio icon, which was either plain (no open VS projects) or decorated with a mark at the bottom to show that there was an open project. I'd like to return to that happy place but I can't figure out how. There is no property that I can find on the Taskbar nor in VS itself.
For me, this seems to be a Windows 11 bug. I have the same problem for another program than VS. After unpinning the old icon and pinning the new, the problem is solved for a few days until it occures again. Hope it will be fixed soon.
The answer (so far) seems to be, as #phuzi said, to unpin VS2022. I then closed the project and repinned VS 2022. There is now only one icon - result.
Related
I have a problem with Visual Studio 2019.
From what I have seen in tutorials, during publishing an application, I should be able to change profile settings, by clicking a small pencil (I included a screenshot, it's a little pencil next to "false" and other settings.) However, every time i click it, it opens FolderProfile.pubxml file in Visual Studio instead! Is this indended behaviour, am I doing something completely wrong? How to change that? Screenshot
My problem fixed when I updated visual studio.
Also go to extensions and update all.
Now show UI options.
I reecently updated my Unity editor from 5.1 to 5.4.f2f, and my IDEs started misbehaving. I use Visual Studio 2015 Community, and when I updated its Intellisense stopped recognizing all Unity terms. When I open scripts from the Inspector, VS opens nothing first, and open the script with broken Intellisense if I try and open it a second time. Monodevelop also cannot recognize any Unity terms. When I try and "Open C# Project," Visual Studio opens nothing.
The Unity editor also keeps on mentioning in the Inspector that GameObject scripts are missing too.
I'd really appreciate some help here guys. Keep in mind that I've also accidentally pressed the "Publish" button at the bottom of the VS window, but It was after the issue surfaced, so I'm not sure if it has any ties to this.
I think I solved the Problem.
It involved manually opening the Unity project in Explorer and opening the projects .sln file.
Apparently, this is a Windows OS flaw.
I got this answer from This link
I am having an issue within the razor view in Visual Studio 2012. For some reason, most of the time when I am trying to edit a style property, my keyboard freezes and doesn't allow me to type anything.
<section style="height: 15[Try to edit here]">
For instance, trying to add in a zero or 'px' where the "Try to edit here" has been placed above is impossible as the keyboard freezes.
I have ReSharper 7.1 installed, I'm not sure if that is the culprit?
Closing the tab and re-opening it fixes the issue, but it then re-occurs later on (not sure if there is a pattern as to when it re-occurs)
This happens to me often. I just switch tabs and come back and it doesn't happen(for sometime of course :-)). It could be some kind of unresolvable bug although i would suggest that you uninstall ReSharper and try again to see if it gets fixed.
It happens to me and my other colleagues as well.
I have found it to be linked to having a floating code window(s). Unlike the floating window for something like Find Results (without a title bar), these appear almost like another instance of Visual Studio. These do not come to the front when the main Visual Studio Window is selected. I have found the keyboard stops responding only on these windows if there is a Find Results kind of floating window open. When the problem occurs, clicking on another VS window and come back sorts it.
In earlier versions of VS, any pulled code windows appeared without a thick title bar and window controls box.
I tried posting images of the two kinds of floating windows but don't have enough reputation to do so! Let me know if it is confusing and I'll try to clarify.
This may not be the only way for this problem to occur but this is what I've observed consistently in the last few weeks of using Visual Studio 2012. I have C# environment settings with Resharper 7 and Reflector installed.
Picture says it all, it should currently be showing a file but as you can see its having issues drawing the content of the file.
I have unloaded all addons and restart visual studio.
If it mathers the previus project was a VS 2k8.
New Info:
If i wait a good 5min ( I have a Quad core I7 with 6gb ram, 295gtx. VS is running from a SSD).
It will load the text, but im unable to "edit", as it will have loaded some document (.cs ) but when i select the one i want to edit it not realy open that file.
It can best be described as visual studio having a 5min lag.
I had this precise bug. I would open files from the solution explorer but the editor window would either not appear, only 1-2 lines of 100+ line files would display, or the file would display but I could not scroll or otherwise edit the file. Some parts of VS were working, i.e. little tooltips would appear if I moused over the right part of the (invisible) text but I obviously couldn't do much in this state.
I have a lot of VS stuff installed so I thought it was some sort of plugin or extension that was causing things to go screwy. These installed items include:
Visual Studio 2010 10.0.30319.1
ReSharper 5.1.3000.12 (JetBrains)
DevExpress DXCore 10.1.5 (free community edition)
DX Source Outliner (reason for DXCore, from sbohlen)
Tabs Studio 2.0.6 (www.tabsstudio.com)
Productivity Power Tools 10.0.11019.3 (Microsoft)
Snippet Designer 1.3.0 (Matt Manela)
I solved it (2/18/2011) by Tools... Extension Manager... disabling the Productivity Power Tools and Snippet Designer. No idea what was going on but this fixed it for me and I was back to work. Probably something in the system drawing and/or display options.
EDIT
The issue continues. Unfortunately it is intermittent and I have not be able to reproduce it reliably. Now the suspects are the BugShooting and CaptureWiz screen capture tools. I've had the behavior show up and then disappear in and around the time of logging bugs with them.
2nd EDIT
The issue continually continues. I have not yet been able to determine the cause but usually quitting VS and restarting resolves the issue(s). Other parts of the behavior includes the menu options (File, Edit, View, etc.) not operating properly as they show only the highlight but not the actual menu items. The solution will build and run just fine, but things still won't show up properly.
I had a similar issue whereby VS2012 was telling me that I had active (open) files, but the text editor was not displaying them. Clicking on the file(s) in the solution explorer seemingly did nothing. Alt + Tab just cycled through the open files, but still, nothing rendered on screen.
I solved it by clicking on the "WINDOW" menu item and then"Close All Documents". Visual Studio then behaved as expected and opened (and rendered) the files correctly.
This bug was created by mumble 1.2.x, but is fixed in the snapshot versions of 1.3.x. YOu can likely get simular bugs by other software that does DirectX overlay.
I had the same issue in Visual Studio 2012. It was fixed by running a repair of Visual Studio 2012 via Add/ Remove Programs.
The following had no effect:
Closing and reopening a solution
Opening different file types
Restarting Visual Studio
Adding and removing plugins
Resetting options via the 'Reset all Settings' option in Visual Studio's 'Import and Export Settings'
Rebooting windows
I had this problem in Visual Studio 2013. Problem was: extension "Regex Tester". I had to uninstall this extension.
I have 3 versions of Visual Studio installed, and 3 projects that require a specific version. VSLauncher USED to look at the SLN or VCPROJ file and open the correct version of Visual Studio. Now it only starts the most recent version, regardless of the project.
Note that this has nothing to do with the commonly reported problem with beta versions of VS. none of the SLNs have ever been touched by a beta VS.
I had this same issue. VS 2008 solutions opening in VS2010 when double clicked. This problem went away after first going into VS 2008 and using 'Restore File Associations' then right clicking on a 2008 solution file and choosing open with and pointing it to Version Selector. Prior to this they invariably opened in 2010. Very frustrating. Hope this helps.
Tools | Options | Environment | (big button marked Restore File Associations
The problem was that the SLN files were subtly corrupted. Deleting the files and letting the appropriate version of VS recreate them resulted in a file that the diff tool thought was identical, but was exactly 3 bytes longer. I suspect the problem can be traced to a missing UTF-8 Byte Order Mark. Why VSLauncher is that picky is another question.
ADD: Yes, After opening the new file in a hex editor, I can say for certain that the problem was a missing BOM on the old file. This was tricky to spot because my diff tool apparently does not even see the BOM.
I also found, in Windows 7 Explorer, that I could right-click the sln, select Open with / Choose default program, then select Microsoft Visual Studio Version Selector - it would open with VS2008 (as was appropriate) and from then on, double-clicking the sln file would cause VS2008 to launch.
I had the same problem.
Visual studio could open normally the solution, but the version selector couldn't identify the version correctly.
In my case there was a problem with the EOL. Somehow the file was using unix EOL format, by changing it back to Windows format, the version selector started working again.
For Windows 10 and Visual Studios 2017 and 2019:
Click Windows Start Button
Start Typing 'Default app settings'
Choose "Default app settings'
Near the bottom of the page, click the link "Choose default apps by file type"
Find the extension ".sln" or ".vcproj", and select the default application.
Open your solution in the right Visual Studio version. Click your Solution to select it. Click File --> Save xxx.sln.