Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to access session from a view in ASP .NET Core MVC 1.0

I am trying to access session data from inside a view.

Use Case: I'm storing status messages in the session that will be displayed at the top of the page. Currently I implemented this by using a DisplayMessages() function that sets some ViewData[....] properties and calling it at the beginning of every controller action.

Goal: I want to only set the status message once without needing additional code in the controller to display the messages on the next page load.

So I'm trying to access the messages that are stored in the session directly from the view.

So far I have tried the following:

  • Dependency Injection of an IHttpContextAccessor (doesn't seem to work anymore with ASP .NET Core MVC 1.0.0
  • Creating a static class to access the session, including the change from next() to next.invoke() suggested in the comment
    • This didn't work. I could access the HttpContext and Session.IsAvailable was true, but there was no data in the session.
like image 282
FSMaxB Avatar asked Aug 31 '16 04:08

FSMaxB


Video Answer


2 Answers

The following should work in the view: Context.Session.TryGetValue

If you are using the SessionExtensions then Context.Session.GetString will work.

like image 92
bvoleti Avatar answered Sep 21 '22 03:09

bvoleti


Injecting IHttpContextAccessor does work, but starting with ASP.NET Core 1.0.0 RC2, the IHttpContextAcessor is not registered by default, because it has significant performance overhead per request. See this GitHub announcement for more information.

Tratcher posted:

IHttpContextAccessor can be used to access the HttpContext for the current thread. However, maintaining this state has non-trivial performance costs so it has been removed from the default set of services.

Developers that depend on it can add it back as needed: services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();

But in your use case, I would suggest using a ViewComponent, which is a reusable piece of View with logic, that do not depend on a controller.

The documentation can be found here.

In your Views you would simply embed it with

@await Component.InvokeAsync("PriorityList", new { maxPriority = 2, isDone = false })

or

@Component.Invoke("PriorityList", new { maxPriority = 2, isDone = false })

for synchronous calls.

like image 38
Tseng Avatar answered Sep 22 '22 03:09

Tseng