[Question]: Close All but this

The 'Close all but this' window context item seems to be gone from
Resharper since 215. Is this intentional?

If so, I would make a plea to bring this back. This was a very cool
feature as I tend to open file after file after file. Being able to
close all but the current one was a really nice feature.

--
Matt Berther
http://www.mattberther.com

13 comments
Comment actions Permalink

I noticed that too. Please bring it back :)

Matt Berther wrote:

The 'Close all but this' window context item seems to be gone from
Resharper since 215. Is this intentional?

If so, I would make a plea to bring this back. This was a very cool
feature as I tend to open file after file after file. Being able to
close all but the current one was a really nice feature.

0
Comment actions Permalink

Hello Alex,

what version of VS you're using? If VS 2005, then it has this feature built-in.
The problem is
that it was previously overriden by ReSharper's one, and we've removed this
feature in ReSharper
for VS 2005. As a result, it may happen that currently you have neither the
built-in nor the ReSharper's
feature. To restore the built-in one, please do the following:

1) Disable ReSharper
2) Reset All Settings (Tools|Import And Export|..)
3) Enable ReSharper.

If you're running on VS 2003, then the feature should remain intact.


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

I noticed that too. Please bring it back :)

Matt Berther wrote:

>> The 'Close all but this' window context item seems to be gone from
>> Resharper since 215. Is this intentional?
>>
>> If so, I would make a plea to bring this back. This was a very cool
>> feature as I tend to open file after file after file. Being able to
>> close all but the current one was a really nice feature.
>>


0
Comment actions Permalink

Hi Dmitry,

I am using VS2005 and your steps work. I have the feature back. Thanks!

Alex

Dmitry Shaporenkov (JetBrains) wrote:

Hello Alex,

what version of VS you're using? If VS 2005, then it has this feature
built-in. The problem is
that it was previously overriden by ReSharper's one, and we've removed
this feature in ReSharper
for VS 2005. As a result, it may happen that currently you have neither
the built-in nor the ReSharper's
feature. To restore the built-in one, please do the following:

1) Disable ReSharper
2) Reset All Settings (Tools|Import And Export|..)
3) Enable ReSharper.

If you're running on VS 2003, then the feature should remain intact.


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

>> I noticed that too. Please bring it back :)
>>
>> Matt Berther wrote:
>>
>>> The 'Close all but this' window context item seems to be gone from
>>> Resharper since 215. Is this intentional?
>>>
>>> If so, I would make a plea to bring this back. This was a very cool
>>> feature as I tend to open file after file after file. Being able to
>>> close all but the current one was a really nice feature.
>>>


0
Comment actions Permalink

Hi,

This solution works, but has caused the following problem for me:

The lightbulb does not appear anymore. When I move the cursor to an error, I
can do ALT + Enter and then I get the menu with suggestions, but no
lightbulb.

Nor does the yellow lightbulb appear to indicate a refactoring issue.

Regards,

Patrick


"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9fc8e88c7fbbb7d96a0fd@news.intellij.net...

Hello Alex,

>

what version of VS you're using? If VS 2005, then it has this feature
built-in. The problem is
that it was previously overriden by ReSharper's one, and we've removed
this feature in ReSharper
for VS 2005. As a result, it may happen that currently you have neither
the built-in nor the ReSharper's
feature. To restore the built-in one, please do the following:

>

1) Disable ReSharper
2) Reset All Settings (Tools|Import And Export|..)
3) Enable ReSharper.

>

If you're running on VS 2003, then the feature should remain intact.

>
>

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

>
>> I noticed that too. Please bring it back :)
>>
>> Matt Berther wrote:
>>
>>> The 'Close all but this' window context item seems to be gone from
>>> Resharper since 215. Is this intentional?
>>>
>>> If so, I would make a plea to bring this back. This was a very cool
>>> feature as I tend to open file after file after file. Being able to
>>> close all but the current one was a really nice feature.
>>>
>



0
Comment actions Permalink

Hello Patrick,

hmm, this hardly relates to the original problem. There is currently a known
issue with light bulb appearing in
a not visible are in files with collapsed regions. May be this is your case?


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

Hi,

This solution works, but has caused the following problem for me:

The lightbulb does not appear anymore. When I move the cursor to an
error, I can do ALT + Enter and then I get the menu with suggestions,
but no lightbulb.

Nor does the yellow lightbulb appear to indicate a refactoring issue.

Regards,

Patrick

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9fc8e88c7fbbb7d96a0fd@news.intellij.net...

