{"action":"created","issue":{"url":"https://api.github.com/repos/aspnet/AspNetCore/issues/3774","repository_url":"https://api.github.com/repos/aspnet/AspNetCore","labels_url":"https://api.github.com/repos/aspnet/AspNetCore/issues/3774/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/AspNetCore/issues/3774/comments","events_url":"https://api.github.com/repos/aspnet/AspNetCore/issues/3774/events","html_url":"https://github.com/aspnet/AspNetCore/issues/3774","id":375995861,"node_id":"MDU6SXNzdWUzNzU5OTU4NjE=","number":3774,"title":"Consider moving ASP.NET Core Data Protection to Microsoft.Extensions.*","user":{"login":"PinpointTownes","id":6998306,"node_id":"MDQ6VXNlcjY5OTgzMDY=","avatar_url":"https://avatars1.githubusercontent.com/u/6998306?v=4","gravatar_id":"","url":"https://api.github.com/users/PinpointTownes","html_url":"https://github.com/PinpointTownes","followers_url":"https://api.github.com/users/PinpointTownes/followers","following_url":"https://api.github.com/users/PinpointTownes/following{/other_user}","gists_url":"https://api.github.com/users/PinpointTownes/gists{/gist_id}","starred_url":"https://api.github.com/users/PinpointTownes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PinpointTownes/subscriptions","organizations_url":"https://api.github.com/users/PinpointTownes/orgs","repos_url":"https://api.github.com/users/PinpointTownes/repos","events_url":"https://api.github.com/users/PinpointTownes/events{/privacy}","received_events_url":"https://api.github.com/users/PinpointTownes/received_events","type":"User","site_admin":false},"labels":[{"id":792032421,"node_id":"MDU6TGFiZWw3OTIwMzI0MjE=","url":"https://api.github.com/repos/aspnet/AspNetCore/labels/repo:DataProtection","name":"repo:DataProtection","color":"5319e7","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/aspnet/AspNetCore/milestones/5","html_url":"https://github.com/aspnet/AspNetCore/milestone/5","labels_url":"https://api.github.com/repos/aspnet/AspNetCore/milestones/5/labels","id":3005291,"node_id":"MDk6TWlsZXN0b25lMzAwNTI5MQ==","number":5,"title":"Backlog","description":null,"creator":{"login":"aspnet-hello","id":34947467,"node_id":"MDQ6VXNlcjM0OTQ3NDY3","avatar_url":"https://avatars3.githubusercontent.com/u/34947467?v=4","gravatar_id":"","url":"https://api.github.com/users/aspnet-hello","html_url":"https://github.com/aspnet-hello","followers_url":"https://api.github.com/users/aspnet-hello/followers","following_url":"https://api.github.com/users/aspnet-hello/following{/other_user}","gists_url":"https://api.github.com/users/aspnet-hello/gists{/gist_id}","starred_url":"https://api.github.com/users/aspnet-hello/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aspnet-hello/subscriptions","organizations_url":"https://api.github.com/users/aspnet-hello/orgs","repos_url":"https://api.github.com/users/aspnet-hello/repos","events_url":"https://api.github.com/users/aspnet-hello/events{/privacy}","received_events_url":"https://api.github.com/users/aspnet-hello/received_events","type":"User","site_admin":false},"open_issues":201,"closed_issues":34,"state":"open","created_at":"2018-01-01T07:20:36Z","updated_at":"2018-12-07T18:21:04Z","due_on":null,"closed_at":null},"comments":25,"created_at":"2018-10-31T14:40:15Z","updated_at":"2018-12-09T21:17:12Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"[@davidfowl asked for concrete examples](https://github.com/aspnet/AspNetCore/issues/3753#issuecomment-434253160) of things people would like to use outside of ASP.NET Core, that will be limited to .NET Core starting with 3.0.\r\n\r\nSome of the OWIN/Katana apps I've worked on rely on the `Microsoft.Owin.Security.Interop` backcompat' package to be able to share things like cookies and authentication tokens with more recent ASP.NET Core apps. This package depends on the shiny ASP.NET Core Data Protection, which currently lives in the `Microsoft.AspNetCore.DataProtection` namespace.\r\n\r\nMy request is simple: please consider moving the DP components to `Microsoft.Extensions.DataProtection` and keeping them compatible with .NET Standard (and .NET Framework)."},"comment":{"url":"https://api.github.com/repos/aspnet/AspNetCore/issues/comments/445572498","html_url":"https://github.com/aspnet/AspNetCore/issues/3774#issuecomment-445572498","issue_url":"https://api.github.com/repos/aspnet/AspNetCore/issues/3774","id":445572498,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0NTU3MjQ5OA==","user":{"login":"PinpointTownes","id":6998306,"node_id":"MDQ6VXNlcjY5OTgzMDY=","avatar_url":"https://avatars1.githubusercontent.com/u/6998306?v=4","gravatar_id":"","url":"https://api.github.com/users/PinpointTownes","html_url":"https://github.com/PinpointTownes","followers_url":"https://api.github.com/users/PinpointTownes/followers","following_url":"https://api.github.com/users/PinpointTownes/following{/other_user}","gists_url":"https://api.github.com/users/PinpointTownes/gists{/gist_id}","starred_url":"https://api.github.com/users/PinpointTownes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PinpointTownes/subscriptions","organizations_url":"https://api.github.com/users/PinpointTownes/orgs","repos_url":"https://api.github.com/users/PinpointTownes/repos","events_url":"https://api.github.com/users/PinpointTownes/events{/privacy}","received_events_url":"https://api.github.com/users/PinpointTownes/received_events","type":"User","site_admin":false},"created_at":"2018-12-09T21:17:12Z","updated_at":"2018-12-09T21:17:12Z","author_association":"CONTRIBUTOR","body":"> The bar for breaking changes isn't as different as you imply.\r\n\r\nEach major version of ASP.NET Core was released with many breaking changes (in 2.0, the most important one was authentication, in 3.0, it will be the hosting stuff). I'm not aware of any API removal in .NET Core/CoreFX itself. Have I missed something?\r\n\r\n> You can also expect the APIs to get heavily reviewed if we're going to expand the supported scenarios.\r\n\r\nCorrect me if I'm wrong, but the reviewing process you use for ASP.NET Core seems way different (much simpler) than the one used for .NET Core (each API change must come with a formal API proposal, which is heavily reviewed - potentially during a meeting - before one can even start working on the implementation).\r\n\r\nIt's worth mentioning that no one here has asked for features that are not already supported by DP. We just want it to keep supporting .NET Standard, which is already the case."}}
{"actor":{"display_login":"PinpointTownes"}}