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
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
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
Good day! I became interested in the tool from Microsoft vsimporter. There was such a problem: when I try to convert .xcodeproj project .sln project in the command line the message appears "The "project" workspace does not contain any schemes". All the schemes are in place. This problem occurs randomly, because It succeded to convert two projects, but with the other two the problem above. I can not understand because of what it happens. If anyone faced with an identical problem I will be glad to any hint!
The problem you're encountering is likely due to the presence of CocoaPods – was your Xcode workspace file generated by CocoaPods? The bridge currently does not support CocoaPods because of limitations in its clang compiler front end, but it's a request we get a lot so we're investigating adding support. Try removing CocoaPods and including your third-party libraries manually. If you run into issues, feel free to get in touch by filing an issue on Github – it's the best way to talk directly to our team. Thanks for checking out the bridge!
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 may have done something wrong because since the v9 I can't get resharper to suggest classes from different namespaces (different from the current one) if I don't type the using first.
But anything outside the project is ok. So it looks in imported dlls without any problem but won't look in the current project.
Any idea how I could have done that? (looked at the jetbrains forum and didn't see any similar issue so I assume it's not a bug)
Thank you