>> Hello Alex,
>>
>> what version of VS you're using? If VS 2005, then it has this feature
>> built-in. The problem is
>> that it was previously overriden by ReSharper's one, and we've
>> removed
>> this feature in ReSharper
>> for VS 2005. As a result, it may happen that currently you have
>> neither
>> the built-in nor the ReSharper's
>> feature. To restore the built-in one, please do the following:
>> 1) Disable ReSharper
>> 2) Reset All Settings (Tools|Import And Export|..)
>> 3) Enable ReSharper.
>> If you're running on VS 2003, then the feature should remain intact.
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I noticed that too. Please bring it back :)
>>>
>>> Matt Berther wrote:
>>>
>>>> The 'Close all but this' window context item seems to be gone from
>>>> Resharper since 215. Is this intentional?
>>>>
>>>> If so, I would make a plea to bring this back. This was a very cool
>>>> feature as I tend to open file after file after file. Being able to
>>>> close all but the current one was a really nice feature.
>>>>


0
Comment actions Permalink

Hi Dmitry,

No, there is no Region in the file. The lightbulb worked fine before I did
the Reset, but not after, so the two are definitely related in some way. I
have restarted Studio but this has no effect.

Regards,

Patrick

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9fd5968c7fc478945bcb4@news.intellij.net...

Hello Patrick,

>

hmm, this hardly relates to the original problem. There is currently a
known issue with light bulb appearing in
a not visible are in files with collapsed regions. May be this is your
case?

>
>

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

>
>> Hi,
>>
>> This solution works, but has caused the following problem for me:
>>
>> The lightbulb does not appear anymore. When I move the cursor to an
>> error, I can do ALT + Enter and then I get the menu with suggestions,
>> but no lightbulb.
>>
>> Nor does the yellow lightbulb appear to indicate a refactoring issue.
>>
>> Regards,
>>
>> Patrick
>>
>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
>> news:c8a894d9fc8e88c7fbbb7d96a0fd@news.intellij.net...
>>
>>> Hello Alex,
>>>
>>> what version of VS you're using? If VS 2005, then it has this feature
>>> built-in. The problem is
>>> that it was previously overriden by ReSharper's one, and we've
>>> removed
>>> this feature in ReSharper
>>> for VS 2005. As a result, it may happen that currently you have
>>> neither
>>> the built-in nor the ReSharper's
>>> feature. To restore the built-in one, please do the following:
>>> 1) Disable ReSharper
>>> 2) Reset All Settings (Tools|Import And Export|..)
>>> 3) Enable ReSharper.
>>> If you're running on VS 2003, then the feature should remain intact.
>>>
>>> Regards,
>>> Dmitry Shaporenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>>>> I noticed that too. Please bring it back :)
>>>>
>>>> Matt Berther wrote:
>>>>
>>>>> The 'Close all but this' window context item seems to be gone from
>>>>> Resharper since 215. Is this intentional?
>>>>>
>>>>> If so, I would make a plea to bring this back. This was a very cool
>>>>> feature as I tend to open file after file after file. Being able to
>>>>> close all but the current one was a really nice feature.
>>>>>
>



0
Comment actions Permalink

This is madness,

After writing the preceding post, I switched back to studio and what catches
my eye: a red lightbulb!!!
The problem seems to have fixed itself and no, I was completely awake and
have perfect vision ;)

Regards,

Patrick

"Patrick" <patrick@nospam.com> wrote in message
news:dshhfr$9n2$1@is.intellij.net...

Hi Dmitry,

>

No, there is no Region in the file. The lightbulb worked fine before I did
the Reset, but not after, so the two are definitely related in some way. I
have restarted Studio but this has no effect.

>

Regards,

>

Patrick

>

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9fd5968c7fc478945bcb4@news.intellij.net...

>> Hello Patrick,
>>
>> hmm, this hardly relates to the original problem. There is currently a
>> known issue with light bulb appearing in
>> a not visible are in files with collapsed regions. May be this is your
>> case?
>>
>>
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>
>>> Hi,
>>>
>>> This solution works, but has caused the following problem for me:
>>>
>>> The lightbulb does not appear anymore. When I move the cursor to an
>>> error, I can do ALT + Enter and then I get the menu with suggestions,
>>> but no lightbulb.
>>>
>>> Nor does the yellow lightbulb appear to indicate a refactoring issue.
>>>
>>> Regards,
>>>
>>> Patrick
>>>
>>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
>>> news:c8a894d9fc8e88c7fbbb7d96a0fd@news.intellij.net...
>>>
>>>> Hello Alex,
>>>>
>>>> what version of VS you're using? If VS 2005, then it has this feature
>>>> built-in. The problem is
>>>> that it was previously overriden by ReSharper's one, and we've
>>>> removed
>>>> this feature in ReSharper
>>>> for VS 2005. As a result, it may happen that currently you have
>>>> neither
>>>> the built-in nor the ReSharper's
>>>> feature. To restore the built-in one, please do the following:
>>>> 1) Disable ReSharper
>>>> 2) Reset All Settings (Tools|Import And Export|..)
>>>> 3) Enable ReSharper.
>>>> If you're running on VS 2003, then the feature should remain intact.
>>>>
>>>> Regards,
>>>> Dmitry Shaporenkov
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
>>>>> I noticed that too. Please bring it back :)
>>>>>
>>>>> Matt Berther wrote:
>>>>>
>>>>>> The 'Close all but this' window context item seems to be gone from
>>>>>> Resharper since 215. Is this intentional?
>>>>>>
>>>>>> If so, I would make a plea to bring this back. This was a very cool
>>>>>> feature as I tend to open file after file after file. Being able to
>>>>>> close all but the current one was a really nice feature.
>>>>>>
>>
>>
>



0
Comment actions Permalink

Hello Patrick,

can you repeat this on simple solution?


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

Hi Dmitry,

No, there is no Region in the file. The lightbulb worked fine before I
did the Reset, but not after, so the two are definitely related in
some way. I have restarted Studio but this has no effect.

Regards,

Patrick

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d9fd5968c7fc478945bcb4@news.intellij.net...

>> Hello Patrick,
>>
>> hmm, this hardly relates to the original problem. There is currently
>> a
>> known issue with light bulb appearing in
>> a not visible are in files with collapsed regions. May be this is
>> your
>> case?
>> Regards,
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> Hi,
>>>
>>> This solution works, but has caused the following problem for me:
>>>
>>> The lightbulb does not appear anymore. When I move the cursor to an
>>> error, I can do ALT + Enter and then I get the menu with
>>> suggestions, but no lightbulb.
>>>
>>> Nor does the yellow lightbulb appear to indicate a refactoring
>>> issue.
>>>
>>> Regards,
>>>
>>> Patrick
>>>
>>> "Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in
>>> message news:c8a894d9fc8e88c7fbbb7d96a0fd@news.intellij.net...
>>>
>>>> Hello Alex,
>>>>
>>>> what version of VS you're using? If VS 2005, then it has this
>>>> feature
>>>> built-in. The problem is
>>>> that it was previously overriden by ReSharper's one, and we've
>>>> removed
>>>> this feature in ReSharper
>>>> for VS 2005. As a result, it may happen that currently you have
>>>> neither
>>>> the built-in nor the ReSharper's
>>>> feature. To restore the built-in one, please do the following:
>>>> 1) Disable ReSharper
>>>> 2) Reset All Settings (Tools|Import And Export|..)
>>>> 3) Enable ReSharper.
>>>> If you're running on VS 2003, then the feature should remain
>>>> intact.
>>>> Regards,
>>>> Dmitry Shaporenkov
>>>> JetBrains, Inc
>>>> http://www.jetbrains.com
>>>> "Develop with pleasure!"
>>>>> I noticed that too. Please bring it back :)
>>>>>
>>>>> Matt Berther wrote:
>>>>>
>>>>>> The 'Close all but this' window context item seems to be gone
>>>>>> from Resharper since 215. Is this intentional?
>>>>>>
>>>>>> If so, I would make a plea to bring this back. This was a very
>>>>>> cool feature as I tend to open file after file after file. Being
>>>>>> able to close all but the current one was a really nice feature.
>>>>>>


0
Comment actions Permalink

Patrick,
There exist a strange problem when R# wrongly detects, whether VS is actiove
or not. Switching somewhere outside and back typically works.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hi Dmitry and Sergey,

The problem suddenly reoccurred.

Instead of the lightbulb, there very fast flashes an error message in the
status bar saying:

'More exceptions occur. You can continue working.'

Or something like that, it is very hard to read.

ALT + Enter shows the suggestion menu and the lightbulb, but in the upper
left corner of the editor instead of on the same line as the cursor.

Regards,
Patrick

"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
news:dsi6r2$a0b$1@is.intellij.net...

Patrick,
There exist a strange problem when R# wrongly detects, whether VS is
actiove or not. Switching somewhere outside and back typically works.

>

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"



0
Comment actions Permalink

Hello Patrick,

this indicates that some exceptions have happened and those exceptions prevent
correct functioning. Could you please take a look at the log (ReSharper|Show
Log) and check
the latest stack traces there?


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

Hi Dmitry and Sergey,

The problem suddenly reoccurred.

Instead of the lightbulb, there very fast flashes an error message in
the status bar saying:

'More exceptions occur. You can continue working.'

Or something like that, it is very hard to read.

ALT + Enter shows the suggestion menu and the lightbulb, but in the
upper left corner of the editor instead of on the same line as the
cursor.

Regards,
Patrick
"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
news:dsi6r2$a0b$1@is.intellij.net...

>> Patrick,
>> There exist a strange problem when R# wrongly detects, whether VS is
>> actiove or not. Switching somewhere outside and back typically works.
>> --
>> Sergey V. Coox
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"


0
Comment actions Permalink

Hi Dmitry,

The following stack trace appears a zillion times in my log file.

Regards,

Patrick

JetBrains.ReSharper.Util.InternalErrorException: An exception has
occurred ---> System.NullReferenceException: Object reference not set to an
instance of an object.
at JetBrains.ReSharper.Psi.ConstantValue.Int32Value() in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\constantValue\ConstantValue.cs:line 482
at JetBrains.ReSharper.Psi.ConstantValue.Int32Value() in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\constantValue\ConstantValue.cs:line 472
at JetBrains.ReSharper.Psi.ConstantValue.ToType(ConstantValueType type)
in c:\TEMP\tmp1532.tmp\src\Psi\src\impl\constantValue\ConstantValue.cs:line
269
at JetBrains.ReSharper.Psi.ConstantValue.ToType(IType type) in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\constantValue\ConstantValue.cs:line 253
at JetBrains.ReSharper.Psi.ConstantValue.ToTypeExplicit(IType type) in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\constantValue\ConstantValue.cs:line 231
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.CastExpression.CompileTimeConstantValueInternal()
in c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\CastExpression.cs:line
41
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.CSharpExpressionBase.CompileTimeConstantValue()
in
c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\CSharpExpressionBase.cs:line
65
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.CastExpression.GetExpressionType()
in c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\CastExpression.cs:line
15
at
JetBrains.ReSharper.Psi.Impl.Resolve.MatchParametersFilter.ArgumentInfo..ctor(IArgument
argument) in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\resolve\filters\MatchParametersFilter.cs:line
139
at
JetBrains.ReSharper.Psi.Impl.Resolve.MatchParametersFilter..ctor(IArgument[]
arguments) in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\resolve\filters\MatchParametersFilter.cs:line
17
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.ReferenceExpressionBase.GetMethodReferenceFilter(IArgument[]
arguments) in
c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\ReferenceExpressionBase.cs:line
330
at
JetBrains.ReSharper.Psi.Impl.Resolve.ResolveUtil.ReferenceExpressionResolveFilters(IExpression
expression, String name, IAccessContext context, ParameterTypeFilterProvider
filterProvider) in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\resolve\ResolveUtil.cs:line 777
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.ReferenceExpressionBase.Resolve(ISymbolTable
table, IAccessContext context, ResolveErrorType& errorType) in
c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\ReferenceExpressionBase.cs:line
284
at
JetBrains.ReSharper.Psi.Impl.Resolve.ResolveUtil.ResolveQualifiableReference(IQualifiableReference
reference, IAccessContext context, ResolveErrorType& errorType) in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\resolve\ResolveUtil.cs:line 585
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.ReferenceExpressionBase.ResolveWithoutCache(ResolveErrorType&
errorType) in
c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\ReferenceExpressionBase.cs:line
267
at
JetBrains.ReSharper.Psi.Impl.Resolve.ResolveUtil.ResolveWithCache(IInternalRef
reference) in
c:\TEMP\tmp1532.tmp\src\Psi\src\impl\resolve\ResolveUtil.cs:line 529
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.ReferenceExpressionBase.Resolve()
in
c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\ReferenceExpressionBase.cs:line
211
at
JetBrains.ReSharper.Daemon.CSharp.Stages.SmartResolverProcess.VisitReferenceExpression(IReferenceExpression
referenceExpression) in
c:\TEMP\tmp1532.tmp\src\Daemon.CSharp\src\Stages\SmartResolver.cs:line 217
at
JetBrains.ReSharper.Daemon.CSharp.Stages.SmartResolverProcess.VisitElement(IResolveElement
resolveElement) in
c:\TEMP\tmp1532.tmp\src\Daemon.CSharp\src\Stages\SmartResolver.cs:line 161
at
JetBrains.ReSharper.Psi.Resolve.Resolver.ProcessAfterInterior(IResolveElement
element) in c:\TEMP\tmp1532.tmp\src\Psi\src\resolve\Resolver.cs:line 160
at
JetBrains.ReSharper.Psi.CSharp.Impl.Tree.InvocationExpression.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\cSharp\impl\tree\InvocationExpression.cs:line
85
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Resolve.ResolveElementUtil.ProcessDescendantForResolve(IResolveElementProcessor
processor, IResolveElement descendant) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Resolve\SharedImplUtil.cs:line
15
at
JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendantsForResolve(IResolveElementProcessor
processor) in
c:\TEMP\tmp1532.tmp\src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 523
at JetBrains.ReSharper.Psi.Resolve.Resolver.ProcessFile(IResolveElement
topElement) in c:\TEMP\tmp1532.tmp\src\Psi\src\resolve\Resolver.cs:line 43
at
JetBrains.ReSharper.Psi.Resolve.AllNonQualifiedReferencesResolver.ProcessFile(IResolveElement
topElement) in
c:\TEMP\tmp1532.tmp\src\Psi\src\resolve\AllNonQualifiedReferencesResolver.cs:line
14
at JetBrains.ReSharper.Psi.Resolve.Resolver.ProcessFile(IFile file) in
c:\TEMP\tmp1532.tmp\src\Psi\src\resolve\Resolver.cs:line 35
at
JetBrains.ReSharper.Daemon.CSharp.Stages.SmartResolverProcess.Execute() in
c:\TEMP\tmp1532.tmp\src\Daemon.CSharp\src\Stages\SmartResolver.cs:line 74
at JetBrains.ReSharper.Daemon.Impl.DaemonProcess.HighlightingProcess() in
c:\TEMP\tmp1532.tmp\src\Daemon\src\Impl\DaemonProcess.cs:line 272
--- End of inner exception stack trace ---

