title: .svc handler mappings for .Net 2.0 app pool working after a .Net 3.0 install?
body: <p>This is odd.  I have a website running under a .Net 2.0 app pool (Integrated mode) and couldn't connect to a WCF service on the site.  A message reading "The requested content appears to be script and will not be served by the static file handler" would pop up whenever I navigated to the URL on my box.</p>
  
  <p>I checked the handler mappings in IIS for this website's .svc extension and saw entries reading <code>svc-Integrated-4.0, svc-ISAPI-2.0- and svc-ISAPI-2.0-64</code>.  But nothing for svc-Integrated, which I assume was the problem.</p>
  
  <p>I followed the ServiceModelReg -i recommendations in <a href="http://blogs.microsoft.co.il/blogs/bursteg/archive/2008/12/01/wcf-on-iis7-on-vista-adding-svc-handler.aspx" rel="nofollow">this post</a>, but there was no instance of that executible in my Framework\v2.0.5027 subfolder.  So I went up a level and found it in my Framework\3.0.0 folder, and ran it from there.  Lo and behold, things work now and there's a new handler for svc-Integrated in the mappings section.  </p>
  
  <p>But my question is: if I installed this for .Net 3.0, how is a .Net 2.0 app pool making use of it?  I thought there would be a compatibility issue?</p>