Please tell me NO to this question. Shouldn't all controls be developed
with Server.Transfer or Server.Execute in mind? I am finding my Login
Control does not behave per its "ShowWhileLoggedIN" setting unless I
force some kind of client side navigation to happen.
Is it me, or the control that is broken? :-)
Happy Holidays
Please reply to brian.oneil@dotnet.itags.org.mcdean.com
( I am not finding my own posts in this forum anymore
( what happened to Search for messages by author feature? ) )Revision to this problem ; Whenever I browse to a page called
"DEFAULT", the Login Control refuses to adhere to the
"VisibleWhenLogged" property.
Any other pages on the site seem to function as expected. The Default
page has no code in it, as is the case with my other test cases. Guess
this is a throwback to the original security model where the Web.Config
handles all the Forms auth page setup?
Thanks for listening,
Brian
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment