Resharper out of sync with Aspx

Hi, I've looked in the bug tracker, and couldn't find this issue, please correct me if it was already there.

I work on a -lot- of small to medium size asp.net web application (they're not web -sites-, though I've seen the same issue happen in web sites) in Visual Studio 2005 SP1.

An issue that I see happening more or less randomly, is Resharper flagging, all of a sudden -all- of my event methods as not found, even though the application compile, and the methods are clearly there. Making a change in the aspx (and then saving) almost always fix the issue. If it doesn't, I can simply keep adding spaces and saving 2-3 times, and bang, all fixed.

It seems that sometimes resharper simply forget to update itself. Clicking the button to reanalyse errors in the solution analysis window doesn't help.

If thats already fixed, or easy to fix, great! If not, would it be possible to have a button in the status bar that would have the same behavior as whatever happens when an aspx file is saved, so at worse we can refresh it manually?

I've had similar issues too when referencing DLLs from a different project (not part of the solution. Like, refererencing the assembly directly). If the DLL change (because I'm recompiling the assembly in a separate instance of Visual Studio), then resharper will get completly confused... 100% of the time, deleting the Resharper files in the solution directory fixes it. Again, if that issue cannot realistically be fixed (it is a weird scenario, I'll admit), especialy for performance reasons, a button to be able to redo the symbol cache would be great, instead of having to delete the files and reopening the solution to force resharper to do it :)

5 comments
Comment actions Permalink

Hello,

The first problem you mention is most likely fixed in the upcoming bugfix
update. You can try nightly builds to see if it works for you and let us
know. See http://www.jetbrains.net/confluence/display/ReSharper/ReSharper4.0Nightly+Builds

The other problem looks like a bug and we'll take a look at it, thanks for
letting us know.

Sincerely,
Ilya Ryzhenkov

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


IR> Hi, I've looked in the bug tracker, and couldn't find this issue,
IR> please correct me if it was already there.
IR>
IR> I work on a -lot- of small to medium size asp.net web application
IR> (they're not web -sites-, though I've seen the same issue happen in
IR> web sites) in Visual Studio 2005 SP1.
IR>
IR> An issue that I see happening more or less randomly, is Resharper
IR> flagging, all of a sudden -all- of my event methods as not found,
IR> even though the application compile, and the methods are clearly
IR> there. Making a change in the aspx (and then saving) almost always
IR> fix the issue. If it doesn't, I can simply keep adding spaces and
IR> saving 2-3 times, and bang, all fixed.
IR>
IR> It seems that sometimes resharper simply forget to update itself.
IR> Clicking the button to reanalyse errors in the solution analysis
IR> window doesn't help.
IR>
IR> If thats already fixed, or easy to fix, great! If not, would it be
IR> possible to have a button in the status bar that would have the same
IR> behavior as whatever happens when an aspx file is saved, so at worse
IR> we can refresh it manually?
IR>
IR> I've had similar issues too when referencing DLLs from a different
IR> project (not part of the solution. Like, refererencing the assembly
IR> directly). If the DLL change (because I'm recompiling the assembly
IR> in a separate instance of Visual Studio), then resharper will get
IR> completly confused... 100% of the time, deleting the Resharper files
IR> in the solution directory fixes it. Again, if that issue cannot
IR> realistically be fixed (it is a weird scenario, I'll admit),
IR> especialy for performance reasons, a button to be able to redo the
IR> symbol cache would be great, instead of having to delete the files
IR> and reopening the solution to force resharper to do it :)
IR>


0
Comment actions Permalink

Francois,

I've had similar issues too when referencing DLLs from a different project
(not part of the solution. Like, refererencing the assembly directly). If
the DLL change (because I'm recompiling the assembly in a separate
instance of Visual Studio), then resharper will get completely confused...
100% of the time, deleting the Resharper files in the solution directory
fixes it. Again, if that issue cannot realistically be fixed (it is a
weird scenario, I'll admit), especially for performance reasons, a button
to be able to redo the symbol cache would be great, instead of having to
delete the files and reopening the solution to force resharper to do it :)


Does it help to switch from Visual Studio to another application and back?
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Sorry, what do you mean by switching to another application and back? You mean simply changing focus from Visual Studio to, let say, Note-Pad, and coming back? So you guys can trigger some kind of "On Window Focus" event in the back?

0
Comment actions Permalink

Francois,

Sorry, what do you mean by switching to another application and back? You
mean simply changing focus from Visual Studio to, let say, Note-Pad, and
coming back? So you guys can trigger some kind of "On Window Focus" event
in the back?


Exactly. We process external to working VS changes once it gets focus. The
idea is not to process numerous small changes, that might occur, for
instance, when you update your project from version control.

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


0
Comment actions Permalink

I see, I will try that. Obviously it is happening once, since I am going from one instance of VS to another (maybe it confuses it though? are these events shared between instances?).

I however didn't have the problem today, I'll keep you updated next time it happen, I'll try it.

I still do vote for a button to force it. I don't think its humanly possible for you guys to make resharper work for every single weirdo scenarios that we may end up being forced into, especially in projects with poor development procedures implemented... so having buttons to "force refresh" is probably a better option than having resharper try and handle 100% of cases when some of them may very well never happen. I rather just hit something in my status bar to refresh the cache.

0

Please sign in to leave a comment.