{"action":"created","issue":{"url":"https://api.github.com/repos/Azure/Azure-Functions/issues/805","repository_url":"https://api.github.com/repos/Azure/Azure-Functions","labels_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/805/labels{/name}","comments_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/805/comments","events_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/805/events","html_url":"https://github.com/Azure/Azure-Functions/issues/805","id":324051533,"node_id":"MDU6SXNzdWUzMjQwNTE1MzM=","number":805,"title":"Add support for authoring Azure Functions as .NET Core class library","user":{"login":"pscholtes","id":2772725,"node_id":"MDQ6VXNlcjI3NzI3MjU=","avatar_url":"https://avatars2.githubusercontent.com/u/2772725?v=4","gravatar_id":"","url":"https://api.github.com/users/pscholtes","html_url":"https://github.com/pscholtes","followers_url":"https://api.github.com/users/pscholtes/followers","following_url":"https://api.github.com/users/pscholtes/following{/other_user}","gists_url":"https://api.github.com/users/pscholtes/gists{/gist_id}","starred_url":"https://api.github.com/users/pscholtes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pscholtes/subscriptions","organizations_url":"https://api.github.com/users/pscholtes/orgs","repos_url":"https://api.github.com/users/pscholtes/repos","events_url":"https://api.github.com/users/pscholtes/events{/privacy}","received_events_url":"https://api.github.com/users/pscholtes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-05-17T14:35:40Z","updated_at":"2018-06-12T15:12:44Z","closed_at":null,"author_association":"NONE","body":"Add support to the \"Azure Functions and Web Jobs Tools\" extension within Visual Studio for authoring Azure Functions as a .NET Core class library. This issue is a spin off from a conversation started in #686 and is possibly, semi-related to #790. \r\n\r\nWhen creating a new Azure Function app, you must select between the versions \"v1 (.NET Framework)\" or \"v2 (.NET Standard)\". \r\n\r\n1. If v1 is selected, you can target any version of the .NET Framework <= 4.6.1\r\n2. If v2 is selected, you can target any version of .NET Standard <= 2.0\r\n\r\n**Neither option allows the resulting Azure Function project to target .NET Core 2.x.**\r\n\r\n**Scenario**\r\nGiven the following VS solution/project architecture for Company Xyz:\r\n* `Xyz.Common` .NET Core 2.x shared library leveraging EF Core and various 3rd party packages\r\n* `Xyz.Web` ASP.NET Core Web Application leveraging AspNetCore.All, EF Core, Controllers, etc.\r\n* `Xyz.Functions` v2 Azure Functions project with HTTP, timer, and queue triggers\r\n\r\n**Problem**\r\nWhen a project reference is added from `Xyz.Functions` to `Xyz.Common` Visual Studio generates a \"project not compatible\" build error as these two projects reference different frameworks (i.e. .NET Standard != .NET Core).\r\n\r\n**Reasoning**\r\nIn a \"real word\" enterprise-level application, it's a _very_ realistic expectation for a developer to centralize the logic for a specific processing routine and want to leverage that code from an `IActionResult` in a MVC app and a `[TestMethod]` in a MSTest project. Continuing with that approach, AF should allow a developer to leverage their .NET Core code from a `Trigger` as well.\r\n"},"comment":{"url":"https://api.github.com/repos/Azure/Azure-Functions/issues/comments/396625951","html_url":"https://github.com/Azure/Azure-Functions/issues/805#issuecomment-396625951","issue_url":"https://api.github.com/repos/Azure/Azure-Functions/issues/805","id":396625951,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NjYyNTk1MQ==","user":{"login":"pscholtes","id":2772725,"node_id":"MDQ6VXNlcjI3NzI3MjU=","avatar_url":"https://avatars2.githubusercontent.com/u/2772725?v=4","gravatar_id":"","url":"https://api.github.com/users/pscholtes","html_url":"https://github.com/pscholtes","followers_url":"https://api.github.com/users/pscholtes/followers","following_url":"https://api.github.com/users/pscholtes/following{/other_user}","gists_url":"https://api.github.com/users/pscholtes/gists{/gist_id}","starred_url":"https://api.github.com/users/pscholtes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pscholtes/subscriptions","organizations_url":"https://api.github.com/users/pscholtes/orgs","repos_url":"https://api.github.com/users/pscholtes/repos","events_url":"https://api.github.com/users/pscholtes/events{/privacy}","received_events_url":"https://api.github.com/users/pscholtes/received_events","type":"User","site_admin":false},"created_at":"2018-06-12T15:12:44Z","updated_at":"2018-06-12T15:12:44Z","author_association":"NONE","body":"Hey @paulbatum, in [your recent comment](https://github.com/Azure/Azure-Functions/issues/836#issuecomment-395919411) you mention that more \"investigation\" is required for this issue. I am just curious, but is this issue in active discovery/development on the MSFT side? Do you have any updates or roadmap for support? Thanks!\r\n\r\n"}}
{"actor":{"display_login":"pscholtes"}}