Another step backwards in Build 233

Just installed it and loaded up my solution ... and virtually EVERY class
definition in my entire project is showing up as an error: What's strange
is there seems to be no rhyme or reason to why most classes show the errors,
but a few classes don't.

"Duplicate Definition 'namespace.classname'. Possibly missing keyword
partial"

This worked fine in build 232. This is just a standard class being defined.
And the whole file (ALL files) are just riddled with error underlines
everywhere ("Ambiguous Reference"). They all say things like "Foo.Bar.Baz
and Foo.Bar.Baz match" -- of course they do: THEY'RE THE SAME CLASS. I
can't imagine what it thinks is a duplicate definition.

Of course, none of the class definitions are incorrect or duplicate, and
none of the references are really ambiguous at all.

I have to roll back to 232 as this alone makes the entire product unusable.


6 comments
Comment actions Permalink

Paul Bradshaw wrote:

Just installed it and loaded up my solution ... and virtually EVERY class
definition in my entire project is showing up as an error: What's strange
is there seems to be no rhyme or reason to why most classes show the errors,
but a few classes don't.

"Duplicate Definition 'namespace.classname'. Possibly missing keyword
partial"

This worked fine in build 232. This is just a standard class being defined.
And the whole file (ALL files) are just riddled with error underlines
everywhere ("Ambiguous Reference"). They all say things like "Foo.Bar.Baz
and Foo.Bar.Baz match" -- of course they do: THEY'RE THE SAME CLASS. I
can't imagine what it thinks is a duplicate definition.

Of course, none of the class definitions are incorrect or duplicate, and
none of the references are really ambiguous at all.

I have to roll back to 232 as this alone makes the entire product unusable.


I've had this issue in an earlier build, don't recall which, but it can
be fixed by removing the _ReSharper cache directory and letting it re-index.

0
Comment actions Permalink

Much of the issues seem to revolve around the Web application in the new web
site model, I've had no problems once I migrated to the new Web Application
Project model. And the builds since 231 does not crash on exit anymore.

Krishna


<user@domain.invalid> wrote in message news:e16f2m$d5q$1@is.intellij.net...

Paul Bradshaw wrote:

>> Just installed it and loaded up my solution ... and virtually EVERY class
>> definition in my entire project is showing up as an error: What's
>> strange is there seems to be no rhyme or reason to why most classes show
>> the errors, but a few classes don't.
>>
>> "Duplicate Definition 'namespace.classname'. Possibly missing keyword
>> partial"
>>
>> This worked fine in build 232. This is just a standard class being
>> defined. And the whole file (ALL files) are just riddled with error
>> underlines everywhere ("Ambiguous Reference"). They all say things like
>> "Foo.Bar.Baz and Foo.Bar.Baz match" -- of course they do: THEY'RE THE
>> SAME CLASS. I can't imagine what it thinks is a duplicate definition.
>>
>> Of course, none of the class definitions are incorrect or duplicate, and
>> none of the references are really ambiguous at all.
>>
>> I have to roll back to 232 as this alone makes the entire product
>> unusable.
>>
>>
>

I've had this issue in an earlier build, don't recall which, but it can be
fixed by removing the _ReSharper cache directory and letting it re-index.



0
Comment actions Permalink

That was the first thing I did: I shut down VS2005, deleted the _Resharper*
directory under my solution, and restarted.

Same problem still existed.

In fact, I couldn't get it to go away no matter what I tried. So I
uninstalled and rolled back to 232, and will await the next version.


<user@domain.invalid> wrote in message news:e16f2m$d5q$1@is.intellij.net...

Paul Bradshaw wrote:

>> Just installed it and loaded up my solution ... and virtually EVERY class
>> definition in my entire project is showing up as an error: What's
>> strange is there seems to be no rhyme or reason to why most classes show
>> the errors, but a few classes don't.
>>
>> "Duplicate Definition 'namespace.classname'. Possibly missing keyword
>> partial"
>>
>> This worked fine in build 232. This is just a standard class being
>> defined. And the whole file (ALL files) are just riddled with error
>> underlines everywhere ("Ambiguous Reference"). They all say things like
>> "Foo.Bar.Baz and Foo.Bar.Baz match" -- of course they do: THEY'RE THE
>> SAME CLASS. I can't imagine what it thinks is a duplicate definition.
>>
>> Of course, none of the class definitions are incorrect or duplicate, and
>> none of the references are really ambiguous at all.
>>
>> I have to roll back to 232 as this alone makes the entire product
>> unusable.
>>
>>
>

I've had this issue in an earlier build, don't recall which, but it can be
fixed by removing the _ReSharper cache directory and letting it re-index.



0
Comment actions Permalink

Paul,

how is your solution structured? Do you ever reference outputs from C#
projects from other C# projects?
Is this reproducible on any solution?
Does this happen after you remove ReSharper caches?

Friendly,
Dmitry


