R# reporting false compile errors in VB.net

So I entered a bug in the bug tracker almost a year and a half ago for resharper reporting compile errors that are not compile errors. The code still builds and runs just fine, but I have all these red errors all over my code from resharper.

The issue is when your base class adds 2 overloads to a method and then a derived class adds another overload and an overrides one of the overloads in the base class, then whenever you attempt to call the original method that is defined in the base class on an instance of the derived class R# can't seem to find the definition for that method and it reports a compile error even though that method totally exists and everything builds just fine. You can see the bug for steps to recreate and an attached project to reproduce the issue: http://youtrack.jetbrains.com/issue/RSRP-354217

I reported this almost a year and half ago and it's still an issue. It only occures in VB, not in C#, but the company I work for uses exclusively VB. Who knows when it will be fixed. Is there any kind of work-around to suppress the "error"?

3 comments
Comment actions Permalink

I found this page that describes how to ignore certain warnings/errors: http://www.jetbrains.com/resharper/webhelp/Code_Analysis__Solution-Wide_Analysis__Configuring_Solution-Wide_Analysis.html

My trial of R# has expired so I can't try this. Can anyone confirm or deny that this particular error can be ignored following this method? If it works I am prepared to purchase R# today. This really is the one and only thing holding me back at this point. I can't live with bogus errors all over my code.

0
Comment actions Permalink

Hello Nick,

  Please submit a request here http://resharper-support.jetbrains.com and I will provide you an evaluation extension.

Thanks!

0
Comment actions Permalink

This removes the error from the Error List window, but it keeps the red underline on the code that calls ToString, it keeps the red circle at the top of the scrollbar and it keeps the red mark on the scrollbar where the "error" is, so even ignoring this error still makes it show up as an error.

0

Please sign in to leave a comment.