title: Best practices for testing a netTcp WCF service at development environment
body: <p>I have got a <code>netTcp</code> WCF service. This service will be hosted at IIS 7.5 at production time.</p>
  
  <p>But is it necessary to install IIS 7.5 also at the development machine to debug the service?
  I'm not able to use the built-in <code>Cassini</code> server or <code>IIS Express</code>, because both do not support <code>netTcp</code>. I don't have a good feeling when installing a full web server just for debugging, so I want to know if there are any other possibilities.</p>
  
  <p>How do you debug <code>netTcp</code> WCF services?
  Of course there are several options:</p>
  
  <ul>
  <li>Install IIS 7.5</li>
  <li>Self-host the WCF app and port it to IIS 7.5 later</li>
  <li>Something like <a href="http://msdn.microsoft.com/en-us/library/bb552363.aspx" rel="nofollow">WcfSvcHost.exe</a></li>
  <li>...</li>
  </ul>
  
  <blockquote>
    <p>Note to WcfSvcHost.exe: <em>I can't find such tool in <strong>Visual Web
    Developer Express 2010</strong>. Is it still possible to use this tool in
    Visual Web Developer Express 2010?
    If the option WcfSvcHost.exe is suggested, it would be nice to hear a solution for this  problem.</em></p>
  </blockquote>
  
  <p>What are the advantages/disadvantages of each option in following aspects?</p>
  
  <ul>
  <li>How close to reality? </li>
  <li>Installation effort</li>
  <li>Security (Is installing a full web server a good idea?)</li>
  </ul>
  
  <p>Thanks!</p>