Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
DotNet
acad.assignment.mngr
academic
adonet
aspnet
aspnet.announcements
aspnet.build.controls
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
clr
compactframework
component_services
datatools
distributed_apps
drawing
faqs
framework
framework.wmi
general
internationalization
interop
languages.csharp
languages.jscript
languages.vb
languages.vb.controls
languages.vb.data
languages.vb.upgrade
languages.vc
languages.vc.libraries
myservices
odbcnet
performance
remoting
scripting
sdk
security
setup
vjsharp
vsa
webservi.enhancements
webservices
windowsforms
windowsforms.controls
winforms.databinding
winforms.designtime
xml
  
 
date: Wed, 19 Dec 2007 19:17:31 +0100,    group: microsoft.public.dotnet.distributed_apps        back       


SOAP HTTP   
J'ai trouvé ceci sur msdn :

Donc il semblerait qu'il faudrait absolument passer par un server IIS et 
ASP.Net web services :

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>



aaa.aaa a écrit :
 > Bonjour,
 >
 > Je voudrais savoir si avec le DotNet framework 2.0, il serait 
possible d'écrire une application windows service qui incorporait un 
serveur HTTTP "embedded"( via code) sans passer par le serveur web IIS 
en local.
 >
 > Le but de l'application serait de consommer des messages SOAP sur 
HTTP contenant des objets ( décrit dans un schéma XSD) et de renvoyer 
des reponse contenant des objets serialisé avec xml ( via leur schema xsd )
 >
 >
 > Je ne voudrais pas à avoir à installer IIS et à passer par des web 
services car dans les messages SAOP il n'y aurait pas de déscription des 
méthodes mais la déscription des objets .
 >
 > Je voudrais connaitre les espaces de nom et les classes.
 > Ainsi qu'un exemple de code , ou des lien sur le web.
 >
 > Merci


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>
date: Wed, 19 Dec 2007 19:17:31 +0100   author:   aaa.aaa

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us