My first (buggy) experience with ReSharper 2.0

I downloaded the actual evaluation version of ReSharper (2.0 build 249) and ran into various problems while testing it on our projects using VS2005:

1. ReSharper did reset the language of VisualStudio to "Same As Microsoft Windows" (see Tools->Options->International Settings) on installation (was "English" before that).

2. Installing ReSharper did miss setting the rather important alt-return keyboard shortcut (Using ResetShortcuts in the ReSharper options fixed that) though the other keyboard shortcuts seem to have been set.

3. ReSharper mistakes a class for a namespace when both have the same name. In our project we have a Company.Dictionary namespace, when using that namespace in a class all usages of Dictionary from the System.Collections.Generic namespace result in ReSharper not recognizing them as the class but rather the namespace. VisualStudio though does compile the code.

4. In VS2005 it is possible that a project has project-references which are not in the same solution. As long as the referenced projects are build beforehand VisualStudio is able to resolve those references and build the dependent project. ReSharper is unable to resolve any symbols from those referenced projects.


Bug 3. and 4. have the side-effect that ReSharper will incorrectly remove using directives when optimizing them.

Also what memory overhead should I expect when using ReSharper? A quick comparison in one solution showed about 150MB without and about 450MB with ReSharper.


- Christoph Hornung

3 comments
Comment actions Permalink

Hello Christoph,

could you please elaborate more on this? How can one create such a reference?
Thanks in advance.


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


4. In VS2005 it is possible that a project has project-references
which are not in the same solution. As long as the referenced projects
are build beforehand VisualStudio is able to resolve those references
and build the dependent project. ReSharper is unable to resolve any
symbols from those referenced projects.

- Christoph Hornung



0
Comment actions Permalink

Hello Dmitry,

maybe these simple steps reproducing the problem and demonstrating how to add references to projects not in the same solution can help. In VS2005 do the following:

1. Create a project A in a new Solution SolutionA
2. Add the class ClassA to the project A
3. Add a new project B to the SolutionA residing in another directory.
4. Add the class ClassB to the project B.
5. Add a new reference to B and under projects choose A so that now B references A.
6. Add a field a to ClassB of type ClassA (importing the namespace A) and compile.
7. Close solution A and open projectB and save into a new Solution SolutionB. SolutionB should now only contain projectB and not projectA. Under References in the Solution Explorer should be an entry A with an explanation mark in a small yellow triangle.
8. Open ClassB and compile. Compilation should succeed but ReSharper should indicate with a red bar "Cannot resolve symbol 'A' at the "import A" statement and a "can not resolve symbol 'ClassA'" at the "ClassA a" statement .

Interestingly while building this small test-case I found after closing and reopening the solution the bug as described in 8. does not appear anymore (also the yellow triangle with the exclamation mark at the reference was gone). In the solutions I use though are many references as described above and I constantly hit the bug. (even though the solutions have been opened and closed many times).

I hope this helps clarify the issue.

Regards,
Christoph Hornung

0
Comment actions Permalink

Hello Christoph,

thanks for your explanation, I've created a tracker request (http://www.intellij.net/tracker/resharper/viewSCR?publicId=26425)

from your post. We'll investigate it.


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

Hello Dmitry,

maybe these simple steps reproducing the problem and demonstrating how
to add references to projects not in the same solution can help. In
VS2005 do the following:

1. Create a project A in a new Solution SolutionA

2. Add the class ClassA to the project A

3. Add a new project B to the SolutionA residing in another
directory.

4. Add the class ClassB to the project B.

5. Add a new reference to B and under projects choose A so that now B
references A.

6. Add a field a to ClassB of type ClassA (importing the namespace A)
and compile.

7. Close solution A and open projectB and save into a new Solution
SolutionB. SolutionB should now only contain projectB and not
projectA. Under References in the Solution Explorer should be
an entry A with an explanation mark in a small yellow triangle.

8. Open ClassB and compile. Compilation should succeed but ReSharper
should indicate with a red bar "Cannot resolve symbol 'A' at the
"import A" statement and a "can not resolve symbol 'ClassA'" at the
"ClassA a" statement .

Interestingly while building this small test-case I found after
closing and reopening the solution the bug as described in 8. does not
appear anymore (also the yellow triangle with the exclamation mark at
the reference was gone). In the solutions I use though are many
references as described above and I constantly hit the bug. (even
though the solutions have been opened and closed many times).

I hope this helps clarify the issue.

Regards,
Christoph Hornung



0

Please sign in to leave a comment.