a couple of days ago I updated my VS to Microsoft Visual Studio Enterprise 2019 Version 16.8.3 (+resharper 2020.3 version)
And I catch the next case: VS begins to add spaces for an empty line (on the enter keyboard press).
[edit]: This is a ReSharper option. As mentioned by Piers Myers in the comments.
But before it adds spaces only after I write something in a new line:
Maybe somebody resolves this?
This is a ReSharper bug and they are working on it. I will edit this answer when they will release a fix.
[Edit]: The fix will be available in 2020.3.1 version of resharper.
Link to the issue: RSRP-482555
Related
I've got a problem with Visual Studio Enterprise 2019, it hangs on "Execute Suggested Action" when I use it to add a reference to another project or library.
It's a Visual Studio bug. They are working on it.
Take a look here: https://developercommunity2.visualstudio.com/t/Infinite-suggested-action-never-ends/1223055
The fix will be probably released on the next release (16.9).
UPDATE:
Still in vs 16.8.4 but should be solved in 16.9.
UPDATE 2:
In 16.9 PREVIEW 3, this issue seems to be resolved.
UPDATE 3:
Fix has been released! You can download the new version of VS now.
if anyone struggle with adding references: go to your project -> right click on Dependencies -> select eg Add Project Reference -> look for proper reference
I was having the same issue when adding on the suggestion of Intellisense. For me, it turned out to be an issue of cyclic reference. My bad. I corrected it and now it doesn't hang.
It was VS 2019 community, Windows Forms (C#)
I recently upgraded to Visual Studio Enterprise 2019 (version 16.0.3) and I have been having serious problems with autocomplete. It is so slow that I type faster than it is able to update, and frequently after I type out a complete and correct language keyword such as foreach the autocomplete drop down won't appear until moments before I press space which in many cases causes the keyword foreach to be corrected to some nonsense without warning.
This hasn't been a problem for me with any other version of Visual Studio going back to Visual Studio 97, and it is driving me nuts. I have no addons installed.
Is anyone else having this problem, and if so, what if anything were you able to do to resolve it?
You should open window defender then add exclusion folder for visual studio 2019.
I also add my folder source code.
Hope this help to who need
Hello I found that checking out this checkbox speeds ups VisualStudio InteliSence a lot...enter image description here
Upgrading to 16.1.4 seems to have resolved the problem.
I just started using TypeScript, and was using the TypeScript Playground here: https://www.typescriptlang.org/play/index.html
It has decent intellisense, and autocompletes on enter, as well as auto-completes parenthesis and brackets.
However, once I decided to use it in VS 2015, I noticed that enter no longer selects the suggested dropdown, and neither parenthesis nor brackets are auto-added. When programming in C#, these features work out great.
How do I enable this behavior in Visual Studio? I would assume that if it exists on the website, it would definitely exist in a full blown IDE like VS.
Can I enable similar refactoring features to C#, like automatic variable/property renaming across the project if I change a variable name? Using Ctrl-R Ctrl-R to rename a variable doesn't seem to work, it only changes the line I'm on.
Edit:
VS 2015 Update 3
Typescript for VS 2015 v 1.8.6.0
Typescript for VS 2015 v 2.0
Edit2: Upgraded to the TS 2.0 VS plugin. The Automatic Brace Completion checkbox is no longer greyed out, yet enabling it does not seem to have an effect on brace completion.
Edit3: These features are in Visual Studio Code.
TypeScript 2.0.2 RC for Visual Studio 2015 — August 30, 2016 fixed this issue. You can download here.
Click Details to see list of all the versions.
Make sure you have the latest TypeScript VS extension installed.
I recently installed the Update 2. So now when I put a breakpoint it just puts a red dot on the left side of the file, but it doesn't highlight the entire line. I am not sure if Update 2 changed the settings, but I thought so.
I tried this: in Tools>Options>Debugger>General>Highlight entire source line for breakpoints and current statement (C++ only). So it tells that this doesn't work for C#. What should I do to highlight the entire line?
UPDATE:
I had the same problem and it went away by closing VS 2013 and delete / rename following registry keywords:
12.0_Config
12.0
in
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\
when restarting Visual Studio, the config settings dialog appeared and I selected not to import settings from previous version.
Breakpoints and current line while debugging were normal again :)
I had the same problem on visual studio 2012 and by following the instruction by McNos, I was able to resolve the problem.
In my case, I renamed the registry node 11.0 to 11.0-OLD and 11.0_Config to 11.0-Config-OLD under
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\
Restarted visual studio and it popped the config settings dialog...
Thanks McNos
I could not find the configuration for VS2019. Then I searched a bit more and found that this command fixes the issue:
devenv.exe /updateconfiguration
Reference:
https://developercommunity.visualstudio.com/t/debug-no-longer-highlights-current-line-yellow-lin/25156
Note: the problem started to happen after installing the lastest VS update.
I have got the following problem with F# code recently: almost the complete code is underlines with curly red lines (indicating problems) and whenever I hover with the mouse cursor over any word the pop-up appears with the message "Unexpected token". IntelliSence doesn't work either.
Nonetheless if I start the project it is executed without any problem.
This happens both to already existing F# files and to newly created F# projects. I remember it was working just 2-3 months ago!
I tried to deactivate all possible extensions but it doesn't help.
Any ideas?
I get this too. Sometimes, simply exiting and going back into VS helps. When I tweeted the problem, Don answered with this:
"do you have "python tools for visual studio alpha" installed? if so, uninstall it or apply the hot fix"
This wasn't relevant to me (as I haven't been anywhere near python) but I'm posting here in case it helps you.
-- Edit: here's a link to the patch, thanks to Alexander Galkin: http://pytools.codeplex.com/workitem/599
I haven't seen this situation before but here's a guess at why it's happening and how you might cure it.
Visual studio works on a system for plugins. Even the stuff that is "native", like the C#/F#/VB.NET project systems, are just plugins that uses the visual studio shell. It looks like the F# plugin has been damaged in someway.
If this is Visual Studio 2010:
You might try opening the visual studio installer and trying a repair installation or deactivation and reactivating the F# project system
If this is Visual Studio 2008:
You might try uninstalling and reinstalling the F# plugin