title: Are Service Fabric Katana with Web API Projects Supported By Microsoft?
body: <p>Regarding the switch from the Katana / Web API project template to ASP.NET Core for Service Fabric in Visual Studio 2017 that happened around April <a href="https://stackoverflow.com/users/4849191/vaclav-turecek">Vaclav Turecek</a> made this comment on a <a href="https://stackoverflow.com/questions/43478809/using-weblistener-or-owin-as-api-gateway-for-azure-service-fabric">post</a>...</p>
  
  <blockquote>
    <p>Katana was largely a prototype for what would become ASP.NET Core. Most, if not all, new feature work is going into ASP.NET Core, not Katana, and <strong>ASP.NET Core is officially supported by Microsoft</strong>.</p>
  </blockquote>
  
  <p>Does this mean that the previous project template that used Katana / Owin is <strong>not</strong> officially supported by Microsoft?</p>
  
  <p>How critical is it to migrate any Azure Service Fabric services we wrote using that old template to the new ASP.NET Core template?</p>
  
  <p>Are the old Katana based services acceptable for production?</p>
  
  <p>If we continue to use these old services should we expect any issues?  For example, what about automated deployments with Team Services?  ASP.NET Core doesn't require XML transforms for it's configurations during deployment but the older Service Fabric template uses web.config so it does.  Can we expect this to cause headaches that migrating to ASP.NET would cure?</p>