Re: non-asp.net web services

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello CJF,

If you do not want to host your service in IIS, As Robert has suggested,
..NET 2.0 + Indigo supports hosting WebServices in custon ASP.NET process.

For .NET 1.1, Dino Esposito has written a Nice article in msdn about how to
host you service in a smallscale IIS called cassini... I have not read that
article in detail . PLease have a look in that it might help you.

http://msdn.microsoft.com/msdnmag/issues/03/01/cuttingedge/

Thanmks
Ram






"CJF" wrote:

So it sounds like out-of-the-box you can't host a remoting type as a web
service within your own managed executible. I will look more into the WSE 3.0
and see how it fits my needs. Thanks!

"Robert Wilczynski" wrote:

Hi,

Using VS 2005? Have a look at WSE 3.0 (Web Service Enhancements). Using the
features it provides you will be able to host the web service in windows
apps, console apps or windows services (which will probably be your choice):

http://msdn.microsoft.com/webservices/webservices/building/wse/default.aspx
http://msdn.microsoft.com/webservices/webservices/building/wse/default.aspx?pull=/library/en-us/dnwse/html/newwse3.asp
(this atricle has a paragraph on hosting serices outside IIS)

You could also use WCF (Windows Communication Foundation - final version
coming with Windows Vista, but available with a Go-Live license meaning you
can use the CTP builds in production environment now) to achieve the same:

www.windowscommunication.net

Hope this helps.

Best regards,
Robert Wilczynski.

I'm trying to build a web service via .NET remoting (without ASP.NET)
using a pre-existing wsdl file. It doesn't seem to be a very
straight-forward process, as SOAP exceptions keep popping up that
don't appear if I do use the ASP.Net approach. My remoting type looks
exactly like the output of the wsdl.exe utility when executed against
the same wsdl file, so I'm not sure why it's complaining about the
soap message. I don't get these exceptions using the ASP.Net approach.

I've tried googling for information about building non-ASP.Net web
services.
Specifically, I want to use remoting to listen for inbound xml
messages
using SOAP from non-.NET clients. I want to eliminate the need for a
web
server (IIS or any other web server). Is remoting possible in this
situation? Normally remoting is allowed between two .NET endpoints,
but since
I'm passing SOAP requests I was hoping this was the exception to that
rule.
Do I have any other options to hosting web services in my own process
without
the need for a seperate web server to communicate with non-.NET
clients?
Thanks,
CJF



.

Relevant Pages

  • Re: Remoting Hosts
    ... JBOSS) that can be used to host EJBs ... What are the options with .NET remoting? ... You can host objects in a service, desktop app, IIS, or COM+. ... You can integrate COM+ into your remoting object. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Singleton and IIS
    ... Hosting a stateful remoting server under IIS is certainly possible but does ... > I'm now wondering if i could host this .NET Remoting component in IIS. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: [Newbie] What are ASP.NET and ADO.NET ?
    ... You DO need XP pro (or a server version) to run IIS, ... necessary for hosting ASP.NET. ... IIS certainly *won't* run on XP home - I've ... it depends on whether by "to run ASP.NET" you mean to actually host ...
    (microsoft.public.dotnet.languages.csharp)
  • port 80
    ... How can I have my application running on port 80 while ISS and other ... for remoting (without hosting it in IIS) and or simply using sockets. ...
    (microsoft.public.dotnet.languages.csharp)
  • experiment supports concept of using host header names as securit y layer
    ... ISAPI filters can't evaluate a request until a virtual site has been ... selected and its set of running ISAPI filters has become known to the IIS ... As a quick experiment in using a host header name as a security device, ...
    (Focus-Microsoft)