I've recently installed the Fira Code font for Visual Studio 2019, version 16.6.3
The issue that I have is that after I shut down my computer, the font won't load properly unless I close VS and re-install it (and, when I do that, Windows also tells me that the font is already installed and I have to confirm that I want to overwrite it) in order to get it to load properly.
The confusing thing about this issue is that even when the font doesn't load correctly (it loads the default font instead) it stil appears to be properly selected in Tools > Options > Environment > Fonts And Colors.
I solved it by installing the font for all the users, which can be achieved by simply left clicking the .ttf file and selecting the "Install for all users" option.
Related
I found this question that is about enabling ligatures in Visual Studio, which appears to be automatic.
However, I don't like ligatures, so I was wondering if it is possible to disable them. I can't find anything in VS2017 or VS2019.
I also want to disable font ligatures in VS2017 today, then I found this link in MSDN community site. They say:
Currently, Visual Studio doesn’t have the ability to disable font ligatures in the editor, so the only option you currently have available is to chose a font that doesn’t provide ligatures.
I think they are foolish about this.
I ran into that issue in VS2022 aswell when tried to install Jetbrains Mono font. But it occured that jetbrains provides same font without ligatures, it's name is followed by 'NL'
Some time ago Microsoft created "Cascadia Mono" font, which is the same font as default in Visual Studio, but without ligatures.
You can download "Cascadia Mono" font from here:
https://github.com/microsoft/cascadia-code/releases
Install this font on your machine, restart Visual Studio, select "Cascadia Mono" font, and you will achieve the same result as "disabling" ligatures in VS.
In Visual Studio 2017, is it possible to change the UI font size for the IDE Error List tool window only, i.e., without affecting any other settings?
Having said this, I can't even find any setting in Tools > Options > Environment > Fonts and Colors that affects the Error List at all, even after restarting Visual Studio as suggested.
It is done by changing the Environment Font. It changes the menu font too.
Tools->Options->Fonts and Colors->Environment
I have the same issue and couldn't resolve in Visual Studio (the font size updates in other areas of VS, but the error list stays the same).
I only needed a bigger font for a presentation so used the magnifier tool in Windows. Not something you want to use all the time, but great for a short-term need
Unfortunately, Visual Studio (2022 and most likely older) does not allow to change the font of the error list independently from the rest of the environment.
Somebody asked for the default font of the environment. The default font is "Segoe UI" with font size 9.
I installed (as MS recommend) a font and tried to assign it into 'Options/Environment/Fonts and Colors' but doesn't work.
Lucida Console font applied:
InputMonoCondensed font applied:
Restarted Visual Studio and my computer without success, what could be wrong?
Notes:
OS: Windows 10 Pro
VS: Community 2015 v14 Update 3
.NET Framework: v4.6
All were installed and updated into a new computer.
This is actually a known issue documented on Input download website http://input.fontbureau.com/workarounds/
Here is the relevant part:
In certain configurations of Visual Studio (2010–2013), the default Input installation will not display at all, and instead you’ll see Courier. A workaround is to customize and download a four-style family (which will appear in your font menu as “Input”), rather than selecting from the whole family. Some users reported that they had to reboot their system for the change to take effect.
Solution is mentioned, on the download page http://input.fontbureau.com/download/ chose "Customize your download" option and select "Download a custom four-style family", based on InputMonoCondensed.
Install this font after downloading, and select the font named Input (just Input, not InputMono or InputMonoCondensed for instance) into Visual Studio options:
That's it!
Now you can edit using Input font, that's actually what I personally use.
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 export my settings in Visual Studio and if I ever move to a new machine or have problems, I use those backed up settings to restore Visual Studio to the way I like it. It also allows me to maintain a consistent development environment between the various machines that I use.
This works great for keybindings, syntax highlighting, user tools, pretty much everything except for the toolbar locations and customizations. Whenever I move to a new machine and restore the settings, the toolbars are not affected. I have spent a fair amount of time setting up toolbars with my macros, external tools, etc and cut'n'pasted icons in for them. I hate losing all that work.
Does anybody know how to back up and restore the toolbars' locations and customizations? If it is not a feature of Visual Studio, is there an addin that will do the job?
Edit
As mentioned below, the Menu and Command Bar Customizations in Import and Export Settings is supposed to do this, but when I re-import my previous settings, I get
Error 1: Menu and Command Bar Customizations: The version of command bar settings being imported is not supported. All the command bar settings have been ignored.
The settings I am trying to re-import were exported earlier this month with the same version of Visual Studio. The only difference is that I am now running 64 bit as opposed to x86. I didn't think that would make a difference though since the settings files are XML.
Any ideas?
I have finally found the solution to this. There is a known bug in Visual Studio and there are two workarounds given. The first workaround does not apply, but the second worked.
To Backup your toolbars:
Copy the file CmdUI.PRF from the path %AppData%\Microsoft\VisualStudio\X.Y\1033 to the same directory as your exported .settings file.
where X.Y is either of 8.0, 9.0, 10.0 or 11.0 depending on your visual studio version (2005, 2008, 2010 and 2012 respectively).
To Restore your toolbars:
Make sure Visual Studio is closed and copy the backed up file back to the original location.
For the benefit of others, as you mentioned this feature doesn't seem to be supported across versions of Visual Studio, presumably because of a change in the DTD/XSD for the settings file? At any rate, here's where the settings for your custom toolbars lie in the "Import and Export Settings..." dialog:
Note: Your options may look different, depending on the settings you exported.
I have not tried it, but "Tools\Import and Export Settings..." maybe will let you export a .vssettings file you can then take to another box.
See also
http://blogs.msdn.com/saraford/archive/2005/04/19/409887.aspx
and other Sara 'export' tips.