2.0 shows every identifier as an error

Every one of my source files seems to have every identifier marked as an
error.

I don't know if this is the reason, but we are building our source files
with NAnt. To get around the VS.NET locking, we copied the "release"
configuration to an "NAnt" configuration, while our NAnt scripts build
to the debug directories under the hood.

Resharper 1.5 seemed to handle this well - is there something different
about how Resharper 2.0 parses files?

Matt.

7 comments
Comment actions Permalink

Hello Matthew,

please post a stack trace illustrating this problem. Do you experience it
with a newly created or
existing solutions?


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

Every one of my source files seems to have every identifier marked as
an error.

I don't know if this is the reason, but we are building our source
files with NAnt. To get around the VS.NET locking, we copied the
"release" configuration to an "NAnt" configuration, while our NAnt
scripts build to the debug directories under the hood.

Resharper 1.5 seemed to handle this well - is there something
different about how Resharper 2.0 parses files?

Matt.



0
Comment actions Permalink

It happens with one existing solution and doesn't actually throw an
error - it's just that every identifier (built-in or not) is shown as
an error. It's as if Resharper never loads any symbols from anything.

This includes stuff like void, string and the root "System" namespace.

I tried it on another large sourcebase and it seemed to work. The only
difference was that the non-working solution has some edits to disable
all the projects from building in favour of using an NAnt build.

Matt.

Dmitry Shaporenkov wrote:

Hello Matthew,

please post a stack trace illustrating this problem. Do you experience
it with a newly created or
existing solutions?


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

>> Every one of my source files seems to have every identifier marked as
>> an error.
>>
>> I don't know if this is the reason, but we are building our source
>> files with NAnt. To get around the VS.NET locking, we copied the
>> "release" configuration to an "NAnt" configuration, while our NAnt
>> scripts build to the debug directories under the hood.
>>
>> Resharper 1.5 seemed to handle this well - is there something
>> different about how Resharper 2.0 parses files?
>>
>> Matt.
>>


0
Comment actions Permalink

Hello Matthew,

could you please describe this solution in more detail? Which project does
it include?

Thanks.


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

It happens with one existing solution and doesn't actually throw an
error - it's just that every identifier (built-in or not) is shown
as an error. It's as if Resharper never loads any symbols from
anything.

This includes stuff like void, string and the root "System" namespace.

I tried it on another large sourcebase and it seemed to work. The
only difference was that the non-working solution has some edits to
disable all the projects from building in favour of using an NAnt
build.

Matt.

Dmitry Shaporenkov wrote:

>> Hello Matthew,
>>
>> please post a stack trace illustrating this problem. Do you
>> experience
>> it with a newly created or
>> existing solutions?
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Every one of my source files seems to have every identifier marked
>>> as an error.
>>>
>>> I don't know if this is the reason, but we are building our source
>>> files with NAnt. To get around the VS.NET locking, we copied the
>>> "release" configuration to an "NAnt" configuration, while our NAnt
>>> scripts build to the debug directories under the hood.
>>>
>>> Resharper 1.5 seemed to handle this well - is there something
>>> different about how Resharper 2.0 parses files?
>>>
>>> Matt.
>>>


0
Comment actions Permalink

Found the problem - looks like IKVM is killing the initial scan of the
project. When Resharper failed to load the assemblies, it didn't bother
scanning the rest of the project (including the system assemblies!).
Once I deleted the IKVM DLLs off the disk, the project started up file.

We're using the latest IKVM release from:
http://sourceforge.net/project/showfiles.php?group_id=69637

Dmitry Shaporenkov wrote:

Hello Matthew,

could you please describe this solution in more detail? Which project
does it include?

Thanks.


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

