In WCF, I'm taking an approach I quite like. I've got my Contracts /
Interfaces / Messages defined in a standard .Net DLL. This lets me write
Unit Tests, and do all the other basic stuff. I then build host projects to
host it where I need.

To expose the service through IIS, I create a Web Project, and add in an
".svc" file that looks like:

<%@ ServiceHost Language="C#" Debug="true"
Service="MyStuff.Services.MyService1"%>

That's the sum total of the "expose to IIS" that has to go in there. The
reference to MyService1 is found in the config file:
<services>
   <service name="MyStuff.Services.MyService1">
       ...
   </service>
</services>

I then deploy to IIS the .scv file, the config file, and the DLL's that
contain my WCF classes.

It's really quite slick, and (in my opinion) a big jump forward over what
Web Services have been in the past. It no longer feels like a big ugly mess
that's going to be unmatinainable in the long-term.

--
Chris Mullins