Paul Bradshaw wrote:

Just installed it and loaded up my solution ... and virtually EVERY class
definition in my entire project is showing up as an error: What's strange
is there seems to be no rhyme or reason to why most classes show the errors,
but a few classes don't.

"Duplicate Definition 'namespace.classname'. Possibly missing keyword
partial"

This worked fine in build 232. This is just a standard class being defined.
And the whole file (ALL files) are just riddled with error underlines
everywhere ("Ambiguous Reference"). They all say things like "Foo.Bar.Baz
and Foo.Bar.Baz match" -- of course they do: THEY'RE THE SAME CLASS. I
can't imagine what it thinks is a duplicate definition.

Of course, none of the class definitions are incorrect or duplicate, and
none of the references are really ambiguous at all.

I have to roll back to 232 as this alone makes the entire product unusable.



--
Dmitry Lomov
Senior Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop With Pleasure!"

0
Comment actions Permalink

Same as some others have said, but I'll repeat for you:

The solution has about a dozen C# library projects (producing DLL
assemblies) and one website (not project, but the 2005 website crap). All
references are to DLL assemblies, not to projects.

The project build process copies all the output DLL assemblies to a common
directory, and the references are to the assemblies in this directory, not
to the location in bin/debug underneath the project.

It is completely reproducable, restart doesn't solve the problem, and
removing the _Resharper* folders didn't solve the problem.

Reverting back to 232 did solve the problem.

Most every references class showed the problem, but as I said, I noticed a
few that did not, and I didn't notice an immediate pattern for that. Since
I revered to 232 since 233 was unusable, I cannot do more detective work for
you just now. I'll try the next build when it comes out, and if there are
still problems, I'll try to get you more information then.

- Paul

"Dmitry Lomov (JetBrains)" <dmitry.lomov@jetbrains.com> wrote in message
news:e1avt3$388$1@is.intellij.net...

Paul,

>

how is your solution structured? Do you ever reference outputs from C#
projects from other C# projects?
Is this reproducible on any solution?
Does this happen after you remove ReSharper caches?

>

Friendly,
Dmitry

>
>

Paul Bradshaw wrote:

>> Just installed it and loaded up my solution ... and virtually EVERY class
>> definition in my entire project is showing up as an error: What's
>> strange is there seems to be no rhyme or reason to why most classes show
>> the errors, but a few classes don't.
>>
>> "Duplicate Definition 'namespace.classname'. Possibly missing keyword
>> partial"
>>
>> This worked fine in build 232. This is just a standard class being
>> defined. And the whole file (ALL files) are just riddled with error
>> underlines everywhere ("Ambiguous Reference"). They all say things like
>> "Foo.Bar.Baz and Foo.Bar.Baz match" -- of course they do: THEY'RE THE
>> SAME CLASS. I can't imagine what it thinks is a duplicate definition.
>>
>> Of course, none of the class definitions are incorrect or duplicate, and
>> none of the references are really ambiguous at all.
>>
>> I have to roll back to 232 as this alone makes the entire product
>> unusable.
>>
>>
>
>

--
Dmitry Lomov
Senior Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop With Pleasure!"



0
Comment actions Permalink

I have seen the same problem. I have about 7 projects in my solution.
Several projects which are .exe files reference other projects which are
dll's. I tried deleting the caches but did not have any success.
The large number of errors makes it unusable.

--


-


This mailbox protected from junk email by MailFrontier Desktop
from MailFrontier, Inc. http://info.mailfrontier.com

"Dmitry Lomov (JetBrains)" <dmitry.lomov@jetbrains.com> wrote in message
news:e1avt3$388$1@is.intellij.net...

Paul,

>

how is your solution structured? Do you ever reference outputs from C#
projects from other C# projects?
Is this reproducible on any solution?
Does this happen after you remove ReSharper caches?

>

Friendly,
Dmitry

>
>

Paul Bradshaw wrote:

>> Just installed it and loaded up my solution ... and virtually EVERY class
>> definition in my entire project is showing up as an error: What's
>> strange is there seems to be no rhyme or reason to why most classes show
>> the errors, but a few classes don't.
>>
>> "Duplicate Definition 'namespace.classname'. Possibly missing keyword
>> partial"
>>
>> This worked fine in build 232. This is just a standard class being
>> defined. And the whole file (ALL files) are just riddled with error
>> underlines everywhere ("Ambiguous Reference"). They all say things like
>> "Foo.Bar.Baz and Foo.Bar.Baz match" -- of course they do: THEY'RE THE
>> SAME CLASS. I can't imagine what it thinks is a duplicate definition.
>>
>> Of course, none of the class definitions are incorrect or duplicate, and
>> none of the references are really ambiguous at all.
>>
>> I have to roll back to 232 as this alone makes the entire product
>> unusable.
>>
>>
>
>

--
Dmitry Lomov
Senior Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop With Pleasure!"



0

Please sign in to leave a comment.