I upgraded Visual Studio for Mac 2017 to 2019 yesterday, and immediately noticed that the Subpixel rendering is switched off inside the text editor! It looks terrible.
I'm running OS X Mojave where I, after having upgraded it, explicitly turned subpixel rendering on again for the entire system using a guide I found on the net. So everything else than the VS for Mac 2019 text editor windows themselves is using subpixel rendering.
What's going on, and how do I turn it back on? I have searched the net for an hour now and found no clue or hack.
Related
I have a very odd problem where I will apply a recommended change that uses a C# 8.0 language feature (in this example I'll use compound assignment). I then get a red squiggly with the following message...
C# 8.0 language feature
This is a net5.0 project I have tried setting my language version property to any of the following...
<LangVersion>9</LangVersion>
<LangVersion>9.0</LangVersion>
<LangVersion>latest</LangVersion>
All of them show the same behaviour. The only way I can get the error to go away is by setting the property to 8 or 8.0 which seems a somewhat retrograde step!
I'm using Visual Studio 2019 and I'm fully patched and up to date as of the time of writing, along with the latest version of ReSharper.
The code will compile without problems but the squiggles are generating noise. Has anyone else found this and has any ideas how to make it go away?
This looks like it was a ReSharper issue - JetBrains have introduced a new tool called Jetbrains Toolbox that seems to manage their updates now. My installed package was telling me it was up to date when it wasn't - I looked deeper and I was running ReSharper 2019.1 and not 2021.1
Visual Studio 2019 Community 16.8.4 crashes when drag and drop Document Tab.
I have re-installed VS 2019 Community and it does not fix the problem. I have been using 2019 Community for a year now with no problem. Not sure if it is related to 16.8.4 or not.
Has anyone else had this problem? If so have you figured out how to fix it?
[Workaround]
Edit %InstallRoot%\Common7\IDE\devenv.exe.config and %LocalAppData%\Microsoft\VisualStudio\16.0_xxx\devenv.exe.config and append the following text to the AppContextSwitchOverrides element’s value attribute:
;Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true;Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true
After restarting VS, you should be able to drag your VS windows around without crashing.
https://developercommunity2.visualstudio.com/t/Unexpected-VS-crash-when-docking-or-spli/1323017#T-N1330689
Indeed fixed in 16.8.5 as specified here: https://developercommunity2.visualstudio.com/t/Unexpected-VS-crash-when-docking-or-spli/1323017
It's just started doing it today, been fine on this version up to this point. It only seems to be the docking so I have Visual Studio on the left hand side of the screen then I'm floating editor windows on the right. Seems to be OK like that.
I have VS2015 and the updates that are supposedly causing the crash weren't installed. Instead I got KB5001028 and KB4601056 installed on the 15th and docking any windows in Visual Studio crashed immediately. Removing those updates fixed the crashing partially. Now I'll get random crashes when docking and immediately switching windows, but not always.
Updating visual studio 2017 to its latest minor version, fixed issue for me.
For those who can't find a solution shall try this.
For me, none of the solutions worked. I've updated to latest version and even tried all windows updates recommended.
Finally I figured it out that it was due to eXtra Buttons application. Once the eXtra Buttons is closed, everything was back to normal. Please share if this fix works.
I installed the final Version of Visual Studio 2019. I read that is has this new feature to work correctly on a system with different DPI screens.
The Requirements are "Windows 10, 1803" (I have 1809) and .NET Framework 4.8 (installed the current Preview).
The Option in Visual Studio 2019 is still grayed out.
I have no clue why. - Has anyone else succeeded in activating this setting?
from https://developercommunity.visualstudio.com/comments/578963/view.html
I found what caused the issue. It was a registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\devenv.exe]
"dpiAwareness"=dword:00000001
After I deleted it everything works as it should.
Worked on my machine.
The Registry key may have been installed when I re-installed VS2017 after VS2019 lapsed into CPUholism
The final version of .NET Framework 4.8 was released on April 18, 2019. I installed it today, and this option now works in Visual Studio 2019. Upgrade from the preview and you should be good to go: https://dotnet.microsoft.com/download
Another reason why Visual Studio has the option grayed out is that the Visual Studio is run by clicking *.sln file in an app having HIGHDPIAWARE flag set.
The flag is usually set by right clicking the app -> Compatibility -> Change high DPI settings -> Override high DPI scaling behavior. Scaling performed by Application. It will add ~ HIGHDPIAWARE string for the app path to:
Computer\HKEY_USERS\S-1-5-21-786552173-3883971264-3181160094-1001\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
The flag can be removed by UI or deleting the key by regedit.exe from the above registry path.
If you click the *.sln file in a file manager app which has the flag set, Visual Studio Optimize rendering will be disabled.
So just ensure all the parent processes of Visual Studio have the flag disabled.
https://learn.microsoft.com/en-us/visualstudio/ide/reference/general-environment-options-dialog-box?view=vs-2019
As stated in the tip dialog box, windows has a setting "Let Windows try to fix apps so they're not blurry". Turning that off and restarting Visual Studio 2019 fixed this.
Note that I have all the minimum requirements
Since its installation, the android designer is not rendering properly because of which I have problems designing the UI. This is the screenshot that says it all.
I have repaired the installation and also uninstalled and the reinstalled the VS2017 but still it is not showing up correctly.
Check for updates and install, I dont have that problem with VS 2017 enterprise
I cannot see the story board in Visual Studio 2013, when I open it it tells me
There was a problem rendering this document.
Also in the errors list I have the following:
The clocks on the Build Host and this Machine are out of Sync. Please make sure they are within 3 minutes (UTC) of each other.
Failed to retrieve SDK status from server Xamarin.iOS Extension.
Also the output from the MAC server log tells me:
Error sending iOS designer payload
What can be wrong here?
I was also having a similar problem where I couldn't open the story board in Visual Studio 2012 or 2013 (I didn't have any errors in my error list, just the error when displaying the designer). My setup is dev work in Windows 7 with Visual Studio 2012/2013 with a Mac acting as a Build Host. I had just updated my Xamarin version from 3.0.54 to version 3.3.47 (it had been a little while) and I had created a little prototype app a couple days ago with no problems, so I figured I had killed something with the update.
In my case, the solution was checking for updates in Xamarin Studio on the Mac, where it found several that needed updated. After installing the updates on the Mac side, I was able to display my story board in both Visual Studio 2012/2013 without issues... so I chalked it up to version mismatch issues between the Build Host and my dev environment in Windows.