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.
Related
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
Is everything from VS Code insiders, eventually going to be added to normal VS code? Is there a feature, where you can take features from insiders, and put it in normal VS code? I wanted to see if I should just go to VS code insiders for the extra features. Should I?
I say that you shouldn't use insiders in a corporate environment as it still a kind of "beta" software, but if you're just having some fun, go for it. As for the features, most of them will eventually come to the stable release, but not all of them. I don't know of any way to "take" features from insider and put them on stable unless you want to go on GitHub and manually merge the branch and compile it.
Also, if you want to go for the features, I say you read the changelog of the insiders first.
After a recent update on VS2017. I'm seeing lots of Late binding errors on all projects.
The errors are showing because Option Script of set to on somewhere, but all my projects have the option Option Strict set to Off.
On some projects even if I set Option Strict to Off in the page code behind, I still get the error.
Sometimes if I try to reference Microsoft Visual Basic in the project, the errors go away, sometimes not.
Anyone else experiencing this problem? Any ideas how to fix?
seems to be fixed in Rel. 15.5.2!
pLease have a look at
https://developercommunity.visualstudio.com/content/problem/160609/vb-option-strict-on-warnings-are-shown-on-existing.html
So MS is already aware of the bug and proposes another workaround.
I'm facing the same problem. The workaround I found is:
1. Turn option strict ON
2. Compile your project (will not succeed due to option strict on)
3. Turn option strict OFF
4. Compile your project (compilation success and no more errors)
This problem has now been Fixed in release 15.5.2.
You might have to save a project with Option Strict On then save with Option Strict Off. I didn't have to do that.
Source :https://developercommunity.visualstudio.com/content/problem/160609/vb-option-strict-on-warnings-are-shown-on-existing.html
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 ;)
We have an issue with ReSharper (7/VS2010): when you use it to add a reference from one project to another in the same solution sometimes it will add a binary reference to the output of the referenced project instead of a project refs. Can this behavior be disabled, ideally so that it only adds project refs but failing that disable adding refs altogether?
This bug became known to JetBrains not longer after the original question was posed (see it here). It says it is fixed in ReSharper 8.0.14+. JetBrains is sometimes a little over-enthusiastic about declaring bugs to be closed; however there's a similar bug (see the list in the link above) that's supposedly fixed in R# 8.2, so there's a good chance this is no longer an issue with that version.
This is definitely a bug in ReSharper and you need to open an issue for them as #wal has pointed out here: http://devnet.jetbrains.net/community/resharper