{"action":"created","issue":{"url":"https://api.github.com/repos/jbatonnet/Microsoft.AspNetCore.Mono/issues/2","repository_url":"https://api.github.com/repos/jbatonnet/Microsoft.AspNetCore.Mono","labels_url":"https://api.github.com/repos/jbatonnet/Microsoft.AspNetCore.Mono/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/jbatonnet/Microsoft.AspNetCore.Mono/issues/2/comments","events_url":"https://api.github.com/repos/jbatonnet/Microsoft.AspNetCore.Mono/issues/2/events","html_url":"https://github.com/jbatonnet/Microsoft.AspNetCore.Mono/issues/2","id":207034536,"number":2,"title":"There are better ways to add the mono compatibility to support Razor views","user":{"login":"davidfowl","id":95136,"avatar_url":"https://avatars0.githubusercontent.com/u/95136?v=3","gravatar_id":"","url":"https://api.github.com/users/davidfowl","html_url":"https://github.com/davidfowl","followers_url":"https://api.github.com/users/davidfowl/followers","following_url":"https://api.github.com/users/davidfowl/following{/other_user}","gists_url":"https://api.github.com/users/davidfowl/gists{/gist_id}","starred_url":"https://api.github.com/users/davidfowl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidfowl/subscriptions","organizations_url":"https://api.github.com/users/davidfowl/orgs","repos_url":"https://api.github.com/users/davidfowl/repos","events_url":"https://api.github.com/users/davidfowl/events{/privacy}","received_events_url":"https://api.github.com/users/davidfowl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2017-02-12T07:23:35Z","updated_at":"2017-03-04T00:04:57Z","closed_at":null,"body":"A few things before I get to the main issue. I read your post about ASP.NET Core on the Pi (very cool! https://www.thedju.net/articles/asp-net-core-mono-linux). \r\n\r\nDependency Model is OSS:\r\nhttps://github.com/dotnet/core-setup/tree/master/src/Microsoft.Extensions.DependencyModel\r\n\r\nYou probably shouldn't use private reflection to edit the reference assemblies. I know it works but it's fragile. If you're trying to tell razor for where the compilation assemblies are, there are better extensibility points for that:\r\n\r\nhttps://github.com/aspnet/Mvc/blob/rel/1.1.0/src/Microsoft.AspNetCore.Mvc.Razor/RazorViewEngineOptions.cs#L98\r\n\r\nYou can add to the list of assemblies here so that runtime compilation works. This is a public supported API.\r\n\r\nPS .NET Core now works on ARM"},"comment":{"url":"https://api.github.com/repos/jbatonnet/Microsoft.AspNetCore.Mono/issues/comments/284104777","html_url":"https://github.com/jbatonnet/Microsoft.AspNetCore.Mono/issues/2#issuecomment-284104777","issue_url":"https://api.github.com/repos/jbatonnet/Microsoft.AspNetCore.Mono/issues/2","id":284104777,"user":{"login":"davidfowl","id":95136,"avatar_url":"https://avatars0.githubusercontent.com/u/95136?v=3","gravatar_id":"","url":"https://api.github.com/users/davidfowl","html_url":"https://github.com/davidfowl","followers_url":"https://api.github.com/users/davidfowl/followers","following_url":"https://api.github.com/users/davidfowl/following{/other_user}","gists_url":"https://api.github.com/users/davidfowl/gists{/gist_id}","starred_url":"https://api.github.com/users/davidfowl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidfowl/subscriptions","organizations_url":"https://api.github.com/users/davidfowl/orgs","repos_url":"https://api.github.com/users/davidfowl/repos","events_url":"https://api.github.com/users/davidfowl/events{/privacy}","received_events_url":"https://api.github.com/users/davidfowl/received_events","type":"User","site_admin":false},"created_at":"2017-03-04T00:04:57Z","updated_at":"2017-03-04T00:04:57Z","body":"> The thing is, for Mono, I don't want to specify each assembly reference. Instead I want to specify a search path.\r\n\r\nRuntime compilation doesn't hardcode any knowledge of the layout of reference assemblies. That's why the toolchain copies the reference assemblies to the output folder for all non mono cases (even .NET Framework doesn't hard code any GAC knowledge). See PreserveCompilationContext.\r\n\r\n> Ideally, the system would know to look for assemblies in the application path and also the equivalent of the GAC. I agree that hacking a static private variable is no good. \r\n\r\nASP.NET Core doesn't and won't hard code knowledge of the GAC. That's why the extensibility does this.\r\n\r\n> But it's also no good that the only extensible thing is at the granularity of assemblies.\r\n\r\nIt's literally the most flexible thing you can expose, any search capability can be built on top of it. The mono reference assembly location varies per OS and based on where you installed mono. Adding a mono aware razor package would be fine here."}}
{"actor":{"display_login":"davidfowl"}}