I'm turning to this wonderful group to see if anyone can shed some light on our frustration. We have a well developed company intranet done in ASP that we would like to convert to ASP.NET. The intranet is used mostly in an 'anonymous' fashion but there are areas where we use authentication. For our ASP site we had a lovely login.asp page that we would just include (<!--#include virtual="/login/login.asp"-->) wherever we wanted to use a login, and there would be a username/password box right on the page. Content visibility that required the user to be logged in was controlled with a session variable.
Try as we might, we can't seem to find a way that .NET handles this in a similar manner. Every example or instruction we find requires a redirection to a separate login page. Does anyone know if .NET will even allow an #include or @REGISTER method for incorporating a login box on any given page? Something that allows the use of a centralized login format without having to redirect the user away from their current area of activity to the central login page?
Perhaps it's terribly simple or simply impossible, but I would greatly appreciate anything you have to offer on the matter. Thank you!
Try as we might, we can't seem to find a way that .NET handles this in a similar manner. Every example or instruction we find requires a redirection to a separate login page. Does anyone know if .NET will even allow an #include or @REGISTER method for incorporating a login box on any given page? Something that allows the use of a centralized login format without having to redirect the user away from their current area of activity to the central login page?
Perhaps it's terribly simple or simply impossible, but I would greatly appreciate anything you have to offer on the matter. Thank you!