
Signature
Manohar Kamath
Editor, .netWire
www.dotnetwire.com
Hi Manohar,
Thanks for your reply. Yes, I did use the "/server" switch because I
thought that's what I was supposed to do to generate the server stubs. When
I saw that the tool generated an abstract class and methods, and saw the
comments in the file warning not to modify the file, it seemed to make sense.
I would override the class/methods in a separate file in the VS.NET project,
and then "somehow" .NET would hook my method overrides into the service at
runtime. When it built successfully I thought I was on the right path.
So there's really no way to use/override the abstract class generated for
the server side when using the "/server" switch? I can't believe the tool
would produce something unusable. Is the abstract class just supposed to be
some sort of "guide"? This problem seems so basic that I thought surely
someone must have hit this problem (and hopefully solved it) before.
Anyway, thanks again - I do appreciate the help so far.
Dave
> I guess you are using the /server option when you are creating your proxy
> class. It will create an abstract class. If you exclude it, you will get a
> concrete class.
>
> wsdl http://myhost/mywebservice.asmx?wsdl
drb - 25 Mar 2005 16:27 GMT
I finally found this. The posted text is about 3/4 of the way through the
article.
---------------------------------------
http://msdn.microsoft.com/msdnmag/issues/02/09/XMLFiles/
"When you derive your new class, make sure that you copy all of the
customization attributes from the generated class to the derived class
(including those on each method). The customization attributes are not
inherited by design. Overlooking this step will break the WSDL contract that
you started with. Then to finish off the implementation, you simply need to
create an .asmx file with a single ASP.NET directive referencing your new
class, like so:
<%@ WebService language="C#" class="GeometryServiceImpl" %>
---------------------------------------
This was exactly what I had been hoping to find. I tried it and it worked.
Hope this helps someone else who's trying to start from scratch with WSDL and
generate the interface for both sides of the wire.
Manohar Kamath - 25 Mar 2005 18:51 GMT
Dave,
From my previous post -- do not use the /server option when using wsdl. The
generated class will be a concrete class that you could use as-is.

Signature
Manohar Kamath
Editor, .netWire
www.dotnetwire.com
> Hi Manohar,
>
[quoted text clipped - 21 lines]
> >
> > wsdl http://myhost/mywebservice.asmx?wsdl