asp.net 2.0 example programs WITHOUT USING WIZARDS

microsoft access database No wizards can be used, all must be coded. #1 • An initial public page called [login to view URL] This page will contain a logon area in which a user will type their username and password and press a logon button to authenticate (hopefully) their membership. If the membership information is not recognized, they should remain on the default page and be given an appropriate "membership not recognized" message or similar. If authenticated they will move to the… • [login to view URL] private membership page The page should only be reachable by authenticated members. If a user attempt to navigate directly to this page without first logging in, the page should automatically redirect them to the logon page. When an authenticated member reached the page, they should be greeted with the following message (assuming Babaloo has logged on previously): Welcome Back, Babaloo! This is your 3rd visit. Your last visit was on 10/2/2005 The visit number, username, lastvisit and password should be stored in the database. The visit information should be updated in the database each time a user logs on. The visits message should contain the correct extension (i.e. 1st, 2nd, 3rd, 4th...) If this is the first visit, the message should indicate there is no visit history available • The membership area should also contain a gridview showing all members in the database • You must use a minimum of two images for this assignment. The use is your discretion NOTES: • In order to develop against the same structure present on our web server, make sure your database is placed in a sub-folder off your application root called app_data • Make sure you have a member named Babaloo McSwell with a username of bmcscwell and a password of donut (be sure you have several other members in the database as well. • For database pathing (which must be physical, not relative), investigate [login to view URL](), or [login to view URL] • By convention, any images you use for this project should be in a sub-folder called images directly under the root folder • All data binding must be done in code #2 Concepts include: • Cookies • Generating emails programically • Session • Using multiple pages • Using graphics • Validator controls • Creating database INSERT and UPDATE statement mplement a website devoted to your politically-correct hobby. The site characteristics you must support include: • A public area of your website which contains some hobby content. The public area should have an option to create a membership or to logon if the user already has a membership. Of the user chooses to create a membership, they should be moved to: • A Create Membership registration page where users go to create an account. The account will consist of: o Username* o Password* o Email address* o nickname Those asterisk items are required and the user cannot create a membership without them. Once created, the application should email the user a greeting message and automatically move the new member to the member's area (where she will see a welcome greeting as done in the previous assignment) • A member's page will contain somewhat detailed content and pictures about your hobby. This can be reached only after a user (member) logs on (or just after they create an account). NOTE: this detailed area must be informative enough to teach/show the class something about your hobby which we likely do not know • As noted above, the member's page will require a logon (similar to the last assignment, where you track visits and last visit and display the data in the private welcome summary.) Optionally, as they log on, the visitor can check a box labeled “Remember Me” which will then leave a cookie on the user machine (which will expire in one year) and will remember them and “automatically log” them on for future visits • The members page will have a logoff feature, which will dump the session and return the user to the logon area • The members area will reject all unauthorized (non-authenticated) access and automatically move the intruder to the login area • The member logon area will have a profile area, which will allow for editing of the users: o Password o nickname o Email • The site should automatically send out an email receipt to the user informing them an update has occurred to their account • An Administrator area, which will show a listing of all member data (except administrators). Administrators to the site will go to this area automatically when logged on (you do not need to have the site create administrative accounts) • The Administrator area will reject all access to those not recognized as administrator, redirecting them to the logon page • Some graphics must be used #3 The site's complexity will be reduced to just two pages: a logon, and a member page • The logon page can be a simple logon area with a description of the site, i.e. "Dan's Sunbeam Tiger classic car restoration site" and with an option to "Sign Up" for a membership. This sign up option should replace the log in area with a sign up area (which is merely a modified profile control) on the login page that allows the user to create an account. Once created, the user should be transferred to the membership area. • An 'Account' consists of: o Username* o Password* o Firstname* o Lastname* o Email* o Kickname o Gender *required • The Member area page header area and navigation menu will now be implemented with static (added at design) usercontrols • Members are greeted as in the past upon log in with a welcome message displaying their last visit and the number of previous visits (be careful to implement first login checking) • You will load one of four dynamic usercontrols into the content area based on the request in the left navigation control (content by default) • As before, every time a member updates their profile an email receipt is sent to them • Member cannot log on without supplying values for their username and password. These values must exist before the page can be sent to the server • Member should be able to cancel (delete) their own membership, which deletes all details from the database. After canceling, they (of course) can't log on unless they create a new account again • An administrators page/view/area (for administrators only which you must validate) allows Admins to: o email the entire membership list o view the entire membership details for all non-admin members • Email should include a graphical header of some type (meaning an image) and be (of course) in HTML format • The content control must again contain some interesting content—the site idea does not necessarily need to be "hobby" based but must have some type of theme • The site should be designed for a screen width of no wider than 800 pixels (to be safe you should choose a width of 760 pixels as not overflowing the page width will become part of your grading) allow the administrator to edit all info for a member except Username CAN NOT USE WIZARDS. MUST BE COMPLETED WITHIN 48 HOURS