>> It happens with one existing solution and doesn't actually throw an
>> error - it's just that every identifier (built-in or not) is shown
>> as an error. It's as if Resharper never loads any symbols from
>> anything.
>>
>> This includes stuff like void, string and the root "System" namespace.
>>
>> I tried it on another large sourcebase and it seemed to work. The
>> only difference was that the non-working solution has some edits to
>> disable all the projects from building in favour of using an NAnt
>> build.
>>
>> Matt.
>>
>> Dmitry Shaporenkov wrote:
>>
>>> Hello Matthew,
>>>
>>> please post a stack trace illustrating this problem. Do you
>>> experience
>>> it with a newly created or
>>> existing solutions?
>>> Regards,
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>
>>>> Every one of my source files seems to have every identifier marked
>>>> as an error.
>>>>
>>>> I don't know if this is the reason, but we are building our source
>>>> files with NAnt. To get around the VS.NET locking, we copied the
>>>> "release" configuration to an "NAnt" configuration, while our NAnt
>>>> scripts build to the debug directories under the hood.
>>>>
>>>> Resharper 1.5 seemed to handle this well - is there something
>>>> different about how Resharper 2.0 parses files?
>>>>
>>>> Matt.
>>>>


0
Comment actions Permalink

Hello Matthew,

thank you a lot for your investigation. We'll check this.


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

Found the problem - looks like IKVM is killing the initial scan of the
project. When Resharper failed to load the assemblies, it didn't
bother scanning the rest of the project (including the system
assemblies!). Once I deleted the IKVM DLLs off the disk, the project
started up file.

We're using the latest IKVM release from:
http://sourceforge.net/project/showfiles.php?group_id=69637
Dmitry Shaporenkov wrote:

>> Hello Matthew,
>>
>> could you please describe this solution in more detail? Which project
>> does it include?
>>
>> Thanks.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> It happens with one existing solution and doesn't actually throw an
>>> error - it's just that every identifier (built-in or not) is shown
>>> as an error. It's as if Resharper never loads any symbols from
>>> anything.
>>>
>>> This includes stuff like void, string and the root "System"
>>> namespace.
>>>
>>> I tried it on another large sourcebase and it seemed to work. The
>>> only difference was that the non-working solution has some edits to
>>> disable all the projects from building in favour of using an NAnt
>>> build.
>>>
>>> Matt.
>>>
>>> Dmitry Shaporenkov wrote:
>>>
>>>> Hello Matthew,
>>>>
>>>> please post a stack trace illustrating this problem. Do you
>>>> experience
>>>> it with a newly created or
>>>> existing solutions?
>>>> Regards,
>>>> Dmitry Shaporenkov
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
>>>>> Every one of my source files seems to have every identifier marked
>>>>> as an error.
>>>>>
>>>>> I don't know if this is the reason, but we are building our source
>>>>> files with NAnt. To get around the VS.NET locking, we copied the
>>>>> "release" configuration to an "NAnt" configuration, while our NAnt
>>>>> scripts build to the debug directories under the hood.
>>>>>
>>>>> Resharper 1.5 seemed to handle this well - is there something
>>>>> different about how Resharper 2.0 parses files?
>>>>>
>>>>> Matt.
>>>>>


0
Comment actions Permalink

I have the same problem (as of 203), dies on IKVM, and stop loading...
Then everything is red in the editor.
I have had to roll back to 165.


Scott

Matthew Mastracci wrote:

Found the problem - looks like IKVM is killing the initial scan of the
project. When Resharper failed to load the assemblies, it didn't bother
scanning the rest of the project (including the system assemblies!).
Once I deleted the IKVM DLLs off the disk, the project started up file.

We're using the latest IKVM release from:
http://sourceforge.net/project/showfiles.php?group_id=69637

Dmitry Shaporenkov wrote:

