{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/Razor/issues/2721","repository_url":"https://api.github.com/repos/aspnet/Razor","labels_url":"https://api.github.com/repos/aspnet/Razor/issues/2721/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/Razor/issues/2721/comments","events_url":"https://api.github.com/repos/aspnet/Razor/issues/2721/events","html_url":"https://github.com/aspnet/Razor/issues/2721","id":379282679,"node_id":"MDU6SXNzdWUzNzkyODI2Nzk=","number":2721,"title":"SDK does not correctly resolve RazorExtension when multiple instances of RazorConfiguration are present","user":{"login":"pranavkm","id":174281,"node_id":"MDQ6VXNlcjE3NDI4MQ==","avatar_url":"https://avatars2.githubusercontent.com/u/174281?v=4","gravatar_id":"","url":"https://api.github.com/users/pranavkm","html_url":"https://github.com/pranavkm","followers_url":"https://api.github.com/users/pranavkm/followers","following_url":"https://api.github.com/users/pranavkm/following{/other_user}","gists_url":"https://api.github.com/users/pranavkm/gists{/gist_id}","starred_url":"https://api.github.com/users/pranavkm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pranavkm/subscriptions","organizations_url":"https://api.github.com/users/pranavkm/orgs","repos_url":"https://api.github.com/users/pranavkm/repos","events_url":"https://api.github.com/users/pranavkm/events{/privacy}","received_events_url":"https://api.github.com/users/pranavkm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-09T18:59:27Z","updated_at":"2018-11-09T18:59:27Z","closed_at":null,"author_association":"MEMBER","body":"This is a bug in how we do filtering here: https://github.com/aspnet/Razor/blob/master/src/Microsoft.NET.Sdk.Razor/build/netstandard2.0/Sdk.Razor.CurrentVersion.targets#L282-L284\r\n\r\nIn addition, there's also an issue when multiple instances of `RazorConfiguration` with the same identity are resolved. This occurs in our interim builds when projects target `netcoreapp3.0` but resolve a `Microsoft.AspNetCore.App v2.x`. We can do a small fix to do a better job here."}}
{"actor":{"display_login":"pranavkm"}}