When using CSLA 8+ with an ASP.NET MVC 5 (and presumably all ASP.NET 5) projects, and a LocalProxy for the data portal, the logical server-side data portal attempts to use Csla.Web.Mvc.ApplicationContextManager. The problem is that HttpContext is not available in logical server-side code, and so the data portal call fails.

The Csla.Web.Mvc.ApplicationContextManager knows it is invalid - but it gets used anyway.

It seems that ApplicationContextAccessor is returning the invalid context manager rather than a valid option, because there is no check for this case in the code.