title: Does .NET Core support creating webjobs that get started by an Azure QueueTrigger?
body: <p>I have an existing webjob (.NET 4.6.1) that runs fine and gets triggered whenever a message arrives in a queue. I'm investigating how to migrate some applications to .NET Core 1.0 and as part of that I did some research.</p>
  
  <p>It looks like at this point in time, .NET Core 1.0 only supports webjobs that run on a schedule and have no special Webjob features, such as this example: <a href="https://blog.kloud.com.au/2016/06/08/azure-webjobs-with-dotnet-core-rc2/" rel="nofollow noreferrer">https://blog.kloud.com.au/2016/06/08/azure-webjobs-with-dotnet-core-rc2/</a></p>
  
  <p>To have a queue message trigger the job I need the features of the Webjob packages. When I add any of the WebJobs Nuget packages (including beta versions), I get the error:</p>
  
  <pre><code>Package Microsoft.Azure.WebJobs.Core 2.0.0-beta2 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package Microsoft.Azure.WebJobs.Core 2.0.0-beta2 supports: net45 (.NETFramework,Version=v4.5)
      One or more packages are incompatible with .NETCoreApp,Version=v1.0.
  </code></pre>
  
  <p>I did apply a workaround for the Azure Storage already as described in:
  <a href="https://jeremiedevillard.wordpress.com/2016/09/27/use-the-azure-storage-library-in-netcore-application/" rel="nofollow noreferrer">https://jeremiedevillard.wordpress.com/2016/09/27/use-the-azure-storage-library-in-netcore-application/</a>
  but thas apparently does not solve the issue for the Webjob package.</p>
  
  <p>I am aware of some workaround of deploying a non-.NET Core webjob next to a .NET Core website as described here: <a href="https://stackoverflow.com/questions/38919723/how-do-i-deploy-an-azure-webjob-alongside-a-net-core-web-app-via-git">How do I deploy an Azure WebJob alongside a .NET Core Web App via Git?</a>
   but - although that would work - I just want to know if I can port my webjob to .NET Core 1.</p>
  
  <p>Does anyone know a way to do this?</p>
  
  <p>TIA,
  Jeroen</p>