HighTechTalks DotNet Forums  

Host an SOAP - HTTP windows service application Outside of IIS

Dotnet Distributed Applications microsoft.public.dotnet.distributed_apps


Discuss Host an SOAP - HTTP windows service application Outside of IIS in the Dotnet Distributed Applications forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
aaa.aaa
 
Posts: n/a

Default Host an SOAP - HTTP windows service application Outside of IIS - 12-19-2007 , 01:01 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>


Reply With Quote
  #2  
Old   
Bryan Phillips
 
Posts: n/a

Default Re: Host an SOAP - HTTP windows service application Outside of IIS - 12-22-2007 , 03:01 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



"aaa.aaa" <aaa.aaa (AT) aaaa (DOT) net> wrote


Quote:
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


Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.