R#6 : Not recognizing web references

OK, where's the magic switch to make R# 6 recognize my web references???
WWW - Microsoft Visual Studio.png
Steps to reproduce:

  • Create an empty web-site project;
  • Add a web reference;
  • Write some code which uses the web reference;
  • Save and close the project;
  • Re-open the project;


Expected results:
The code builds and runs without any problems, so R# should not indicate any errors.

Actual results:
R# hilights all usages of the web reference as an error.

Clearing the caches has no effect.
Restarting VS2010 has no effect.
Refreshing the reference has no effect.
Removing and re-adding the reference has no effect.
Re-creating the solution file has no effect.

This has been a problem for several major versions now. I can't believe it's still not fixed! :(

19 comments
Comment actions Permalink

Hello Richard,

Thank you for detailed report! However, I wasn't able to reproduce this behavior.
Could you please attach a sample solution (which would also contain ReSharper
cache) which exhibits this behavior?

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

In case it helps, the reference I'm using is:
http://www.postcoderwebsoap.co.uk/websoap/websoap.php?wsdl
---
Original message URL:
http://devnet.jetbrains.net/message/5309124#5309124



0
Comment actions Permalink

I'm having the same issue since upgrading to version 6: the web references are no longer recognized. I have tried deleting the cache (manually and via options) but it's still the same. Could you please advise? Thank you.

PS: I have both visual studio 2008 & 2010 installed, this is only happening in vs 2008.

0
Comment actions Permalink

Hello,

Could you please attach a small sample solution demonstrating this problem?
Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I'm having the same issue since upgrading to version 6: the web
references are no longer recognized. I have tried deleting the cache
(manually and via options) but it's still the same. Could you please
advise? Thank you.

---
Original message URL:
http://devnet.jetbrains.net/message/5309222#5309222



0
Comment actions Permalink

Andrey,

Unfortunately, I can't seem to reproduce this in a new empty solution.The solution which is affected is 150Mb, with a 12Mb R# cache, and contains a lot of proprietary code which I can't share.

I did have this problem with R#5 when I first added the reference, but a combination of clearing the caches and restarting Visual Studio seemed to resolve it. Since I've upgraded to R#6, nothing I do will make R# recognize the service reference.

0
Comment actions Permalink

Hello Richard,

Could you please check if the following combination helps:
1. Delete the web reference from your project
2. Close Visual Studio
3. Delete ReSharper cache
4. Reopen your solution
5. Re-add the web reference

Let me know if this helps. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

a



0
Comment actions Permalink

It worked initially, but when I closed and re-opened the solution, R# had lost the reference again.

0
Comment actions Permalink

All the developers in our department also have the same problem and I'd like to expand on Richard's steps to reproduce in hopes that JetBrains can reproduce this issue. It is really bothersome when you know you will never get a green code analysis.

Steps to reproduce:

  • In Visual Studio 2010 create an empty web-site by clicking File > New > Web Site... (not Project)
  • Select Visual C#, select ASP.NET Web Site, .NET Framework 4, Web location: set to File System.
  • Add a web reference by right-clicking on project > Add Service Reference... > Advanced... >  Add Web Reference... > enter URL:

    http://www.postcoderwebsoap.co.uk/websoap/websoap.php?wsdl

  • Change Web reference name to PostCoderWebSOAP.

  • Open Default.aspx.cs
  • Just add  using PostCoderWebSOAP;
  • Build the project just to make sure.
  • Close the solution (File > Close Solution).
  • Reopen the solution (File > Recent Projects and Solutions > [First Item]).


The using directive is dimmed and red and tooltip says, "Cannot resolve symbol 'PostCoderWebSOAP'...".

I so hope you can reproduce this now. Remember, don't create a web project, create a file based Web Site.



Attachment(s):
WebRefProblem.zip
0
Comment actions Permalink

Hello Mark,

Thank you for detailed repro steps! I've followed them exactly and it still
works fine for me. I've created a bug-report in our tracker: http://youtrack.jetbrains.net/issue/RSRP-273951
and assigned it to our QA engineer for further investigation. You can track
the progress there.

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

http://devnet.jetbrains.net/message/5310302#5310302



0
Comment actions Permalink

I'm using a Service Reference rather than a Web Reference, but it's probably the same issue.
(Although, given the hoops I had to jump through to make WCF work with a service which uses ISO-8859-1, I'm starting to wish I'd used the older approach!)

Could this be a timing issue? Is R#6 picking up the dependencies before VS2010 has finished generating the service reference code?

0
Comment actions Permalink

Still can't reproduce? Dang!

Well, here are the versions I'm using. Not sure if that would affect this or not.

Visual Studio 2010 Professional Version 10.0.40219.1 SP1Rel
ReSharper 6.0.2202.688

0
Comment actions Permalink

I'm having the same problem with a web reference.  With R# 6 on, the web services classes aren't recognized and intellisense doesn't work for those classes.  Interestingly, if I suspend R#, the VS intellisense immediately recognizes the classes and intellisense for those classes works again.

0
Comment actions Permalink

Mark, unfortunately I can't reproduce it neither with R# 6.0 release build nor R# 6.1 development build. Any working sample solution could be very useful for us.
Thanks in advance!

Kirill Falk

0
Comment actions Permalink

Hi Guys

I am having exactly the same problem, If I delete the web reference and recreate it all works fine. However after I close sln and reopen I get the following:-

Capture.PNG
The web reference I am connecting to is, https://b2b-email.net/apicrm1/webCRMAPI.asmx

However sln builds fine

0
Comment actions Permalink

Richard, what source control system are you using in your working solution? It could be timing issue, so if it's possible please try to turn source control off and try to reload solution.
Thank you.

0
Comment actions Permalink

I don't have any source control on that particular solution yet.

(I know - I'll get around to it some day, honest! :8})

It's a fairly large project - 16 bin-deployed references, 37 code files in App_Code, ~150 pages and controls, ~40 javscript files, and ~50 css files.

0
Comment actions Permalink

I am using AnkhSVN - Subversion Support for Visual Studio.
However I am relunctant to remove this plugin as it requires me to install/uninstall via Windows Add/Remove.
Can you test this yourselves first for me as I don't want to mess with my setup on my main dev box.
Also after reading latest comment I can't see why this would affect it as ALL my other solutions don't have this problem

0
Comment actions Permalink

OK R#6 I think I can replicate the problem.

I have a ASP.NET Web Application
I have created a folder called "App_Code" (not a special folder as Web applications can't create App_Code special folders)
Inside this App_Code folder I got some classes without Namespaces defined (naughty I know)

This seems to cause the fault, as soon as I added the namespaces r#6 started behaving nicely and could see my webservcies.

I undertand that really the App_Code folder should be a seperate project, but I inhertied this and am slowly cleaning it up!

0
Comment actions Permalink

Hi, Richard

Great news! Could you please send me your demo solution? I've tried your case but still can't reproduce this.

Kirill Falk

0

Please sign in to leave a comment.