ambiguous erros with App_webreferences folder and with use of .wsdl files

I am woking with couple of projects that are "web sites" type of projects. One of them is used for web service strictly and the other is web site(aspx pages). The web site projects makes use of web services. Which then contains App_Webreferences folder with .wsdl files(for all of the web services). By the way both of these projects are web service 3.0 enabled.

My problem is that in the entire project(web site) where a reference is made to web service call I get error or or red indicator on the side becuase the proxy class is not in the project. Visual studio 2005 seems to build both of these projects just fine because it seems to create proxy partial class in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\ directory. Also it seems like the resharper is trying to use some information from .wsdl files out of App_Webreferences folder but I get lot of ambiguous reference all over. Is there any solution to this. It would seems like resharper should look for this proxy partial class generated by visual studio in Temporary ASP .NET files\ directory to resolve rather then .wsdl file in App_webreferences file.

13 comments
Comment actions Permalink

By the way, I am using resharper 3.1 full edition build 3.1.584.3.

0
Comment actions Permalink

Could you create a sample solution for us?

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Sunpat" <no_reply@jetbrains.com> wrote in message
news:6288810.1204427781269.JavaMail.itn@is.intellij.net...
>I am woking with couple of projects that are "web sites" type of projects.
>One of them is used for web service strictly and the other is web site(aspx
>pages). The web site projects makes use of web services. Which then
>contains App_Webreferences folder with .wsdl files(for all of the web
>services). By the way both of these projects are web service 3.0 enabled.
>

My problem is that in the entire project(web site) where a reference is
made to web service call I get error or or red indicator on the side
becuase the proxy class is not in the project. Visual studio 2005 seems
to build both of these projects just fine because it seems to create proxy
partial class in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary
ASP.NET Files\ directory. Also it seems like the resharper is trying to
use some information from .wsdl files out of App_Webreferences folder but
I get lot of ambiguous reference all over. Is there any solution to this.
It would seems like resharper should look for this proxy partial class
generated by visual studio in Temporary ASP .NET files\ directory to
resolve rather then .wsdl file in App_webreferences file.



0
Comment actions Permalink

Attached is a sample solution. It contains following projects:

1) WebService - type of web site project, contains web services
2) WebSite - type of web site project, contains aspx pages.
3) ConselApplication1 - type of console application.

Please be sure to have WSE 3.0 installed.

Also, be sure to configure project 1 and project 2 to use custome server(right click on project, property pages, start options on left, server - use custom server, http://localhost/SandBox/WebService/ and http://localhost/SandBox/WebSite/ for project 2). I have also created virtual directory in IIS.

Notice, how WebSite(2) project's default.aspx file has errors and warnings vs. ConsoleApplication does not. The reason being the WebSite(2) project is parseing .wsdl file and not the partial proxy class that is generated in temp directory I think. Also, notice how Employee class has ambiguous references in Default.aspx. Once again, because it is referencing .wsdl file and not the partial proxy class generated in temp directory. This is not an issue with console application becuase it is parseing the proxy class generated inside project.

We currently utilize setup such as projects 1 and project 2 in our application and it is causing lots of erros all over the files.

Thanks



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

Sergey,

thanks for taking look at the post that posted. I was wondering if you had chance to look at it and wheather you had any recomendation. Thanks.



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

Thanks a lot for the sample. I'll look at it ASAP

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


0
Comment actions Permalink

Sunpat,
Please, try tomorrow's 4.0 nightly.

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


0
Comment actions Permalink

Thank you very much for looking at it. I downloaded 4.0.783.45 build and installed it. I opened my Sandbox or example solution that I provided on this thread and it seems to be fixed there. However, when I open our real project it does not seems to resolve webservice folder.

So, to be more clear, our website application has 'ABCWebService' folder under App_WebReference and about 31 webservice/.wsdl file reference. What I think is happenning is that it can not analyze ABCWebService folder completely or becuase it is showing up as error or red. I have 'using ABCWebService;' statement but now its read.

I posted some bugs in jira ticket that I was getting as I started my solution/projects and when I did a solution wide analysis. I believe I have also gotten simler errors on 3.0 release. just for info.


RSRP-67114 at WhitespaceNodeType.Create : Exception of type 'System.OutOfMemoryException' was thrown. Unassigned sunpat Submitted UNRESOLVED 02 May 08 02 May 08
RSRP-67113 at ArrayOfTokens.ProvideSpaceFor : Exception of type 'System.OutOfMemoryException' was thrown. Unassigned sunpat Submitted UNRESOLVED 02 May 08 02 May 08
RSRP-67112 at ProjectImpl.GetChangeDelta : Exception of type 'System.OutOfMemoryException' was thrown. Unassigned sunpat Submitted UNRESOLVED 02 May 08 02 May 08
RSRP-67111 at TextInfo.nativeChangeCaseString : Exception of type 'System.OutOfMemoryException' was thrown.

0
Comment actions Permalink

Sunpat,

Could you create a small sample that looks exactly as your website? Or maybe
its possible to send the website to me directly for investigation?
We are ready to sign any NDA if necessary.

I posted some bugs in jira ticket that I was getting as I started my
solution/projects and when I did a solution wide analysis. I believe I
have also gotten simler errors on 3.0 release. just for info.

These out of memories appear if you use solution-wide analysis only? Or they
also happen while regular work?

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


0
Comment actions Permalink

Thanks for replying.

The Sandbox soultion that I have uploaded is the exact layout we have for our real application. A "WebService" project containing about 31 webservices(31 .asmx and .cs files, each one containing quite of few operations and several large objects passed in as parameters) files.

The "WebSite" project, just like in sandbox solution, consumes thoses webservices and references on several .aspx(quite a few, fairly large website) pages. Just like in Sandbox solution, "WebSite" project contains a folder called Webservices under App_WebReferences and each one of those 31 webservice is referenced here.

The outof memory errors seems to happen with regualar work as well. Also, in 3.1 release whenever I do Update WebReference by righ clicking on App_webReferences/WebServices folder, I get these errors then as well.

Hope this helps.

0
Comment actions Permalink

Do you experience problems other than OOM exceptions?

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


0
Comment actions Permalink

Mainly just OOM exceptions and majority of time after doing Web Reference Update or soon there after.

0
Comment actions Permalink

Hello Sunpat,

Please try latest ReSharper 4 nightly build, like build 804. We've fixed
a number of memory issues in latest builds.

Sincerely,
Ilya Ryzhenkov

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


IR> Mainly just OOM exceptions and majority of time after doing Web
IR> Reference Update or soon there after.
IR>


0
Comment actions Permalink

Ok. I think I have some more info for you.

I have downloaded RC3 candidate 4.0.818 release and seems to be working pretty good. Lot of the memory related problems have been solved. I am no longer getting out of memory exception.

There is still seems to be couple of problems left related to website type of project that I mentioned in my sandbox solution. The red error has seems to be gone when you reference "WebServices.TheActualService" if the WebServices.cs file does not have lots of lines of code or not many web services.

However, it seems to be a still a problem if WebServices has quite of few services. In our real project the WebServices.cs(proxy class) file that was generated by .Net has 47,260 lines of code with quite of few Types referenced in it. In this case it still displays red erros all over.

Lastly, in a given soultions if you have multiple website projects, and you created WebServices(basically referencing our webservice layter) folder in both website project. Then you will get ambiguous erros etc...

0

Please sign in to leave a comment.