The behavior you're seeing is expected. When you lookup up the profile for a user, we update that user's last activity date (LAD) which affects their "online" status for Membership.
At some level, we have to make a decision on whether or not an operation is indicative of "user activity". Looking up a user's profile data just happends to be one of those cases, but I can see that in an administrative environment where you're just pulling up the data, this doesn't make sense. Except for an explosion in the number of API's, it would be nice to have overloads that allow you to skip updating a user's LAD. We have such an overload for Membership.GetUser(...).
I'll start an internal thread with the team to see if we should overload some of the API's in the next release.
Thanks,
Mark
This posting is provided "AS IS" with no warranties, and confers no rights.
This posting is provided "AS IS" with no warranties, and confers no rights.