Groups | Blog | Home
all groups > dotnet distributed apps > december 2007 >

dotnet distributed apps : Host an SOAP - HTTP windows service application Outside of IIS


aaa.aaa
12/19/2007 7:01:39 AM

Hello,

I wonder whether with the DotNet framework 2.0, it would be possible to
write a windows application service which incorporated a server HTTTP
"embedded" (via code) without using IIS locally.

The purpose of the application is to consume SOAP messages over HTTP
containing objects (described in a blueprint XSD) and return reply
containing objects serialisé with xml (via their XSD schema)


I do not want to have to install IIS and go through web services as in
the messages SAOP there would be no description of methods, but the
description of objects.

Let me know namespaces and classes.
As one example of code, or link on the web.

Thanks


I just find this on MSDN so I think maybe is not possible.
I have to use IIS & ASP Web Services

What do you think ?

http://msdn2.microsoft.com/en-us/library/aa529311.aspx

How to: Host an ASP.NET Web Service Outside of IIS

The Web Services Enhancements for Microsoft .NET Framework (WSE) enables
ASP.NET Web services to be hosted in console applications, Windows
services, COM+ components or Windows Forms applications and then be
called using the TCP protocol or any custom transport protocol written
for WSE.

.............

When a Web service is hosted outside of IIS, some of the programming
elements that are specific to HTTP are not available. The
System.Web.HttpContext.Current property is one example of this. The
following paragraphs summarize the other elements that are not available.

The following properties of the System.Web.Services.WebMethodAttribute
attribute cannot be used by a Web service that is hosted outside of IIS.

* BufferResponse
* CacheDuration
* EnableSession
* TransactionOption

The following configuration elements cannot be used by a Web service
that is hosted outside of IIS.

* <serviceDescriptionFormatExtensionTypes>
* <soapExtensionTypes>
* <soapExtensionReflectorTypes>
* <soapExtensionImporterTypes>
* <wsdlHelpGenerator>
Bryan Phillips
12/22/2007 8:01:14 PM
The easiest way to do this would be to use WCF since it does not require
IIS and reduces the complexity of hosting the web service inside Windows
Service.

--
Bryan Phillips
MCT, MCSD, MCDBA, MCSE
Microsoft MVP - Client Application Development
Blog: http://bphillips76.spaces.live.com
Web Site: http://www.composablesystems.net



[quoted text, click to view]
AddThis Social Bookmark Button