Thread.CurrentPrincipal looses the Principal object

DevUser posted on Tuesday, October 30, 2007

I am using the VB.NET version of CSLA .NET 3.0.2. It's a WPF Application. I have a  custom principal object derived from BusinessPrincipalBase implementing IPrincipal. At the Login the Thread.CurrentPrincipal is seem to be set correctly by Csla’s ApplicationContext.User  property  . But , debugging future method calls from the same program instance, Thread.CurrentPrincipal's Principal wouldn't be the same as that of the current logged in user. Not sure how to set this WPF main thread's principal object so that it doesn't lose the Thread.CurrentPrincipal at any time.

 

Any suggestions to fix this issue?

JoeFallon1 replied on Tuesday, October 30, 2007

There is a large section in the new eBook that explains how to use the Principal in WPF.

Have you got a copy yet?

Joe

 

DevUser replied on Tuesday, October 30, 2007

I did refer to the 3.0 ebook &  have tried the exact same approach in the book. Still can't find the solution.