Cannot resolve symbol (global ressource)

Hi, I -know- this has been reported before, I've seen the thread (not long after 4.1 came out), and I honestly cannot find it, nor can I find it in the issue tracker, so maybe someone can point me in the right direction for the status on this.

Since 4.1 (it worked fine in 4.0), I have issues where ressources (namely, globals) are not picked up by Resharper, which leads to a "Cannot resolve symbol" error in the ASPX (if using the ressource explicitely in markup) or in code (if using the strongly typed ressource accessors).

Anyone can point to me to a thread discussing this or to the issue in the tracker, please? :)

Thank you very much.

-Francois

10 comments

Francois,

Could you create a sample solution for us?
You're welcome to contact me directly at qx jetbrains com
--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

I attached a zip with the simplest possible solution for it. Its simply making a web app, adding a -global- resource (no problem with local resource), and referencing it through the <%$ Resource:SomeFile,SomeName %> syntax. Same problem via strongly typed resource. Its a 100% reproduce no matter the machine or scenario, as far as I can tell (at least with a web application. I didn't try with a web site. VS2005)

Like I said though, this has been reported a little bit after 4.1 came out, so its nothing new, and I vaguely remember you saying it was worked on (not sure). I was just searching the forums and issue tracker to find the status of it all, but couldn't find it :)

-Francois



Attachment(s):
Sample.zip
0

Francois,

Thanks for the sample. The upcoming nightly will contain the fix. It will be
available at
http://www.jetbrains.net/confluence/display/ReSharper/ReSharper4.0Nightly+Builds

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


0

Yup, works perfectly fine now. Finally my solution "green lights" again. It had been a while :)

0

Oh, and I just noticed: with the fix, we end with a somewhat reversed situation: the -local- resource syntax never show as error anymore.

So if I have <%$ Resources: SomeResourceKey %> (as opposed to the global syntax I sent you in the sample), that will -never- flag an error, even if the resource is not found (it used to work).

This is not a show stopper for me though. I prefer false positives to false negatives, but I figured I'd let you know.

Thanks,

-Francois

0

Francois,

I'm pretty sure, it never worked. I'll check it anyway. Thanks for feedback.

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


0

If it never worked, then you can just treat that as a low priority feature request then :)

Thanks for the quick feedback. I'm still happy at how quickly the fix for the global ressource went through!

0

Hi

Hm... I still got the same behaviour here with R# 4.1.
I have GlobalResources labels.de-ch.resx and access it via <%$ Resources:labels, foo %>. At runtime it works perfect, but R# marks it as an error (Cannot resolve Symbol 'labels').

Hints?

0

Daniel,

Could you send us a sample solution for investigation?

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


0

I'm using R# 4.1 and still have issues with this. (Also with the sample app uploaded here).

0

Please sign in to leave a comment.