The results of the check error in my code using VisualStudio 2022 plugin Resharper version 2021.3.4 and Resharper in CLT 2021.3.4 are completely different. Used the same file .DotSettings
There are no bugs in the IDE VisualStudio 2022, but using the CLT there are over 2000.
I checked the results in TeamCity and they match with CLT.
Who have encountered, tell me how to solve the problem...
I had a very similar issue almost a year ago and contacted the JetBrains support. We had a very long back and forth, from which I took the following key aspects:
There are some existing issues, for example this one.
Make sure that no other settings layer (e.g. machine-wide config) comes into your way and overrides certain settings.
Enable solution-wide analyses (SWA), as it comes closer to what R# CLT does.
The whole picture becomes even more fuzzy when using Rider. For example, I had to enable File | Settings | Editor | Inspection Settings | " Enable computationally expensive inspections"
There are different results shown, depending on the used tool window.
Rider
SWA
Code → Inspect Code
VS
SWA
ReSharper → Inspect → Code Issues in Solution
So my key take-away was: it is super-hard to reach a 100% sync of VS and R# CLT, which gets even more complex when Rider comes into play. The almost inexhaustible number of options to configure R# makes it impossible to answer your general question.
What I can recommend: try to reduce the problem to a very small solution and get in contact to JetBrains.
Finally this was corrected in the new version of R# 2022.1.0 at JetBrains (using the Blazor component, files were created with the extension .razor, which R# checks did not take into VS)
That solved my problem
Related
There is some evidence in the Intellij codebase they support ALT(/Meta)+CTL - (mnemonic) in Mac.
E.g: in platform/platform-api/src/com/intellij/openapi/MnemonicWrapper.java
if (SystemInfo.isMac && Registry.is("ide.mac.alt.mnemonic.without.ctrl")) {
And the corresponding resource value in ./platform/util/resources/misc/registry.properties is set to true :
ide.mac.alt.mnemonic.without.ctrl=true
However pressing those two modifier keys together with .. say .. F (for File in the main menu) does not work for me on Sierra with the latest 2017.1 intellij.
Is this supposed to work? Is there any other way to get mnemonics working on Mac.
Note: please do not comment/respond "mnemonics are not encouraged/supported on mac". I am more than well aware of this terrible shortcoming on OS/X. However in previous versions of Intellij it has been possible to use mnemonics on Mac: and it would be a big boost to have them working again.
Update A YouTrack issue was requested by the Intellij Jetbrains support lead. It is here https://youtrack.jetbrains.com/issue/IDEA-175624
CTRL-ALT-(Mnemonic) DOES work.
The JetBrains lead Serge Baranov also mentioned that ALT-(Mnenomic) is supposed to work. It did not / does not for any of my laptops on 2017.X.
The Jetbrains support team led by Serge Baranov worked diligently on this - but were unable to reproduce. I expressed surprise since a half dozen installations on my side - all do not work. Apparently for their testing team it does work. One of my Mac's was factory new in June 2017 with Sierra and I installed IJ Ultimate 2017.1 without any changes from defaults. It did not work.
It is unclear what conditions were required for the Alt-Mnemonics to work on 2017.X.
* Another update* . Jetbrains has provided a fix for this: see last answer.
Make sure mnemonics are not disabled in IntelliJ IDEA settings:
By default mnemonics should work with Ctrl+Alt and Alt on Mac.
If you prefer only Ctrl+Alt, add -Dide.mac.alt.mnemonic.without.ctrl=false in Help | Edit Custom VM Options (Processes Alt-based shortcuts for mnemonics in addition to Ctrl+Alt-based shortcuts. Affect MacOS only.)
There is also a bug in IntelliJ IDEA 2017.1.x versions which causes mnemonics to work via Alt in dialogs, but not in the menu. Adding -Dide.mnemonic.helper.old=true in Help | Edit Custom VM Options will workaround this issue. The fix will be available in 2017.2.x.
Thanks to Serge Baranov of JetBrains : we now have a solution
Add the following to Custom VM Options
-Dide.mnemonic.helper.old=true
In addition a fix will be added to 2017.2
Just upgraded to Visual Studio 2015 and the Code Definition Window is not working.It just says "No definition selected" no matter what I select. Project is Windows Forms written in C#.
Go to Definition and Peek Definition are working fine
Went back to VS2013 to try it out and it's still working there
Tried to make a brand new project in VS2015 to see if it was project related, but it was not
Checked with a couple of colleagues and it wasn't working for them either
I have a feeling this is either a bug in VS2015 or some sort of configuration change.
Anyone found a way to configure it, or any sort of work around to get it up and running again?
I got a reply from Microsoft on my Bug report. Turns out it's not implemented and possibly never will be:
Hi,
Based on the fact that Peek Definition was introduced in VS2013,
combined with telemetry data that shows that only a tiny percentage of
users ever display the Code Definition Window, we decided not to
implement support for it as part of Roslyn. I've filed an issue on our
GitHub project to consider resurrecting it.
Thanks for the report!
-- Kevin Pilch-Bisson Visual Studio Managed Languages
Here´s the github issue Kevin created in response to my bug report in July: https://github.com/dotnet/roslyn/issues/4224
Looks like they just merged a fix for this into Roslyn:
https://github.com/dotnet/roslyn/pull/56102
I've had this problem for a long time. At some point IntelliSense just stopped working on my laptop, completely. Whenever I type in a ., -> or (, it says
IntelliSense: 'No additional information available' (See 'Troubleshooting IntelliSense in C++ Projects' for further help.)
It doesn't work in any projects, even if I make a new blank one. Hovering over identifiers doesn't show any information either. Furthermore, some actions such as go to definition used to completely freeze the studio, until I did a full settings reset and that problem was resolved. But intellisense is still not working. Is there anything I can do, short of full reinstall? (If that would even help.. besides I doubt I can find the CD now.)
Update: this question describes the exact issue I was having: VS2010 Intellisense problems
Since I already tried installing service packs and something didn't go right, I went with a rather hacky solution - I replaced my ole32.dll with an older version, which seems to have fixed the issue. This is obviously not recommended if you care about your system's stability, but if you're still running WinXP, chances are that you don't ;)
I have dyslexia and am starting my first collaborative project with other students using the IDE Visual Studio 2013. I fear that my miss spellings may cause errors and annoyance to the rest of the team, so I wish to keep my spelling mistakes to a minimum.
Projects on which I work alone are less of a problem, as if I spell the word wrong I tend to spell it wrong throughout the program in the same way - but I feel I would still get use out of a spell checker for these too.
I have had a google but only found a few plugins, most of which are outdated. Any help is much appreciated.
There is this one that has been updated recently: Visual Studio Spell Checker
You can just add it from VS by going to the Extensions.
Tools -> Extensions and Updates -> Online -> Search box -> Search for Spell Checker
I just tried it out, works well.
If you have ReSharper (highly recommended, but a bit pricey) then I can recommend ReSpeller. Costs only $10 and is completely integrated into ReSharper.
http://etherealcode.com/respeller/
At the same time, I can mention that ReSpeller (at least for the version I have, 2.3 for ReSharper 7.1) has one unfortunate quirk, but it is an option that can fortunately be turned off.
ReSpeller is unexpectedly accepting "prefered" as correct spelling
If you are using the Code Analysis/Fxcop rules built into visual studio you could add the following to your ruleset:
CA1703: Resource strings should be spelled correctly
CA1704: Identifiers should be spelled correctly
CA2204: Literals should be spelled correctly
You can try this too.
I am using this spell checker it is awesome. . .
https://visualstudiogallery.msdn.microsoft.com/7c8341f1-ebac-40c8-92c2-476db8d523ce
Another spell checker
https://visualstudiogallery.msdn.microsoft.com/F9CDA5D8-10AF-4CC6-9D17-207222A3FD13?SRC=VSIDE
I have two solutions within VS2012, one a branch of the other.
I have installed the latest version of resharper (8.0.2).
I open the same .cs file from both solutions.
On the one I get the warning triangle saying that I have unused directives, (which I do). On the other I get no warnings or errors. I have also noticed that the cleanup code feature within the one solution is disabled.
How can I enable this feature?
Try resetting your Resharper options back to their defaults.
Resharper -> Manage Options -> Reset all settings
If that fixes the problem then I guess you've turned something off along the way.