Possible Duplicate:
difference between http.context.user and thread.currentprincipal and when to use them?
What’s the difference between these two in an ASP.NET application?
I know the HttpContext.User.Identity is set when the user is authenticated through FormsAuthentication. But when is the Thread.CurrentPrincipal.Identity set?
Do they always hold the same value?
Does that still hold true for other layers of the application that do not have access to a HttpContext?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
HttpContext.User.Identity is the current logged in user in your web app.
Thread.CurrentPrincipal applies only when the <authentication mode = "windows"/>. Normally this is using with Windows based applications (Winforms,WPF..)
Method 2
if you use the HttpContext.User.Identity equals the Thread.CurrentPrincipal
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0