Goto Declaration with DLL project references

I have a solution with about 20 projetcs in it.

Each project is referencing others using a DLL reference, not a project
reference.

In addition, the DLL reference is pointing to a common "bin" directory that
all the DLLs are copied to during a post-build step, rather than in the
in-place "Debug" or "Release" folders.

If I'm in one project, and select "Go to Definition", Resharper brings up
the object browser rather than going to the source code.

This is scheduled to be fixed prior to release, correct?  Resharper 1.5.x
can do this, and it's a near requirement for this to work for our project
(otherwise refactoring is rather useless).

Just curious where this stands, as we get closer and closer to release...

  - Paul


2 comments
Comment actions Permalink

Hello Paul,

you are correct that we plan to support association of project outputs with
projects to ReSharper.

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

I have a solution with about 20 projetcs in it.

Each project is referencing others using a DLL reference, not a
project reference.

In addition, the DLL reference is pointing to a common "bin" directory
that all the DLLs are copied to during a post-build step, rather than
in the in-place "Debug" or "Release" folders.

If I'm in one project, and select "Go to Definition", Resharper brings
up the object browser rather than going to the source code.

This is scheduled to be fixed prior to release, correct?  Resharper
1.5.x can do this, and it's a near requirement for this to work for
our project (otherwise refactoring is rather useless).

Just curious where this stands, as we get closer and closer to
release...

- Paul



0
Comment actions Permalink

Hello Paul,

you are correct that we plan to support association of project outputs with
projects to ReSharper.

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

I have a solution with about 20 projetcs in it.

Each project is referencing others using a DLL reference, not a
project reference.

In addition, the DLL reference is pointing to a common "bin" directory
that all the DLLs are copied to during a post-build step, rather than
in the in-place "Debug" or "Release" folders.

If I'm in one project, and select "Go to Definition", Resharper brings
up the object browser rather than going to the source code.

This is scheduled to be fixed prior to release, correct?  Resharper
1.5.x can do this, and it's a near requirement for this to work for
our project (otherwise refactoring is rather useless).

Just curious where this stands, as we get closer and closer to
release...

- Paul



0

Please sign in to leave a comment.