#if directives drive ReSharper crazy

Hi, I'm evaluating ReSharper for over a week. So far it seems very useful and pretty easy to use, albeit a bit heavy on the CPU (I have P4 1.7MHz, 1GB RAM, 2 GB free disk).
It has a problem with the #if directives I use in the attached sample (I have a real case that is similar - the reason to do this is that the designer won't design an abstract class)

ReSharper gives



Attachment(s):
a.cs
6 comments
Comment actions Permalink

(your site has confusing GUI... didn't mean to post yet)

ReSharper gives a 'abstract inherited member is not implemented' error, although the current configuration is debug.

0
Comment actions Permalink

Hello Uri,

this is actually a known issue - ReSharper 1.x does not treat #if directives
in
a reasonable way. This is fixed in the upcoming ReSharper 2.0.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

(your site has confusing GUI... didn't mean to post yet)

ReSharper gives a 'abstract inherited member is not implemented'
error, although the current configuration is debug.



0
Comment actions Permalink

Thanks.
Any estimate when v2.0 will be out?

0
Comment actions Permalink

Any estimate when v2.0 will be out?


ReSharper 2.0 release is scheduled to happen about the official release of
Visual Studio 2005 (AFAIK, Microsoft announced it for the first decade of
November).

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Thanks.
Any estimate when v2.0 will be out?



0
Comment actions Permalink

But it will still work with VS.NET 2003, right? We don't intend to switch to 2.0 yet

0
Comment actions Permalink

Hello Uri,

yes, it will support both 2003 & 2005 Beta 2 versions of Visual Studio.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

But it will still work with VS.NET 2003, right? We don't intend to
switch to 2.0 yet



0

Please sign in to leave a comment.