at JetBrains.ReSharper.Util.Logger.LogExceptionEx(Exception, String,
Boolean) in c:\TEMP\tmp1532.tmp\src\Util\src\Logger.cs:line 297 column 9
at JetBrains.ReSharper.Util.Logger.LogException(Exception) in
c:\TEMP\tmp1532.tmp\src\Util\src\Logger.cs:line 309 column 5
at JetBrains.ReSharper.Daemon.Impl.DaemonProcess.HighlightingProcess() in
c:\TEMP\tmp1532.tmp\src\Daemon\src\Impl\DaemonProcess.cs:line 312 column 9
at System.RuntimeMethodHandle._InvokeMethodFast(Object, Object[],
SignatureStruct&, MethodAttributes, RuntimeTypeHandle)
at System.RuntimeMethodHandle.InvokeMethodFast(Object, Object[], Signature,
MethodAttributes, RuntimeTypeHandle)
at System.Reflection.RuntimeMethodInfo.Invoke(Object, BindingFlags, Binder,
Object[], CultureInfo, Boolean)
at System.Delegate.DynamicInvokeImpl(Object[])
at AsyncHelper.DynamicInvokeShim(Object) in
c:\TEMP\tmp1532.tmp\src\Util\src\AsyncHelper.cs:line 63 column 3
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object)
at System.Threading.ExecutionContext.Run(ExecutionContext, ContextCallback,
Object)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object)





"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> wrote in message
news:c8a894d91009c68c7fe992b76b066@news.intellij.net...

Hello Patrick,

>

this indicates that some exceptions have happened and those exceptions
prevent
correct functioning. Could you please take a look at the log
(ReSharper|Show Log) and check
the latest stack traces there?

>
>

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

>
>> Hi Dmitry and Sergey,
>>
>> The problem suddenly reoccurred.
>>
>> Instead of the lightbulb, there very fast flashes an error message in
>> the status bar saying:
>>
>> 'More exceptions occur. You can continue working.'
>>
>> Or something like that, it is very hard to read.
>>
>> ALT + Enter shows the suggestion menu and the lightbulb, but in the
>> upper left corner of the editor instead of on the same line as the
>> cursor.
>>
>> Regards,
>> Patrick
>> "Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
>> news:dsi6r2$a0b$1@is.intellij.net...
>>
>>> Patrick,
>>> There exist a strange problem when R# wrongly detects, whether VS is
>>> actiove or not. Switching somewhere outside and back typically works.
>>> --
>>> Sergey V. Coox
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
>



0
Comment actions Permalink

Patrick,
This is a known problem, it will be fixed in build 218.
Thanks for your investigation.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.