Do ASMX or WCF Proxy clients use IO completion ports?

I'm in the middle of performance testing a critical section of my project, when I notice a whole lot of extra threads being used to to perform WaitOrTimerCallback operations. 

On closer inspection I can see that these are being spawned by my ASMX client proxy class for operations on a remote server.

I was under the impression that these were using IO completion ports like all of my other asynchronous IO Calls.

Installing WCF on IIS6

I have finally reinstalled WHS (Windows Home Server), now the tricky bits: Getting WCF and MVC working correctly.

Getting WCF Working

1. Install the latest .Net framework (3.5 SP1 in this case)
2. Launch a Command Prompt with full privileges

Right click on the command prompt short cut in the start menu

Uncheck 'Run this program with restricted access'

1. Go to 'C:\Windows\Microsoft.NET\Framework\v2.0.50727'
2. Run aspnet_regiis -i
3. Add a new web-site in IIS, check to see if the .svc extension is now available

1. The .svc extension is now appearing, if your WCF service is in a web-site that already exists (Default web-site etc) then just copy and paste the .svc information into the properties of your website.  Otherwise when you create your new site it should be working.

WCF and IIS 6.0 Hosting Issue

I've developed a WCF Service which I have tested extensively in the Visual Studio environment.  I have had it successfully hosted on Vista and also Windows XP.

Today when I attempted to install the Service on my windows Server 2003 machine, it refused to display the .svc file.  It would only return a 404 error.

After much stuffing around I found this resource which described the same problem I was facing. (Always nice to know you are not alone!)

The only method that worked for me was uninstalling and reinstalling IIS.  I then repaired my .NET 3.5 SP1 installation and Vola! A visible svc and wsdl file!

Wow what a waste of an afternoon that was!