Windows Activation Hosting (WAS) and WCF
A few years ago, I took a job at Tiba Solutions . One of the coolest things about that job was working with Tobin Titus. Tobin is pretty much a bad a55 at all sorts of things and one of the things he really rocked at was Remoting. I learned most of what I know from him. He has long since left Tiba as have I and moved on to greener pastures. Currently he's at Microsoft. Now that I've sucked up enough to Tobin hopefully I can get him to explain to me how to get my GD WCF service configured properly to run in IIS 7.0 under WAS.. So if I run appcmd.exe from the VS Command Line, this file is generated and all is good. If I create a new site and do this manually, it bombs on me telling me the target machine is actively refusing my connection. I can't see any difference for the life of me. Does appcmd.exe do something else critical that I'm missing?
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.applicationhost>
<sites>
<site name="CuckooClock" id="1">
<bindings>
<binding protocol="http" bindinginformation="*:80*"/>
<binding protocol="net.msmq" bindinginformation="*"/>
<binding protocol="net.tcp" bindinginformation="*"/>
<binding protocol="net.pipe" bindinginformation="*"/>
</bindings>
</site>
</sites>
</system.applicationhost>
</configuration>