Thursday, July 26, 2007

RE: Serious issue with HttpContext.Current.User.Identity.Name

The best solution I found: use ASP 2.0.
There were apparently some bugs with 1.1 that caused things like this.
I never got a great solution. The best thing I could do is compare the HttpContext.Current.User.Identity.Name with what I stored in a session variable and make sure they are the same.

Date: Thu, 28 Jun 2007 03:07:14 -0700
Subject: Serious issue with HttpContext.Current.User.Identity.Name

Hi kiran

I have the same problem about HttpContext.Current.User.Identity.Name. But the solution in forum thescripts developer network you posted in year of 2005 is still discontinued. Please help me where i can find the solution for it.

best regards

Andi Purwito

Got a little couch potato?
Check out fun summer activities for kids.