Recently, I turned on IIS components feature in the add/remove components under the Add/remove programs feature on a brand new windows 7 box.
The new windows 7 was stock and had the latest .NET frameworks available, but IIS was not configured.
I attempted to published a WCF service to my local host, after jumping through a few hoops, I was able to publish the WCF service to my local host.
Then, I saw that none of the handler mappings were installed nor the modules nor the default modules for .aspx or .svc files. No wonder, my wcf service was not running.
After some research on the net, thanks to google. I found that that TURNING ON IIS COMPONENTS IN THE ADD/REMOVE PROGRAMS does not install or register the ASP.NET components. I had assumed all of them would automatically be installed, but not.
So, it was a simple matter of navigating to c:\windows\microsoft.net\framework\version\and running aspnet_regiis.exe -i.
That was it, my WCF service started working.
Enjoy, hope this titbit helped others.
The new windows 7 was stock and had the latest .NET frameworks available, but IIS was not configured.
I attempted to published a WCF service to my local host, after jumping through a few hoops, I was able to publish the WCF service to my local host.
Then, I saw that none of the handler mappings were installed nor the modules nor the default modules for .aspx or .svc files. No wonder, my wcf service was not running.
After some research on the net, thanks to google. I found that that TURNING ON IIS COMPONENTS IN THE ADD/REMOVE PROGRAMS does not install or register the ASP.NET components. I had assumed all of them would automatically be installed, but not.
So, it was a simple matter of navigating to c:\windows\microsoft.net\framework\version\and running aspnet_regiis.exe -i.
That was it, my WCF service started working.
Enjoy, hope this titbit helped others.