Problem with MessageName and .NET ISAPI handler

Problem with MessageName and .NET ISAPI handler

Post by Damien Foggo » Thu, 14 Nov 2002 23:06:32

I've got an overloaded method in a web service and have used MessageName to
give the messages different names when in the WSDL file.  The function
signatures are as follows:

<WebMethod(MessageName:="Overload1")> Public Function GetReleaseDate(ByVal
objDetails As ArtistAlbum) As String
<WebMethod(MessageName:="Overload2")> Public Function GetReleaseDate(ByVal
strArtist As String, ByVal strAlbum As String) As String

When I create the proxy in VS.NET the two methods are created correctly with
the name GetReleaseDate with the correct signatures.  Now if I look at the
ASMX file in IE the two overloaded methods have names that are the values of
MessageName rather than the names of the methods.

It seems that the ASMX parser is picking up the MessageName and using that
when it shouldn't?  Does this look like a bug to anyone else?



1. WebDAV Handler/ISAPI Filter/HTTP Modules

My group needs to implement a custom WebDAV interface.  i.e. we need to by
pass Microsoft's handling of a WebDAV request and send that request to our
own DMS system.  Is this something that can be done using C# and HTTP
Modules or does it have to be implemented as a C/C++ ISAPI Filter?

  Marcus Kellermann

2. using windoze defaults (was poll: user-defined read-only macr o variable)

3. MessageName attribute on WebMethod

4. Inverse algorithm of Chan and Ho's DCT?

5. writing ISAPI filter/extension using .Net

6. Validation - Databasepainter

7. problem with "$" in XSL ISAPI

8. ZAP & Windows XP- no True Vector in MSCONFIG?

9. Problem on Debuging ISAPI Filter

10. ISAPI Extension in .NET

11. Filtros Isapi en .Net