>> Hello Matthew,
>>
>> could you please describe this solution in more detail? Which project
>> does it include?
>>
>> Thanks.
>>
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>
>>> It happens with one existing solution and doesn't actually throw an
>>> error - it's just that every identifier (built-in or not) is shown
>>> as an error. It's as if Resharper never loads any symbols from
>>> anything.
>>>
>>> This includes stuff like void, string and the root "System" namespace.
>>>
>>> I tried it on another large sourcebase and it seemed to work. The
>>> only difference was that the non-working solution has some edits to
>>> disable all the projects from building in favour of using an NAnt
>>> build.
>>>
>>> Matt.
>>>
>>> Dmitry Shaporenkov wrote:
>>>
>>>> Hello Matthew,
>>>>
>>>> please post a stack trace illustrating this problem. Do you
>>>> experience
>>>> it with a newly created or
>>>> existing solutions?
>>>> Regards,
>>>> Dmitry Shaporenkov
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
>>>>
>>>>> Every one of my source files seems to have every identifier marked
>>>>> as an error.
>>>>>
>>>>> I don't know if this is the reason, but we are building our source
>>>>> files with NAnt. To get around the VS.NET locking, we copied the
>>>>> "release" configuration to an "NAnt" configuration, while our NAnt
>>>>> scripts build to the debug directories under the hood.
>>>>>
>>>>> Resharper 1.5 seemed to handle this well - is there something
>>>>> different about how Resharper 2.0 parses files?
>>>>>
>>>>> Matt.
>>>>>
>>
>>

0
Comment actions Permalink

Hello Scott & Matthew,

fixes for IKVM assemblies will be available in the build 204.
We've indeed found a number of issues, in particular, with the IKVM.GNU.Classpath
assembly (the latest version from sourceforge). Although this is not very
surprising,
since you can easily check that this assembly is unverifiable (and Reflector
also seems to
have problems with it).

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

I have the same problem (as of 203), dies on IKVM, and stop loading...
Then everything is red in the editor.
I have had to roll back to 165.
Scott

Matthew Mastracci wrote:

>> Found the problem - looks like IKVM is killing the initial scan of
>> the project. When Resharper failed to load the assemblies, it didn't
>> bother scanning the rest of the project (including the system
>> assemblies!). Once I deleted the IKVM DLLs off the disk, the project
>> started up file.
>>
>> We're using the latest IKVM release from:
>> http://sourceforge.net/project/showfiles.php?group_id=69637
>> Dmitry Shaporenkov wrote:
>>
>>> Hello Matthew,
>>>
>>> could you please describe this solution in more detail? Which
>>> project does it include?
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> It happens with one existing solution and doesn't actually throw an
>>>> error - it's just that every identifier (built-in or not) is
>>>> shown as an error. It's as if Resharper never loads any symbols
>>>> from anything.
>>>>
>>>> This includes stuff like void, string and the root "System"
>>>> namespace.
>>>>
>>>> I tried it on another large sourcebase and it seemed to work. The
>>>> only difference was that the non-working solution has some edits to
>>>> disable all the projects from building in favour of using an NAnt
>>>> build.
>>>>
>>>> Matt.
>>>>
>>>> Dmitry Shaporenkov wrote:
>>>>
>>>>> Hello Matthew,
>>>>>
>>>>> please post a stack trace illustrating this problem. Do you
>>>>> experience
>>>>> it with a newly created or
>>>>> existing solutions?
>>>>> Regards,
>>>>> Dmitry Shaporenkov
>>>>> JetBrains, Inc
>>>>> http://www.jetbrains.com
>>>>> "Develop with pleasure!"
>>>>>> Every one of my source files seems to have every identifier
>>>>>> marked as an error.
>>>>>>
>>>>>> I don't know if this is the reason, but we are building our
>>>>>> source files with NAnt. To get around the VS.NET locking, we
>>>>>> copied the "release" configuration to an "NAnt" configuration,
>>>>>> while our NAnt scripts build to the debug directories under the
>>>>>> hood.
>>>>>>
>>>>>> Resharper 1.5 seemed to handle this well - is there something
>>>>>> different about how Resharper 2.0 parses files?
>>>>>>
>>>>>> Matt.
>>>>>>


0

Please sign in to leave a comment.