Wrong IContextManager is used in ASP.NET 5 with LocalProxy #4354
Assignees
Labels
Comments
rockfordlhotka
added a commit
that referenced
this issue
Nov 29, 2024
This was referenced Nov 29, 2024
rockfordlhotka
added a commit
that referenced
this issue
Dec 4, 2024
rockfordlhotka
added a commit
that referenced
this issue
Dec 5, 2024
rockfordlhotka
added a commit
that referenced
this issue
Dec 6, 2024
rockfordlhotka
added a commit
that referenced
this issue
Dec 13, 2024
* #3785 Update to .NET 9 package references * #3785 Update to .NET 9 package references * #3785 Update to .NET 9 package references * #3785 Update to .NET 9 package references * #4354 Use correct context manager for aspnet classic * Add global.json to solution files * #4360 Create packages for generators * Update v9 upgrade guide with RabbitMQ changes and NRT * Add missing net8 TFM in Grpc and RabbitMQ projects * Add missing NRT clarification * Revert MAUI controls update because they cause the build to fail * #3785 Update for CSLA 9 --------- Co-authored-by: Stefan Ossendorf <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 thatHttpContextis not available in logical server-side code, and so the data portal call fails.The
Csla.Web.Mvc.ApplicationContextManagerknows it is invalid - but it gets used anyway.It seems that
ApplicationContextAccessoris returning the invalid context manager rather than a valid option, because there is no check for this case in the code.The text was updated successfully, but these errors were encountered: