WSE 3.0 Interoperability with client platform and technologies



Hi

I am preparing to use VS2005 and WSE 3.0 create a Web Service that is
fully platform independent, from MSDN it seems WSE3.0's
"Interoperability is not guaranteed with protocols such as TCP", any
ideas what may be interoperability problem?
Also my main concern is that whether or not a http web service
developed by VS 2005 and WSE 3.0 hosted on IIS can be real platform
independent?

Any comments suggestions?

Thanks in advance.
.



Relevant Pages

  • Re: How to call Web Service Securely
    ... Maybe I am complicating WSE too much - can you point me to a simple ... you could provide a logon screen in the client app and create a NetworkCredential ... tokens - but that is tied to .NET 2.0 ... make a web method via dialup to my IIS Web Service. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: VBA access to WSE web service?
    ... \par Yes, you're right, COM interop is one possible approach as long as the client machine also has .net framework and WSE installed... ... \par Microsoft Online Support ... \par Subject: Re: VBA access to WSE web service? ... \par>Regarding on the calling WSE protected XML Webservice through Office ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE Settings 3.0 problems (Soap protocol factory)
    ... guessing it is a configuration issue of the solution I'm trying to create. ... when I try to create a totally new Web Service project using the ... I assume you downloaded the WSE 3.0 Enhancements from MS: ... Soap Protocol Factory" is greyed out. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • RE: Web Service Security
    ... You could encrypt or hash your ... As far as web service authentication/authorisation is concerned you would be ... WSE does a pretty good job of abstracting away most of the ... a windows domain account). ...
    (microsoft.public.dotnet.framework.webservices)
  • Asychronous web service call using WSE 3.0
    ... I need to make multiple simultaneous asynchronous calls to a web service ... proxy.FooCompleted += new FooCompletedEventHandler; ... That is when we call the web service without using WSE. ... // Distinguish among asynchronous operation by providing a unique ...
    (microsoft.public.dotnet.framework.webservices.enhancements)

Loading