The default page is determined by the web server and not something to be
changed in code. Also, it's good not to mess with the list because it can
affect perormance. The longer the list for example, the longer it takes IIS
to check what is the default page for a directory.
Why don't you put a check into the default.aspx page itself? You can check
if the user is currently authenticated and if so, determine where they
should go. Essentially, your default page just becomes a redirecting agent.
The tricky part though is you wouldn't be able to have a normal default.aspx
page since you can't determine whether the person who is visiting it just
returned to the site, or if they have been logged on for a while and are
just navigating around. With the right structure though this can be a moot
point, especially if the default.aspx page isn't something that they'll hit
except when they return to the site.
--
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression
"Jonathan Wood" <jw***@softcircuits.comwrote in message
news:%2****************@TK2MSFTNGP02.phx.gbl...
My site requires all users to log on. Depending on the user's role, they
will have access to a certain set of pages.
I implemented this by redirecting the user to the appropriate home page in
the handler for the LoggedIn event of the Login control.
The problem is that users don't always go through the Login control. For
example, if I check the Remember Me box and then disconnect and then
reconnect, I go straight to default.aspx in the root folder withough
having to log in again. And so my code doesn't have a chance to redirect
the user based on role in this case.
I'm thinking the answer would be to modify the default page depending on
the current role, but I'm not sure how to do that. I'm also curious if
anyone has any better ideas.
Thanks.
--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com