Tons of false positive errors reported

I just installed the beta build (2162).  I was previously using the latest stable version (5.1.3?).  I immediately notice that I get a bunch of errors and warnings for things that are perfectly valid.  Upon first glance it looks like these issues only occur when using objects that are in referenced assemblies (not projects in the solution).  For example, referencing log4net.dll and calling LogManager.GetLogger(typeof(MyClass)) produces an ambiguous invocation error.  The GetLogger method is overloaded and you can provide either a string or a Type object so my usage is perfectly valid.  I also have another library that I reference and objects that I get from its API causes a "Local variable 'xyz' is never used" warning even though I am using it (oddly, the quick fix option offers to move to outer scope rather than just remove the variable).  This behavior seems very much broken.  Am I doing something wrong here?  Do I need to delete my ReSharper settings or something?  It is completely unusable in this state.

2 comments

Hi,

we have fixed this. Please download the latest nightly build and let me
know if it helps you ASAP.
Thank you.
--
--
Kirill Falk
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Looks like you fixed it in 2163, thanks that was quick.  :)

I just noticed a very minor typo bug in this build (figured I would just post it here rather than in a new thread).  I get a warning for a redundant comma in an array initializer: "Redundant comma in array iitializer" (notice the missing n in initializer).  It is spelled correctly in the Inspection Severity options.

Thanks again.

0

Please sign in to leave a comment.