Issues hosting WCF web service object in IIS

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hey group,

I have two things:

1. I'm trying to get my head around the real advantages of using WCF
web services as opposed to good-ol .asmx files. In less than five
minutes I can create a simple Hello World SOAP web service inside
an .asmx decorate my methods with [WebMethod], set a web reference
from another project and we're rolling

For WCF web services, I have to create a class library to house my
service, create an interface to house the Service/Operation Contracts,
create a static class for my templates, create transport classes...
Then create a console application to house my WebServiceHost. So the
effort here is multiplied many times and I guess I'm not understanding
why the development tools couldn't abstract all this a bit and what
the strong advantages are for incurring this additional effort as
billable time.


2. In my scenario I need to have ASP.NET compatibility set on my WCF
service
So I'm setting a reference to System.Web and adding this attribute to
my class
[AspNetCompatibilityRequirements(RequirementsMode =
AspNetCompatibilityRequirementsMode.Allowed)]

Great...

Now my problem is getting this thing hosted in IIS. I've created the
required .svc and created a web.config with the binding attributes
(again, why isn't there code generation tools for all this built into
VS.NET 2008? I digress). I guess I have two questions.

A. Aside from creating the .svc and web.config and putting these two
files in the directory along with your .DLLs is there any other
configuration that has to occur inside IIS? I've created a new
application and pointed it to my folder, but that's it.

For example:
http://localhost/myservice/service.svc/mycollection/collectionname/xml

Returns an IIS error.


B. Once a WCF service is deployed to IIS is there any way to attach to
this process and step-through debug?


Thanks in advance and I'm sorry if this is in the wrong group....
Answers greatly appreciated






.

Relevant Pages

  • Re: How to build a WCF service from an existing WSDL
    ... There are too many performance hit by using the ASMX, since IIS is ... processing large amout of data via web services. ... How will WCF help you? ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Some questions on what technology to use
    ... without IIS as some customers will not have it. ... Then you need to host the service in an HTTP server such as IIS. ... ASMX Web services using WSE. ... Weyer has worked in this space for Web services, ...
    (microsoft.public.dotnet.framework)
  • Re: Some questions on what technology to use
    ... without IIS as some customers will not have it. ... Then you need to host the service in an HTTP server such as IIS. ... ASMX Web services using WSE. ... Weyer has worked in this space for Web services, ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: What is the difference between WCF service and web service
    ... WCF "web services" are part of a much broader spectrum of remote ... communication enabled through WCF. ... ASMX is older than WCF, and anything ASMX can do so can WCF. ... Just wonder what is the difference between WCF services and web services? ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: How to build a WCF service from an existing WSDL
    ... are too many performance hit by using the ASMX, ... of data via web services. ... If we cannot use WCF, we will have to dump .Net ... WSDL in any way. ...
    (microsoft.public.dotnet.framework.webservices)