Assignment
Create a Ticket Purchase application.
• Create this program as a Windows Forms Application with multiple forms.
• The first form will be a login form. It will accept a username and password. It will then compare these values to a username/password combination that exists in a text file. If it finds a match it will open the next form and close itself.
• The second form (referred to as the Manager Form below) would display the user's name and allow them select a type of event (include at least 3 types [sporting, music, speaking engagement]. It should also include a list of all the tickets the user has purchased this session (referred to as Ticket List below)
o OPTIONAL and a list of all the tickets the user has purchased in previous sessions (referred to as History List below).
• OPTIONAL: The History List will be populated from information in a file (referred to as the History File below) and only show information for this user.
• When a user clicks a button like "Choose Options" the user will be directed to one of three forms (one form per event type). When the user clicks a button like "Purchase" on those forms, their choice will be sent back to the Manager Form.
• The Ticket List should be updated with each ticket's information.
• When the user clicks a button like "Confirm All Purchases" on the Manager Form, the contents of the Ticket List should be saved to the History File including all information about the event and price and the user who made the purchase.
• Create a base Event class and three classes that inherit from it to represent the three event choices above. There should be at least 3 attributes of the event class that are common to all derived classes and at least 2 attributes specific to each derived type.
• Each event type should have a CalculatePrice method but each should use its own implementation using all attributes (polymorphism). These do NOT have to be as complicated as the sandwich calculation for Assignment 3. They must be different from each other but do not need to take every attribute into account during calculation. For instance, once event could just use a date attribute to calculate price while another could have a standard price across all dates but add a small change based on whether the user wants lawn seats (controlled via checkbox).
• Create a form for each event type as mentioned above. The form should include a header displaying the user's name and event type chosen.
• On each event form display controls to allow the user to select attributes for their event. Each control should be a different type (i.e. one textbox, one checkbox, one list box etc.) Pre-filled controls (like a list box) should be filled from data in a static method in the class.
• Each form should have a calculate price button that creates an instance of the class, fills the attributes from data provided and displays the ticket price.
• Each form should have a Purchase button that returns data to the Manager Form as described above
• Each form should have proper error handling to catch any incorrect values entered in the user controls.