Simple ASP.Net Web Forms project with hard coded usernames/passwords to protect a subfolder with authentication

I have some HTML files that I would like to put onto one of our web servers but have them protected with by a username and password. This is to be deployed onto a Windows Server 2008 R2 server running IIS 7 with .NET Framework 4. On this server IIS is already running a website at the root of the hostname which we will use (i.e. [login to view URL]). I would like to make a new virtual folder on the IIS and have a self contained path which is username/password protected and under this path I'd like to have some HTML files (i.e. [login to view URL]). This should be written in C# ASP.NET Web Forms (not MVC and not ASP.NET Web Pages). The code should be written inline into the web pages. See [login to view URL] I don't want to have to build the solution for deployment. The valid username and password list can be stored in a file or hard coded into the [login to view URL] or C# page. These links may be helpful to you. [login to view URL] [login to view URL] I suspect it will need a [login to view URL] file and a [login to view URL] page. Here are some example cases for clearing understanding. Case 1 - Successful access to [login to view URL] 1. User attempts to go to [login to view URL] 2. User is redirected to [login to view URL] and asked for a username and password. 3. The user enters their username and password. 4. If they match one of the pairs hard coded into the system (i.e. no database) then redirect the user back to [login to view URL] Case 2 - Successful access to [login to view URL] 1. User attempts to go to [login to view URL] 2. User is redirected to [login to view URL] and asked for a username and password. 3. The user enters their username and password. 4. If they match one of the pairs hard coded into the system (i.e. no database) then redirect the user back to [login to view URL] Case 3 - Access to [login to view URL] 1. User attempts to go to http://mywebsite.com. 2. User reaches that location. No code from this project is run at all. This project has no influence or control. Case 4 - Access to [login to view URL] 1. User attempts to go to [login to view URL] 2. User reaches that location. No code from this project is run at all. This project has no influence or control. Case 5 - One unsuccessful attempt access to [login to view URL] 1. User attempts to go to [login to view URL] 2. User is redirected to [login to view URL] and asked for a username and password. 3. The user enters their username and password incorrectly. 4. The username and password are incorrect. The user is informed of this and left on the page [login to view URL] 5. The user enters their username and password correctly. 6. The username and password match one of the pairs hard coded into the system (i.e. no database) then redirect the user back to [login to view URL] Case 6 - Successful access to [login to view URL] 1. User attempts to go to [login to view URL] 2. User is redirected to [login to view URL] and asked for a username and password. 3. The user enters their username and password. 4. If they match one of the pairs hard coded into the system (i.e. no database) then redirect the user back to [login to view URL]