Webservice Error Unable to find System.Web

8 Dec 2006 9:39 PM

commanderjason

I have a webservice written in .net 2.0

I am able to view the web service info and wsdl without issue.

When I execute one of the methods directly from the webservice page
generated by .net I get an error.

System.InvalidOperationException: Unable to generate a temporary class
(result=1).
error CS0012: The type 'System.Web.Security.MembershipUser' is defined
in an assembly that is not referenced. You must add a reference to
assembly 'System.Web, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a'.

The project does have a reference to the System.Web assembly.
Everything compiles fine.

I have tried rebuilding the app, repairing the .net framework.
Everything I can think of.

Any help is appreciated.

11 Dec 2006 12:42 AM

Alvin Bruney [MVP]

Couple things, you need to match the version numbers and public token
against the dll you think is the correct one. If that pans out, you'll need
to make sure that the url that the web services is called from contains that
dll in the application folder.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless author plug
Excel Services for .NET is coming...
OWC Black book on Amazon and
www.lulu.com/owc

<commanderja***@gmail.com> wrote in message

Show quote

news:1165613964.746467.261180@79g2000cws.googlegroups.com...
>I have a webservice written in .net 2.0
>
> I am able to view the web service info and wsdl without issue.
>
> When I execute one of the methods directly from the webservice page
> generated by .net I get an error.
>
> System.InvalidOperationException: Unable to generate a temporary class
> (result=1).
> error CS0012: The type 'System.Web.Security.MembershipUser' is defined
> in an assembly that is not referenced. You must add a reference to
> assembly 'System.Web, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b03f5f7f11d50a3a'.
>
> The project does have a reference to the System.Web assembly.
> Everything compiles fine.
>
> I have tried rebuilding the app, repairing the .net framework.
> Everything I can think of.
>
> Any help is appreciated.
>