asp.net-core-1.0

I am currently trying out the RC2 release of ASP.NET Core and I am running into an issue with SignalR . I need to be able to send messages to the client outside of the request thread. Now in the full .NET framework you can do this like: var context = GlobalHost.ConnectionManager.GetHubContext<MyHub>(); context.Clients.<SendMessage>() But in ASP.NET Core there is no GlobalHost . I found a similar question: How to get SignalR Hub Context in a vNext Project? Where the second answer provides a method to get the hubcontext outside the request thread, but this also does not work in ASP.NET Core . So

How do I get environment variables from elastic beanstalk into an asp.net core mvc application? I have added a .ebextensions folder with app.config file in it with the following: option_settings: - option_name: HelloWorld value: placeholder - option_name: ASPNETCORE_ENVIRONMENT value: placeholder The .ebextensions folder is included in the publish package. On deployment, both the variables are visible in the aws elasticbeanstalk console at Configuration > Software Configuration > Environment Variables However, when I try to read the variables in the application, none of the below options are

In RC1 , IUrlHelper could be injected in services (with services.AddMvc() in startup class) This doesn't work anymore in RC2 . Does anybody know how to do it in RC2 as just newing up a UrlHelper requires an ActionContext object. Don't know how to get that outside a controller. For ASP.NET Core RC2 there is an issue for this on the github repo . Instead of injecting the IUrlHelper , take an IUrlHelperFactory . It also sounds like you'd need the IActionContextAccessor injected as a Controller no longer has a public property ActionContext . Register the dependency: services.AddSingleton

I understand that asp.net core has a new configuration system that is quite flexible and that's great. But there are things I like about the web.config based configuration system from .net 4.x. For example one can put comments in the web.config file since it's an xml file. And that for me is worth sticking with xml rather than going with the shiny new json approach. [ Update: I now understand that the json approach also supports comments in the file.] So, if I have a Asp.Net Core Web Project that targets the full framework it seems like I should be able to use the web.config based System

I am trying to set up authorization in ASP.NET Core 1.0 (MVC 6) web app. More restrictive approach - by default I want to restrict all controllers and action methods to users with Admin role. So, I am adding a global authorize attribute like: AuthorizationPolicy requireAdminRole = new AuthorizationPolicyBuilder() .RequireAuthenticatedUser() .RequireRole("Admin") .Build(); services.AddMvc(options => { options.Filters.Add(new AuthorizeFilter(requireAdminRole));}); Then I want to allow users with specific roles to access concrete controllers. For example: [Authorize(Roles="Admin,UserManager")]