CIS407A Entire Course
CIS407A entire course includes:
CIS407A Week 1 iLab Annual Salary Calculator,
CIS407A Week 2 iLab User Input Web Pages,
CIS407A Week 3 iLab User activity monitoring,
CIS407A Week 4 iLab Web forms with database interaction,
CIS407A Week 5 iLab Transaction Processing,
CIS407A Week 6 iLab Login and Security Levels,
CIS407A Week 7 iLab Error Notification via E-Mail,
Each tutorial includes Visual Studio ASP.NET 2013 Project.
iLAB OVERVIEW
Scenario/Summary
In this lab, we will incorporate error handling into the login process so that a notice of each invalid login is automatically e-mailed to the technical support staff.
Deliverables
When you try to log in, if your user name is not Mickey, Minnie, or another user you added (that is, if the user name is not found in tblUserLogin), then an e-mail should be sent to the [email protected]. If the user attempts to bypass the login page by typing a page name in the URL, your web application should redirect the user back to the login page. Once you have verified that it works, save your project, zip up all files, and submit in the Dropbox.
NOTE: E-mails may be blocked due to firewalls, antivirus software, or even Internet service providers that turned off SMTP because of some known security issues. If the code works (does not produce an error when submitting), you will get full credit for this project even if no e-mail message is actually transmitted. Consult with your instructor before submitting if an error occurs or if no e-mail is generated, to be sure.
iLAB STEPS
STEP 1: Business Layer Functionality
1. Open Microsoft Visual Studio.NET 2008.
2. Click the ASP.NET website named PayrollSystem to open it.
3. Create a new class called clsBusiness Layer.
4. Add the following code in the clsBusinessLayer class:
// **** Add the following at the top of the class file,// Add your comments hereusing System.Net.Mail;//**** Add the following code inside the body of public class clsBusinessLayer ****publicstaticbool SendEmail(string Sender, string Recipient, string bcc, string cc,string Subject, string Body){try{// Add your comments hereMailMessage MyMailMessage =newMailMessage();// Add your comments hereMyMailMessage.From =newMailAddress(Sender);// Add your comments hereMyMailMessage.To.Add(newMailAddress(Recipient));// Add your comments hereif(bcc != null && bcc != string.Empty) {// Add your comments hereMyMailMessage.Bcc.Add(newMailAddress(bcc));}// Add your comments hereif(cc != null && cc != string.Empty) {// Add your comments hereMyMailMessage.CC.Add(newMailAddress(cc));}// Add your comments hereMyMailMessage.Subject = Subject;// Add your comments hereMyMailMessage.Body = Body;// Add your comments hereMyMailMessage.IsBodyHtml = true;// Add your comments hereMyMailMessage.Priority = MailPriority.Normal;// Add your comments hereSmtpClient MySmtpClient =newSmtpClient();// Add your comments hereMySmtpClient.Port = 25;MySmtpClient.Host ="127.0.0.1";// Add your comments hereMySmtpClient.Send(MyMailMessage);// Add your comments herereturntrue;}catch(Exception ex) {// Add your comments herereturnfalse;}} |
STEP 2: Integration
5. Open the frmLogin web form code behind file and add the following code to the body of the if (dsUserLogin.tblUserLogin.Count < 1) statement, just above the return statement:
[php light=”true”]
// Add your comments here
// Add your comments here
if (clsBusinessLayer.SendEmail(“[email protected]”,
“[email protected]”, “”, “”, “Login Incorrect”,
“The login failed for UserName: ” + Login1.UserName +
” Password: ” + Login1.Password))
{
Login1.FailureText = Login1.FailureText +
” Your incorrect login information was sent to
[email protected]”;
}
[/php]
6. NOTE: Change the [email protected] and [email protected] to your e-mail and someone else’s e-mail for testing. 7. Optional: Perform this step only if you are doing this lab using Visual Studio 2008 installed on your own computer, your computer has Internet Information Services (IIS) installed, and you have administrative rights to IIS. If you are doing this lab using the iLab (Citrix) server, or if you do not have access to IIS, skip to step 8. Open IIS (Start > Control Panel > Administrative Tools > Internet Information Services), navigate to the Default SMTP Virtual Server, right-click on it, and left-click on Properties.
8. Click here for text description of this image.
9. Click the Access tab, then the Relay button, then Add, and add the IP 127.0.0.1. Click OK, OK, and APPLY when finished.
10. Click here for text description of this image.
11. We have a security hole in our web application. If you start the web application by going to the login page, you can bypass the login page by simply typing the name of a form in the URL (try it). There is some limited protection because of the check we are doing for user role, but it still allows a user to get to pages we don’t want them to get to unless the role is set properly. Add a security check in the Page_Load of each sensitive page (Manage Users, Add New Employee, View User Activity, Edit Employees), check for the Session role item with a value of “A,” and, if the user is accessing these pages without the proper permissions, redirect back to the frmLogin.aspx page.
12. This still leaves the possibility of a person bypassing the login page. We will fix that by using forms authentication. Add the following to the web.config file. (There should already be an authentication section – replace it with this.)
<authentication mode="Forms"><forms loginUrl="frmLogin.aspx"/></authentication><authorization ><deny users="?"/></authorization> |
13. This will redirect users to the login page if they have not yet gone through it for login. This process will use a cookie – when the user successfully logs in in a cookie is set that allows the user to go to other pages. If that cookie is not set then the user is redirected to the login page if they try to go to any other page. Add the cookie code by adding this code in the frmLogin.aspx C# code after each place that you have e.Authenticated = true:
FormsAuthentication.RedirectFromLoginPage(Login1.UserName, false);
14. Hints: Make sure you reestablish your database connection if you copied the files from a previous lab. Also, make sure to update the web.config file with the database connection string.
Update any DataSource controls you added with the new payroll database location.
When you manually try to go to a second page by skipping the login page, a cookie is set specifying the name of the page you were attempting to go to. Once you login successfully, ASP.Net will automatically attempt to navigate back to that page. You can reset the cookie so that the next page is frmMain, as expected, by typing that page in the URL for the browser before logging in.
Submit Final Lab (includes all previous lab assignments)
STEP 3: Test and Submit
12. Run your project. When you try to log in, enter a user name that is not Mickey or Minnie (i.e., a user name that is not found in tblUserLogin). An e-mail should be sent to [email protected] e-mail address.
Test that frmMain reconfigures properly based on user role. Make sure the user cannot bypass the login page.
Once you have verified that everything works, save your website, zip up all files, and submit in the Dropbox.
NOTE: E-mails may be blocked due to firewalls, antivirus software, or even Internet service providers that turned SMTP off because of some known security issues. If the code works (does not produce an error when submitting), you will get full credit for this project even if no e-mail message is actually transmitted. Consult with your instructor before submitting if an error occurs or if no e-mail is generated. It is expected that no e-mail will be sent if you are using the DeVry iLab (Citrix) server for this lab or if you were not able to configure IIS in step 7.
Make sure you include comments in the code provided where specified (where the ” // Add your comments here” is mentioned), including code you wrote, or else a 5 point deduction per item (form, class, function) will be made.
iLAB OVERVIEW
Scenario/Summary
In this week’s lab, we will create a login form, validate a user based on their login name and password, and allow them to access the system or not. We will assign a session variable to determine the level of security the user has and allow certain functions to be displayed or not displayed in the existing frmPersonnel form depending on the assigned security level. (NOTE: In some cases the instructions for this lab will be less specific than in earlier labs, because you are expected to apply what you have learned in earlier weeks. Refer to the detailed instructions in previous weeks’ labs if you need to do so.)
Instructions for Week 6 iLab: Login and Security Levels
Deliverables
When you try to log in, if you use User Name = Mickey and Password = Mouse, the frmMain form should open with all links visible. If you use User Name = Minnie and Password = Mouse, the frmMain form should open with only the Salary Calculator, View Personnel, and Search options should be available. You will have a new option called Manage Users that will allow you to add new users and remove or update existing users. Once you have verified that it works, save your website, zip up all files, and submit in the Dropbox.
Note on database connections: We are using a SQLDataSource control for the Edit employees feature we added. You should be using the connection string stored in the web.config file for your database connection for this control. Rather than creating a new connection each time, just use this connection. If you change the folder where your website is (e.g., you copy each week’s work to a new location), you will need to update the web.config. The advantage of using the database connection in the web.config is that you only have to set the configuration in one location.
Before starting this week’s lab, make sure everything is working and that all database connections are properly configured.
iLAB STEPS
STEP 1: Login Form (10 points)
1. Open Microsoft Visual Studio.NET 2008.
2. Click the ASP.NET website named PayrollSystem to open it.
3. Create a new web form named frmLogin.
4. Drop a login control onto the form.
5. Set the properties of the login control as follows:
PROPERTY VALUE
DestinationPageUrl frmMain.aspx
TitleText Please enter your UserName and Password in order to log into the system
6. Add the CoolBiz Productions, Inc. logo to the frmLogin form. Do not hylerlink the logo.
7. Highlight everything in the form, then click Format, Justify, Center. Save your work.
8. Go to the Solution Explorer, right-click on frmLogin, and left-click on Set As Start Page. Then run the website to check if the web form appears correctly.
STEP 2: Login Check (10 points)
9. Create a new DataSet called dsUser. Use the table tblLogin as the database table for this dataset. Do this in the same way you added datasets in the previous labs.
10. Open the clsDataLayer and add the following function:
// This function verifies a user in the tblUser tablepublicstaticdsUser VerifyUser(string Database, string UserName, string UserPassword){// Add your comments heredsUser DS;OleDbConnection sqlConn;OleDbDataAdapter sqlDA;// Add your comments heresqlConn =newOleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;"+"Data Source="+ Database);// Add your comments heresqlDA =newOleDbDataAdapter("Select SecurityLevel from tblUserLogin "+"where UserName like '"+ UserName +"' "+"and UserPassword like '"+ UserPassword +"'", sqlConn);// Add your comments hereDS =newdsUser();// Add your comments heresqlDA.Fill(DS.tblUserLogin);// Add your comments herereturnDS;} |
11. Double-click on the login control you added. Add the following code to the login control Authenticate event handler:
// Add your comments heredsUser dsUserLogin;// Add your comments herestring SecurityLevel;// Add your comments heredsUserLogin = clsDataLayer.VerifyUser(Server.MapPath("PayrollSystem_DB.mdb"),Login1.UserName, Login1.Password);// Add your comments hereif(dsUserLogin.tblUserLogin.Count< 1){e.Authenticated = false;return;}// Add your comments hereSecurityLevel = dsUserLogin.tblUserLogin[0].SecurityLevel.ToString();// Add your comments hereswitch(SecurityLevel){case"A":// Add your comments heree.Authenticated = true;Session["SecurityLevel"] ="A";break;case"U":// Add your comments heree.Authenticated = true;Session["SecurityLevel"] ="U";break;default:e.Authenticated = false;<strong> |
STEP 3: Test and Submit (10 points)
12. Open the frmPersonnel form and add the following code to its Page_Load() function:
// Add your comments hereif(Session["SecurityLevel"] =="A") {btnSubmit.Visible = true;//Add your comments here}else{btnSubmit.Visible = false;} |
13. Set the start page as frmLogin.aspx. Run the website. Try to log in with both User Name = Mickey and Password = Mouse and User Name = Minnie and Password = Mouse. Any other user ID and password should not allow you to log in.
14. When the user logs in we want to restrict what they can see and do based on their user role. The role is stored in the database table tblUserLogin. Mickey Mouse has all privileges whereas Minnie Mouse has read only privileges. We want to control the visibility of the links on the frmMain page.
15. Initially we did not set the ID of any of the Link Button or Image Button controls that we used on frmMain. In order to make our code more maintainable we will change the IDs as follows:
Option Link Button ID Image Button IDAnnual Salary Calculator linkbtnCalculator imgbtnCalculatorAdd New Employee linkbtnNewEmployee imgbtnNewEmployeeView User Activity linkbtnViewUserActivity imgbtnViewUserActivityView Personnel linkbtnViewPersonnel imgbtnViewPersonnelSearch Personnel linkbtnSearch imgbtnSearchEdit Employees linkbtnEditEmployees imgbtnEditEmployees |
16. Modify the main form so that the following options are turned off for nonadmin users:
o Add New Employeeo View User Activityo Edit Employees |
17. You now have a web application that honors the role of the logged in user. We don’t have a way of managing the user roles and users in the system.
18. Add a new form called frmManageUsers that will allow the user to add new users. The user will also need to be able to view all users and modify or delete any of the users in the database. Add a main form option called Manage Users that is only accessible to admin users. Add the link and image buttons as we have done in the past. Add the CoolBiz logo that is hyperlinked as you did in previous assignments.
o For the security level of the user, use a dropdown list control to allow the user to select from A or U.
o Name the controls with names that make sense.
o Add code as appropriate to the code behind and clsDataLayer.
19. Hints:
o Make sure you reestablish your database connection if you copied the files from a previous lab.
o Update any DataSource controls you added with the new Payroll database location.
o You can turn a control on or off by setting it’s Visible property.
o You can add a data entry form for new users and a grid displaying all users all on the same form.
o To force a gridView to refresh call its DataBind method.
o In order to use the Advanced SQL Generation option (allowing you to update/delete records) there must be a primary key defined on the table you are generating SQL for. tblUserLogin needs to have a primary key set on the UserID column. You can do this in Access.
20. Test your application to make sure you are logging in with an invalid user id. Try to log in with both Minnie and Mickey and make sure the UI adjusts by the role properly. Make sure you can utilize the Manage Users functionality to add/modify/delete and view user information. Once you have verified that everything works, save your project, zip up all files, and submit in the Dropbox.
NOTE: Make sure you include comments in the code provided where specified (where the ” // Your comments here” is mentioned); also, any code you write needs to be properly commented, or else a five point deduction per item (form, class, function) will be made.
Mickey Mouse (Admin)
iLAB OVERVIEW
Scenario/Summary
This week, we will use the .NET OleDbTransaction functions to either commit a set of changes to the database, if all of them were done correctly, or to roll back all of the changes if there was an error in any one of them. We will first modify the code we created last week so that it saves personnel data in the database in two steps; first by inserting a personnel record for a new employee, and then by updating that record to fill in the start and end dates. This two-step approach is not really needed in this simple case, but we will use it to simulate a more complex database transaction that would have to be done in multiple steps, such as one involving more than one table or even more than one database. We will then see what happens when there is an error in the second operation (the update), allowing a record to be created containing incomplete information–not a good result! We will fix the problem by wrapping both operations (the insert and the update) into a single transaction that will be committed (made permanent) only if both operations succeed or that will be rolled back (undone) if either operation fails. We will also add client-side validation using the ASP.Net validation controls, and we will allow the user an easy way to edit all employees.
Instructions for Week 5 iLab: “Transaction Processing”
Deliverables
All files are located in the subdirectory of the project. The project should function as specified: When you press the Submit button in frmPersonnel, a record should be saved in the tblPersonnel table containing the FirstName, LastName, PayRate, StartDate, and EndDate you entered. Test that the transaction will rollback by entering invalid information in one or more items, such as Hello for a StartDate. Check tht client-side validation works: The ability to edit employees in a grid is working. Once you have verified that it works, save your website, zip up all files, and submit them to the Dropbox.
iLAB STEPS
STEP 1: Modify the clsDataLayer to use a two-step process (10 points)
1. Open Microsoft Visual Studio.NET 2008.
2. Click the ASP.NET project called PayrollSystem to open it.
3. Open the clsDataLayer class.
4. Modify the SavePersonnel() function so that instead of just doing a single SQL INSERT operation with all the personnel data, it does an INSERT with only the FirstName and LastName, followed by an UPDATE to save the PayRate, StartDate, and EndDate into the new record. (This two-step approach is not really necessary here because we are dealing with only one table, tblPersonnel, but we are doing it to simulate a case with more complex processing requirements, where we would need to insert or update data in more than one table or maybe even more than one database.) Find the following existing code in the SavePersonnel() function:
// Add your comments herestrSQL ="Insert into tblPersonnel "+"(FirstName, LastName, PayRate, StartDate, EndDate) values ('"+FirstName +"', '"+ LastName +"', "+ PayRate +", '"+ StartDate +"', '"+ EndDate +"')";// Add your comments herecommand.CommandType = CommandType.Text;command.CommandText = strSQL;// Add your comments herecommand.ExecuteNonQuery();5. Modify it so that it readsasfollows:// Add your comments herestrSQL ="Insert into tblPersonnel "+"(FirstName, LastName) values ('"+FirstName +"', '"+ LastName +"')";// Add your comments herecommand.CommandType = CommandType.Text;command.CommandText = strSQL;// Add your comments herecommand.ExecuteNonQuery();// Add your comments herestrSQL ="Update tblPersonnel "+"Set PayRate="+ PayRate +", "+"StartDate='"+ StartDate +"', "+"EndDate='"+ EndDate +"' "+"Where ID=(Select Max(ID) From tblPersonnel)";// Add your comments herecommand.CommandType = CommandType.Text;command.CommandText = strSQL;// Add your comments herecommand.ExecuteNonQuery(); |
6. Set frmMain as the startup form and run the PayrollSystem Web application to test the changes. When valid data values are entered for a new employee, things should work exactly as they did before. To test this, enter valid data for a new employee in frmPersonnel and click Submit. The frmPersonnelVerified form should be displayed with the entered data values and a message that the record was saved successfully. Click the View Personnel button and check that the new personnel record was indeed saved to the database and that all the entered data values, including the PayRate, StartDate, and EndDate, were stored correctly. Close the browser window.
7. Now run the PayrollSystem Web application again, but this time enter some invalid data (a nonnumeric value) in the PayRate field to cause an error, like this:
frmPersonnel With Bad Data
8. Click here for text description of this image.
9. Now when you click Submit, the frmPersonnelVerified form should display a message indicating the record was not saved:
frmPersonnel Verified With Error Message
10. Click here for text description of this image.
11. However, when you click on the View Personnel button to display the personnel records, you should see that an incomplete personnel record was in fact created, with missing values for the PayRate, StartDate and EndDate fields:
Incomplete Personnel Record
12. Click here for text description of this image.
13. This occurred because the Insert statement succeeded but the following Update statement did not. We do not want to allow this to happen because we end up with incomplete or incorrect data in the database. If the Update statement fails, we want the Insert statement to be rolled back, or undone, so that we end up with no record at all. We will fix this by adding transaction code in the next step.
STEP 2: Add transaction code (10 points)
7. In the clsDataLayer.cls class file, add code to the SavePersonnel() function to create a transaction object. Begin the transaction, commit the transaction if all database operations are successful, and roll back the transaction if any database operation fails. The following listing shows the complete SavePersonnel() function; the lines you will need to add are marked with ** NEW ** in the preceding comment and are shown in bold.
// This function saves the personnel datapublicstaticbool SavePersonnel(string Database, string FirstName, string LastName,string PayRate, string StartDate, string EndDate){bool recordSaved;// ** NEW ** Add your comments hereOleDbTransaction myTransaction = null;try{// Add your comments hereOleDbConnection conn =newOleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;"+"Data Source="+ Database);conn.Open();OleDbCommand command = conn.CreateCommand();string strSQL;// ** NEW ** Add your comments heremyTransaction = conn.BeginTransaction();command.Transaction = myTransaction;// Add your comments herestrSQL ="Insert into tblPersonnel "+"(FirstName, LastName) values ('"+FirstName +"', '"+ LastName +"')";// Add your comments herecommand.CommandType = CommandType.Text;command.CommandText = strSQL;// Add your comments herecommand.ExecuteNonQuery();// Add your comments herestrSQL ="Update tblPersonnel "+"Set PayRate="+ PayRate +", "+"StartDate='"+ StartDate +"', "+"EndDate='"+ EndDate +"' "+"Where ID=(Select Max(ID) From tblPersonnel)";// Add your comments herecommand.CommandType = CommandType.Text;command.CommandText = strSQL;// Add your comments herecommand.ExecuteNonQuery();// ** NEW ** Add your comments heremyTransaction.Commit();// Add your comments hereconn.Close();recordSaved = true;}catch(Exception ex){// ** NEW ** Add your comments heremyTransaction.Rollback();recordSaved = false;}returnrecordSaved;} |
8. Run your Web application. First, enter valid data in all the fields of frmPersonnel. When you press the Submit button in frmPersonnel, a record should be saved in the tblPersonnel table containing the FirstName, LastName, PayRate, StartDate, and EndDate. With valid data entered in all the items, the “successfully saved” message should appear indicating that the transaction was committed.
frmPersonnelVerified After Commit
9. Click here for text description of this image.
10. Click the View Personnel button and verify that the new record was in fact added to the database table correctly.
frmViewPersonnel After Commit
11. Click here for text description of this image.
12. Now close the browser, run the Web application again, and this time test that the transaction will roll back after entering incorrect information. On the frmPersonnel form, enter invalid data for PayRate and click Submit. The “not saved” message should appear, which indicates that the transaction was rolled back.
frmPersonnel Verified After Rollback
13. Click here for text description of this image.
14. Click the View Personnel button and verify that this time, as desired, an incomplete record was not added to the database table.
frmViewPersonnel After Rollback
15. Click here for text description of this image.
16. You have seen how we used the try/catch block to catch an unexpected error. You may have noticed that if you enter bad data for the dates, an exception is thrown. Go back to the validation code you added in the frmPersonnel code and add a try/catch with logic to prevent an invalid date from causing a server error.
17. In the Week 3 and Week 5 labs, you learned how to validate code once the page was posted back to the server. There is some validation that must be done on the server because it requires server resources such as the database. Some validation can also be done on the client. If you can do validation on the client it saves a round trip to the server, which will improve performance. In this approach, we will check values before the page is submitted to the server for processing. Normally, there is a combination of server and client validation used in a web application. ASP.Net includes validation controls which will use JavaScript on the client to perform validation. You will find these controls in the Validation group in the toolbox.
18. Add validation controls to the frmPersonnel form as follows: For the first and last name, make sure each field has data in it. Use the RequiredFieldValidator for this. Add the control to the right of the text box you are validating. The location of the validator control is where the error message (if there is one) will appear for the control you link the validator to. You will be adding one validator control for each text box you want to validate. Remember to set the ControlToValidate and ErrorMessage properties on the validator control. Making this change eliminates the need for the server-side check you were doing previously. Use a regular expression validator to check that the start and end date are in the correct format.
frmPersonnel Validation Controls
19. Click here for text description of this image.
20. Remove the View Personnel and Cancel buttons from the frmPersonnel form as they will cause a Postback and invoke the client-side editing you just added. The user is able to get to the View Personnel from the main form and from the personnel verification screen, so there is no need for these buttons now.
21. Because you have entered data in this lab that is invalid and those partial records are in the database, you will need to add the ability to remove or update data. Add a new main form option called Edit Employees. Add the link and image for this. This option will take the user to a new form called frmEditPersonnel.
frmMain with links added
22. Click here for text description of this image.
23. Add the new form frmEditPersonnel. On frmEditPersonnel, add the CoolBiz log at the top of the form. Add a label that says “Edit Employees.” Add a GridView control with an ID of grdEditPersonnel.
24. You will now add a SQLDataSource to the page. You will be using a databound grid for this form unlike the previous grids, in which you added as unbound (in the designer).
25. Add a new SQLDataSource control to the frmEditPersonnel in the design view. This is not a visible control; that is, it will only appear in design view but the user will never see it. Note: If you change the folder name or location of your database, you will need to reconfigure the data source (right-click on the data source control and select the “Configure Data Source” option.
26. There is a small > indicator in the design view of the SQL Data Source control you added if the configuration menu is collapsed (press it to open the menu), or there is a < with the menu displayed. From the data source menu, select “Configure Data Source.” 27. Press the New Connection button and select the database. 28. Press the Next button. 29. When asked if you want to save the connection in the application configuration file, check the Yes check box and press Next. 30. Select the tblPersonnel table. 31. Select all columns (you can use the * for this). 32. Press the Advanced button and check the Generate Insert, Update, and Delete option and press the OK button. 33. Press the Next button. 34. Press the Test Query button and make sure everything works as it is supposed to. If it does not repeat the above steps to make sure you did everything properly. Press the Finish button. 7. Click on the grid you added in the design view and expand the properties menu (the little > in the upper right of the control). Choose the data source you just added. On the GridView tasks menu, select Edit columns. Add an Edit, Update, and Cancel Command field. Add a Delete Command field. Press OK. You can now test the grid, which is a fully functioning Update and Delete grid. Try it out!
Edit Employees
8. Click here for text description of this image.
9. Hints: Make sure you re-establish your database connection if you copied the files from a previous lab.
In order to keep the validation controls from causing wrapping, you may want to increase the Panel width.
A regular expression for mm/dd/yyyy is this:
^(0[1-9]|1[012])[- /.](0[1-9]|[12][0-9]|3[01])[- /.](19|20)\d\d$
Experiment with the editable grid and command buttons for different display styles.
STEP 3: Test and submit (10 points)
29. Once you have verified that everything works as it is supposed to, save your project, zip up all files, and submit in the Dropbox.
NOTE: Make sure you include comments in the code provided where specified (where the ” // Your comments here” is mentioned) and for any code you write, or else a five point deduction per item (form, class, function) will be made.
iLAB OVERVIEW
Scenario/Summary
In this lab, we will start with the form we created in Week 2 (frmPersonnel) and add functionality to INSERT records into a database table and SELECT records for display to the user. We will create a typed dataset, a Data Layer class, several functions to access the data, and a connection to a database. We also will add a search form to allow the user to search records in the database and display the results of that search.
Instructions for Week 4 iLab: Web Forms with Database Interaction
Deliverables
All files are located in the subdirectory of the project. The project should function as specified: When you press the Submit button in frmPersonnel, a record should be saved in the tblPersonnel table having the FirstName, LastName, PayRate, StartDate, and EndDate you entered on the form. Add a search feature to the project. Update your main navigation page with the new options. Once you have verified that it works, save your website, zip up all files, and submit it in the Dropbox.
iLAB STEPS
STEP 1: Data Layer (10 points)
1. Open Microsoft Visual Studio.NET 2008.
2. Click the ASP.NET project called PayrollSystem to open it.
3. Open the clsDataLayer class and add the following function:
// This function saves the personnel datapublicstaticbool SavePersonnel(string Database, string FirstName, string LastName,string PayRate, string StartDate, string EndDate){bool recordSaved;try{// Add your comments hereOleDbConnection conn =newOleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;"+"Data Source="+ Database);conn.Open();OleDbCommand command = conn.CreateCommand();string strSQL;// Add your comments herestrSQL ="Insert into tblPersonnel "+"(FirstName, LastName, PayRate, StartDate, EndDate) values ('"+FirstName +"', '"+ LastName +"', "+ PayRate +", '"+ StartDate +"', '"+ EndDate +"')";// Add your comments herecommand.CommandType = CommandType.Text;command.CommandText = strSQL;// Add your comments herecommand.ExecuteNonQuery();// Add your comments hereconn.Close();recordSaved = true;}catch(Exception ex) {recordSaved = false;}returnrecordSaved; } |
4. In the frmPersonnelVerified form, go to the Page_Load() event and add the following code after the existing code (but in the Page_Load event handler):
// Add your comments hereif(clsDataLayer.SavePersonnel(Server.MapPath("PayrollSystem_DB.mdb"),Session["txtFirstName"].ToString(),Session ["txtLastName"].ToString(),Session ["txtPayRate"].ToString(),Session ["txtStartDate"].ToString(),Session ["txtEndDate"].ToString())){txtVerifiedInfo.Text = txtVerifiedInfo.Text +"\nThe information was successfully saved!";}else{txtVerifiedInfo.Text = txtVerifiedInfo.Text +"\nThe information was NOT saved."; |
5. Add comments for all code containing // Add your comments here.
6. Test your work to make sure no errors occur! (Make sure to put in valid date values for the date data entry fields).
STEP 2: Data Display and Search (10 points)
7. Using the skills you learned in Week 3, create a new DataSet for the tblPersonnel table (called the DataSet dsPersonnel).
8. Using the skills you learned in Week 3, create a new function called GetPersonnel in the clsDataLayer class. This function should retrieve all data from the tblPersonnel table and return it in the form of a dsPersonnel DataSet. Use the GetUserActivity function as an example.
9. Create a new Web form called frmViewPersonnel.
10. Using the skills you learned in Week 3, add a GridView control (called grdViewPersonnel) to the form. This GridView control will be used to display data from the tblPersonnel table. Add the CoolBiz logo at the top of the page and make sure it links back to frmMain.
11. Add the following code to the Page_Load() function in frmViewPersonnel:
if(!Page.IsPostBack) {// Declare the DataSetdsPersonnel myDataSet =newdsPersonnel();// Fill the dataset with what is returned from the functionmyDataSet = clsDataLayer.GetPersonnel(Server.MapPath("PayrollSystem_DB.mdb"));// Set the DataGrid to the DataSource based on the tablegrdViewPersonnel.DataSource = myDataSet.Tables["tblPersonnel"];// Bind the DataGridgrdViewPersonnel.DataBind();} |
12. Return to the frmPersonnel Web form and add a button ((ID) = btnViewPersonnel, Text = View Personnel) which, when clicked, will display form frmViewPersonnel.
13. Using the skills you learned in Week 3, open the frmPersonnelVerified form and add a button ((ID) = btnViewPersonnel, Text = View Personnel) which, when clicked, will display form frmViewPersonnel. NOTE: This is the same button with the same functionality that you added to form frmPersonnel in the previous step. Also add a new link and linked image to frmMain called View Personnel that will go to the new frmViewPersonnel page you created.
14. You will now add a search feature to allow the user to find and display data. The user will enter a last name and the web application will display the grid of employees with all employees that match that last name.
15. Create a new web form called frmSearchPersonnel. Add the hyperlinked Cool Biz logo to this page. Also add a new item on frmMain (with a link button and image button) called Search Personnel.
16. On the frmSearchPersonnel form, add a label that displays “Search for employee by last name:”. Next to the label, add a text box with an ID of txtSearchName. Add a button with an ID of btnSearch and set the text of the button to “Search”.
17. When the frmSearchPersonnel Search button is pressed, the frmViewPersonnel is displayed. At this point, no searching is actually happening, but you have the forms you need and the navigation working. Now you can focus on the coding you will need to do to have the grid only display matching employees.
18. Before calling the GetPersonnel method you added previously in the lab, get the value that is in the Request[“txtSearch”] item. When the form posts the search page results to the frmViewPersonnel, the name value pair for the search value is passed as part of the Request object. Assign this value to a string variable.
19. Modify the GetPersonnel method you added to include a new parameter called strSearch of type string. This parameter needs to be after the Database string parameter that is already in the method.
20. When calling the GetPersonnel method, pass the value you received to the strSearch parameter.
21. In the GetPersonnel method, you now need to use the passed in strSearch parameter value as part of the SQL string being used to retrieve data. You also need to add logic so that, if strSearch is empty or has no value, all employees are returned in the query.
22. Test the search so that when you enter a last name, employees with that last name are returned. Make sure that when you access frmViewPersonnel and you are not searching, all employees are returned.
23. Lab Hints:
Make sure you re-establish your database connection if you copied the files from a previous lab.
Before you pass the search value into the GetPersonnel method, make sure you check to see if the Request item is null. If it is, you need to pass an empty string into the method or check for null inside the method. If you don’t do this, you will get a server error. To check to see if an object is null, you compare the object to the keyword null.
To create an SQL statement that will search for a given last name in the tblPersonnel table, you can do the following (assume that the search variable was called strSearch).
“select * from tblPersonnel where LastName = ‘” + strSearch + “‘”
24. Add the new Search option and the View Employees option to your main navigation page.
STEP 3:Test and submit (10 points)
Run your project and test it as follows:
The frmMain form should be displayed first (set this form as your start page).
Homepage
Click on the Add New Employee hyperlink to go to the frmPersonnel data entry form. Click the View Personnel button on this form. The frmViewPersonnel form should be displayed in the browser, but at this point, there should not be any personnel listed (because you haven’t entered any yet).
Use the Back button in your web browser to return to the frmPersonnel form and enter some personnel data, similar to the following:
Entering Personnel Data
Now click the Submit button. The frmPersonnelVerified form should be displayed, showing the data you entered, and you should get a message saying that the data was successfully saved, like this:
Verifying Personnel Data
Finally, click the View Personnel data button on this form. The frmViewPersonnel form should be displayed and should show the personnel record you just entered, retrieved from the database, like this:
Viewing Personnel Data
You also should be able to view the employee records by clicking the link on the home page.
Test the search feature and make sure that entering no search string returns all the data and that typing in a last name will return all employees with the same last name.
Search
Search Results
NOTE: Make sure you include comments in the code provided where specified (where the ” // Your comments here” line appears) and for any code you write, or else a five point deduction per item (form, class, function) will be made.
iLAB OVERVIEW
Scenario/Summary
In this lab, we will demonstrate how to save user activity data in a database. We will be creating a new form to display the user activity data, a new dataset to contain the data, a data access class to structure the code, and a function within the data access class to save users’ activity data when users visit the Personnel form page (frmPersonnel.aspx). We will also be adding server side validation to the frmPersonnel for you added in the previous lab and update or main menu for the new functionality. INCLUDE A SCREENSHOT OF THE ASSIGNMENT SUCCESSFULLY RUNNING TO RECEIVE CREDIT
Deliverables
All files are located in the subdirectory of the project. The project should function as specified: When you visit the Personnel form page (frmPersonnel.aspx), a record should be saved in the tblUserActivity table with the IP address, form name accessed (frmPersonnel), and the date accessed. When you click the “View Activity” button, you should see at least one record with this information. When the user goes to the frmPersonnel web form and enters data the following business rules are to be enforced:
• Fields may not be empty or filled with spaces. If any field is empty, turn that field background color to yellow and add to/create an error message to be shown in the error label.
• The end date must be greater than the start date. If the end date is less than the start date turn both date fields yellow and add to/create an error message to be shown in the error label.
If all fields validate properly, then the session state items should be set properly and the user should see the frmPersonnelVerified form with all the values displayed. You will also add a new item to frmMain that will take the user to the new frmUserActivity form you added. Add the proper link and a hyperlinked image to allow the user to select this new option. Once you have verified that everything works, save your website, zip up all files, and submit in the Dropbox.
iLAB STEPS
STEP 1: Data Connection, Dataset and Data Access Class (10 points)
1. Open Microsoft Visual Studio.NET 2008.
2. Open the PayrollSystem website by clicking on it in the Recent Projects list, or by pulling down the File menu, selecting Open Website, navigating to the folder where you previously saved the PayrollSystem, and clicking Open.
3. Download the PayrollSystem_DB.MDB file from Doc Sharing and save it on your local computer. (Note: your operating system may lock or block the file. Once you have copied it locally, right click on the file and select Properties and then Unblock if available). Then add it to the PayrollSystem website as follows: In Visual Studio, in the Solution Explorer click Website, Add Existing Item, then navigate to the PayrollSystem_DB.MDB file you downloaded and click the Add button.
4. Now we need to create a new connection to the PayrollSystem_DB.MDB. To begin, click View Server Explorer.
5. When the Server Explorer toolbox appears, click the Connect to Database button.
6.When the Add Connection dialog appears, click the Change button. In the “Change Data Source” dialog, select MS Access Database File; Uncheck Always use this Selection; then click OK.
7. Click the Browse button to navigate to the PayrollSystem_DB.mdb file in your website folder, then click “Open”. (NOTE: Be sure you select the PayrollSystem_DB.mdb file in your PayrollSystem website folder, not the one you originally downloaded from Doc Sharing!) Click Test Connection. You should receive a message that the test connection succeeded. Click OK to acknowledge the message, then click “OK” again to close the Add Connection dialog.
8. The PayrollSystem_DB.mdb should be added to the Server Explorer. Expand the database, then expand the Tables entry under the database until you see tblUserActivity. Leave the Server Explorer window open for now as you will be returning to it in a moment.
9. Create a new dataset by selecting Website Add New Item. Under Templates, select the Dataset item. Enter dsUserActivity.xsd for the name. Click Add.
10. Click here for text discription of this image.
11. If the following message appears, select Yes. You want to make this dataset available to your entire website.
12. If the TableAdapter Configuration Wizard dialog appears, click Cancel. (We will be configuring a Data Adapter for this dataset later in C# code, so we do not need to run this wizard.)
13. Drag-and-drop the tblUserActivity table from the Server Explorer window into the dsUserActivity dataset in the editor window.
NOTE: If you see a message that says your connection uses a local data file that is not in the current project, that indicates you did not select the correct PayrollSystem_DB.mdb file when you created your data connection. To fix this problem, click No, then right-click on PayrollSystem_DB.mdb in the Server Explorer window and choose Modify Connection. Click the Browse button, navigate to the PayrollSystem_DB.mdb file that is in your PayrollSystem website folder, and click Open. Test the connection, then click OK.
14. Click the Save icon on the toolbar to save the dsUserActivity.xsd dataset.
15. Click here for text discription of this image.
16. (You can now close the Server Explorer window if you wish.)
17. Create a new class to contain the C# code that will access this dataset. To do so, click Website, Add New Item. In the Add New Item dialog, select the Class template, and enter clsDataLayer for the name. Make sure the Language is set to Visual C#. Click “Add”.
18. Click here for text discription of this image.
19. If the following message appears, select Yes. You want to make this class available to everything in your solution.
20. Add the following to the top of your class, below any other using statements created for you by Visual Studio:
// Add your comments hereusing System.Data.OleDb;using System.Net;using System.Data; |
21. Add the following three functions inside the squiggly braces for the “public class clsDataLayer” class, above the beginning of the “public clsDataLayer()” constructor:
// This function gets the user activity from the tblUserActivitypublicstaticdsUserActivity GetUserActivity(string Database){// Add your comments heredsUserActivity DS;OleDbConnection sqlConn;OleDbDataAdapter sqlDA;// Add your comments heresqlConn =newOleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;"+"Data Source="+ Database);// Add your comments heresqlDA =newOleDbDataAdapter("select * from tblUserActivity", sqlConn);// Add your comments hereDS =newdsUserActivity();// Add your comments heresqlDA.Fill(DS.tblUserActivity);// Add your comments herereturnDS;}// This function saves the user activitypublicstaticvoid SaveUserActivity(string Database, string FormAccessed){// Add your comments hereOleDbConnection conn =newOleDbConnection("PROVIDER=Microsoft.Jet.OLEDB.4.0;"+"Data Source="+ Database);conn.Open();OleDbCommand command = conn.CreateCommand();string strSQL;strSQL ="Insert into tblUserActivity (UserIP, FormAccessed) values ('"+GetIP4Address() +"', '"+ FormAccessed +"')";command.CommandType = CommandType.Text;command.CommandText = strSQL;command.ExecuteNonQuery();conn.Close();}// This function gets the IP Addresspublicstaticstring GetIP4Address(){string IP4Address = string.Empty;foreach(IPAddress IPA inDns.GetHostAddresses(HttpContext.Current.Request.UserHostAddress)) {if(IPA.AddressFamily.ToString() =="InterNetwork") {IP4Address = IPA.ToString();break;}}if(IP4Address != string.Empty) {returnIP4Address;}foreach(IPAddress IPA in Dns.GetHostAddresses(Dns.GetHostName())) {if(IPA.AddressFamily.ToString() =="InterNetwork") {IP4Address = IPA.ToString();break;}}returnIP4Address;} |
STEP 2: frmUserActivity, frmPersonnel, frmMain (10 points)
18. Create a new Web form called frmUserActivity. Switch to Design Mode and add a Label and GridView (found under the Toolbox, Data tab) having the following properties:
Property Value
Label – Text User Activity
GridView – (ID) grdUserActivity
19. Go to the Page_Load method and add the following code:
if(!Page.IsPostBack) {// Declares the DataSetdsUserActivity myDataSet =newdsUserActivity();// Fill the dataset with what is returned from the functionmyDataSet = clsDataLayer.GetUserActivity(Server.MapPath("PayrollSystem_DB.mdb"));// Sets the DataGrid to the DataSource based on the tablegrdUserActivity.DataSource = myDataSet.Tables["tblUserActivity"];// Binds the DataGridgrdUserActivity.DataBind();} |
20. Open the frmMain form, add a new link button and image button to point to the new frmUserActivity. Find an image to use for the image button and add the new option as View User Activity.
21. Go to the frmMain Page_Load and add the following code:
// Add your comments hereclsDataLayer.SaveUserActivity(Server.MapPath("PayrollSystem_DB.mdb"),"frmPersonnel"); |
22. On the frmUserActivity form, add the CoolBiz logo hyperlinked logo at the top of the page so that when clicked the user is returned to frmMain.
23. In the Solution Explorer, right click on the frmMain.aspx form and select Set As Start Page. Run your project. When you open the project, a record should be saved in the tblUserActivity table with the IP address, form name accessed (frmPersonnel), and the date accessed. When you click the View Activity button, you should see at least one record with this information.
24. You will now add server side validation code to the frmPersonnel page. Currently, when the Submit button is pressed, the frmPersonnelVerified page is displayed. This is because the frmPersonnelVerified page is set as the Submit button’s PostBackUrl property. Instead of having the page go directly to the frmPersonnelVerified page when the Submit button is pressed, we want to do some server side validation. If any of the validation rules fail, we will redisplay the frmPersonnel page with the fields in question highlighted in yellow with an error message displayed.
First, it is important to understand what is currently happening when the submit button is pressed. This is causing a postback of the form to the frmPersonnelVerified form. When this postback happens, all of the data in the fields on the frmPersonnel form are sent to the frmPersonnelVerified form as name value pairs. In the Page_Load code of frmPersonnelVerified these values are picked up from the Request object and displayed. Each name value pair will be in the Request object as the ID of the control containing the value and the value itself. We can pass data between pages by using Session state instead. In order to do validation on the values but still have the values visible on the frmPersonnelVerified page, we will need to change not only the PostBack URL of the frmPersonnel page but also how the frmPersonnelVerified form is getting the data – it will need to get it from Session state rather than from the Request object.
Make the following changes:
1. Clear the Submit button PostBackURLProperty on the frmPersonnel form.
2. In the btnSubmit_Click event handler get each value from the data entry fields and set Session state items for each.
3. Change the frmPersonnelVerified code behind to get the values from the Session state items you created in the previous step.
When you are done with these steps, you should be able to enter data on the frmPersonnel data entry form and then click the Submit button. The frmPersonnelVerified page should then be displayed with the values that were in the data entry fields on frmPersonnel.
Make sure this is all working before proceeding to the next steps.
25. Add a label to the frmPersonnel form with an ID of lblError. Do not place the label to the right or left of any of the controls on the form. Add it below the controls or above the controls. The text property of this label should be set to an empty string.
26. Add code to perform server side validation in response to the submit button being clicked. Here are the business rules we want to enforce (remember this will be server C# code in the frmPersonnel code behind): Fields may not be empty or filled with spaces. If any field is empty, turn that field background color to yellow and add to/create an error message to be shown in the error label. The end date must be greater than the start date. If the end date is less than the start date, turn both date fields yellow and add to/create an error message to be shown in the error label. If all fields validate properly then the session state items should be set properly and the user should see the frmPersonnelVerified form with all the values displayed.
27. Lab Hints: To set a value in session state do the following:
Session["txtFirstName"] = txtFirstName.Text; |
28. “txtFirstName” is the key and txtFirstName.Text is the value.
29. To get this same value back from the session we use the key and the Session object as follows:
Session["txtLastName"].ToString() |
30. There is a Trim method on the string object that will automatically remove spaces from the beginning and end of a string. Remember, you can turn an object like a Session item object into a string using the Convert class or just using it’s ToString() method.
31. You may want to create variables to work with for validation rather than using the Request item objects directly.
32. To turn a string into a DateTime object you can use the DateTime method Parse. If you had a date value stored in a string called strDate, you could turn it into a DateTime object like this:
DateTime myDateTimeObject = DateTime.Parse(strDate); |
33. You can compare two DateTime objects by using the DateTime.Compare method. If you had two DateTime objects called dt1 and dt2 you can check to see if dt1 is greater than dt2 by doing this:
if(DateTime.Compare(dt1,dt2) > 0) |
34. DateTime.Compare will return a 0 if the two dates are equal, a 1 if dt1 is greater than dt2, and a -1 if dt1 is less than dt2.
35. If you put in an invalid date for either of the date fields, you will get an exception/server error when trying to parse the values. We will address this in a later lab – for now make sure you enter valid dates (valid meaning a date in the form of mm/dd/yyyy).
36. If I had a TextBox control that was called txtAge and you wanted to set it’s background color you could do this:
txtAge.BackColor = System.Drawing.Color.Yellow; |
37. Remember to clear the PostBackURL property of the submit button!
STEP 3: Verify and submit (10 points)
28. View the video above on what functions your lab should have so far.
29. Run your project. When you open the project, and go to the main menu form a record should be saved in the tblUserActivity table with the IP address, form name accessed (frmPersonnel), and the date accessed. When you click the View Activity button you should see at least one record with this information. The validation and error display should work for entering data. All navigation and hyperlinks should work.
Once you have verified that it works, save your project, zip up all files, and submit in the Dropbox.
NOTE: Make sure you include comments in the code provided where specified (where the ” //Your comments here” is mentioned) and for any code you write, or else a five point deduction per item (form, class, function) will be made. You basically put two forward slashes, which start the comment; anything after the // on that line is disregarded by the compiler. Then type a brief statement describing what is happening in following code. Comments show professionalism and are a must in systems. As a professional developer, comments will set you apart from others and make your life much easier if maintenance and debugging are needed.
Lab Overview
Scenario/Summary
In this lab, we will demonstrate how to create an ASP.NET Web application using MVC. In this application we will create a new model and learn how to make our web application responsive.
Please watch the tutorials before each step.
Required Software
Microsoft Visual Studio.Net
Lab Steps
STEP 1: Create Razor Pages
Before every lab, you will want to make a copy of the previous lab so you always have a backup.
Open the Management Portal web application from Lab 1. In our previous lab we used a query string to pass data. This is not an ideal way to pass information. ASP.NET Core MVC uses a Model to store the data for a page. A model is a C# class that models the data for an app and is stored in the Models folder.
In the Solution Explorer, right click on Models and Select Add-> Class.
Name the class Employee.cs
We will add the following Properties and method for the Employee class. Note that the Id property is automatically set as a primary key. Any property named EmployeeId, EmployeeID, or Id is set as a primary key and the value is automatically generated. When coding by convention the identifiers in the controller, views, and models need to be the same.
public class Employee
{
public int Id { get; set; }
public string Name { get; set; }
public DateTime StartDate { get; set; }
public string Title { get; set; }
public decimal PayRate { get; set; }
public decimal Hours { get; set; }
public decimal CalculatePay()
{
return PayRate * Hours;
}
}
Next we will add an EmployeeController. This controller will run in response to GET and POST actions. Right click on the Controllers folder then choose Add->Controller, Choose an Empty controller.
Name this controller EmployeeController.cs
We are going to create an overloaded Salary() action that can handle both GET and POST responses and retrieve values from the Model we just created. To access the Model, we must include the following code at the beginning of the Controller code:
using ManagementPortal.Models;
This will prevent errors when we access the Models. If you forget to add this statement at the beginning of the code, Visual Studio intellisense will prompt you to add it later.
Now write the following code in your EmployeeController. Please note in the [HttpGet] Salary() action we are returning the view that corresponds to the current controller and action with the code return View(). In the [HttpPost] Salary() action we are passing the model to the view that corresponds to the current controller and action. This allows the view to bind to the model. The code is return View(model).
Also note in this code we are using ViewBag rather than ViewData. ViewBag is similar to ViewData and is also dynamic in which properties can be set, however properties in ViewBag look different. ViewData[“Salary”] versus ViewBag.Salary. You will come across both types of dynamic objects when you are developing web applications.
Add this code below the existing Index() action method
[HttpGet]
public IActionResult Salary()
{
ViewBag.Salary = 0;
return View();
}
[HttpPost]
public IActionResult Salary(Employee model)
{
ViewBag.Salary = model.CalculatePay();
return View(model);
}
In the above code the Get request will display a blank form to the user and the POST request will process the data that’s submitted.
Next we need to modify our view. The Salary.cshtml is a View in the home folder but we would like to move it and reorganize our Views better. Click on View and right click and choose Add-> New Folder and name the new folder Employee
Cut and paste the Salary.cshtml page from the Home folder to the Employee folder.
You may get a message box, click OK
Open the Salary.cshtml file. We will now bind the model to the view. At the top of the razor page add the following code:
@model Employee
Note: if you have an older version of Visual Studio, you may need the fully qualified name:
@model ManagementPortal.Models.Employee
We can now make use of the model to enter data on the form. Replace the code you previously had in the Salary.cshtml view to the one below. Make note of the form command. The action is Salary and the method is post. Note the action must be set to Salary in order for the Salary action in the controller to run. You will also notice that we can now use the properties from our model. Your code should look like the following:
@model Employee
Name: Pay Rate: Hours Worked: Salary:
Save and run your application. Our code is in the Employee controller and Salary View. So we will need to add /Employee/Salary at the end of our web address. It will look something like this in your URL (your port will most likely look different from this):- https://localhost:44359/Employee/Salary (Links to an external site.)
Enter in data in the form and click Calculate. You will notice that the salary field updates when you click Submit and the post method of the form runs.
STEP 2: Making an App Responsive
Because so many applications run on different devices such as laptops, phones, and tablets it is important to ensure your app looks good on every device. This is known as responsive web design and we will make our application mobile friendly. Bootstrap is a popular framework for responsive web design. By going to https://bootswatch.com/ (Links to an external site.) you can review some of the free themes for Bootstrap. You can download a css file from this site and add it to your project. You can also use Visual Studio to add font-awesome as well as jQuery for client side validation. Bootstrap is already installed in ASP.NET MVC Core web applications.
To add new client side libraries, in the Solution Explorer right click on the project name (ManagementPortal) and choose Add -> Client Side library.
In the dialog box type in font-awesome@
and press enter. You will see the font-awesome library appear. Click Install. You may have to click “I Accept” to accept the license agreement.
To view the bootstrap.css, in your solution explorer click on wwwroot/lib/bootstrap/dist/css and expand it to view the code.
We want to be sure this css file is used in all our web pages. All razor pages share the same default layout. This shared layout is located in the Views/Shared/_Layout.cshtml file. Open the _Layout.cshtml file
Here you will see the default layout for all pages. We will also add a link to font-awesome. Note that if you want to make a change to your pages, the _Layout.cshtml is where you can make this change. You can also override default the layout by adding Layout=null at the top of your .cshtml pages.
Add the line in bold below.
Next change the link for the main page. Right now it says “ManagementPortal” and the action is Index(). We will change it to Employees but leave the action as Index(). We will modify the Index() page later.
Save the layout. We will come back to it later. In the wwwroot folder, create a folder named images. Within that folder add the logo.jpg
from the Files section. Save it to your own computer first, then copy and paste it into the images folder.
To add this logo to all pages you will want to add it to the _Layout.cshtml. Open the Views/Shared/ _Layout.cshtml file and add the code for the logo at the end of the header. You will also add the jumbotron bootstrap class for the design. Feel free to research the jumbotron class as well as other bootstrap classes for user experience.
Now run your application and notice that the logo appears at the top of the page and the links are “Employees”, “Home”, and “Privacy”.
Navigate to the /Employee/Salary page and note the difference in appearance in your form.
Font-awesome allows you to work with icons and symbols to decorate your page. Go to https://fontawesome.com/ (Links to an external site.) and browse some of the icons shown on the site. These can be added to your forms and page by using the prefix fa or fas (for font awesome solid) and then the name of the icon. Icons must also be coded in an element such as a and there are no leading or trailing spaces. You may want to add a to your html code to include spaces.
In the Salary.cshtml razor page, add a font-awesome icon to the salary label:
Salary:
Image below:
Run your application and note the addition of the icon on your page.
STEP 3: On Your Own
Add the title to your Salary.cshtml page below the Name of the employee. Include the bootstrap classes to format the title label and input box. Customize your form by adding another font-awesome icon or additional bootstrap classes to improve the user experience. Search on the font-awesome site for icon class names. For example, shopping cart can be coded with . Review the bootstrap site or the w3schools site for bootstrap classes to add to your page: Bootstrap 3 Tutorial (w3schools.com). (Links to an external site.) Remember that the changes should be made to the Salary.cshtml page and not to the _Layout.cshtml razor page.
STEP 4: Submit
Save your work and run your Salary.cshtml page after step 3 and enter your full name (first and last), title, a pay rate and salary and click the Calculate button to show that it is working. You should have a nice user experience with icons, bootstrap css formatting and correct calculations. Save a screenshot of your working program to a Word document, and include screenshots of your code. Once you have verified that it works, submit the Word document. .
Be sure to add comments. Comments show professionalism and are a must in systems. As a professional developer, comments will set you apart from others and make your life much easier if maintenance and debugging are needed.
Step 1: Create Website and Home Page
In this Lab, we will learn how to create a simple ASP.NET Web application using Microsoft Visual Studio.NET. Then we will add to our application and perform calculations.
IMPORTANT: Please update your Visual Studio to the latest version of Visual Studio. Also, open Visual Studio Installer and be sure you have ASP.NET (Links to an external site.) and web Development, .NET desktop development, Universal Windows Platform development, and Desktop development for C#.
Open Microsoft Visual Studio and pick Create a New Project
Pick C#, All Platforms, and Web from the drop down list boxes. If you do not see C# or Web, please open the Visual Studio Installer and Install those applications. You should see ASP.NET Core Web Application (NOT .NET Framework). Choose ASP.NET Core Web Application and pick Next.
If you do not see ASP.NET Core Web application, you may see the following screen. If you see this screen, pick ASP.NET Core Web App (Model-View-Controller):
At the next screen, give your system the name ManagementPortal. Remember the location of your project and where it is saved and choose to place the solution and project in the same directory. Click Create.
On this next screen choose ASP.NET Core Web App (Model-View-Controller). Authentication should show “No Authentication”. Click Create.
After you click Create you will get the screen below.
Look at the Solution Explorer on the right side of the screen. You will see Controllers, Models, and Views. Click on each of those folders and note the contents.
Let’s start the program to see how it runs in the default browser. To run your Web Application, you can press Control+F5 or click the Green start arrow in the toolbar.
You should see the web page in the browser. Note that you have pages ManagementPortal, Home, and Privacy.
Close the web page. This will stop the application from running. You can also stop the application by pressing Shift+F5 or clicking the red box on the tool bar. We are going to modify the home page to display a message. The home page is in the Views/Home/Index.cshtml. Open the Index.cshtml page by double clicking on it.
The Index.cshtml is a Razor page. Razor pages allow you to combine C# code and HTML for a dynamic web experience.
For example, you can use an if statement or foreach loop with C# syntax by preceding the code with a @ symbol. This allows you to declare a razor code block. In the beginning of the cshtml code you may see the following:
@{
ViewData[“Title”] = “Home Page”;
}
The @ symbol indicates that the following block of code is C#. For now, we will start by using HTML. Modify the html code in the Index.cshtml to the following (note: leave the Razor code the same):
<div class=”text-center”>
<h1 class=”display-4″>Welcome to Our Site</h1>
<p>This site is here for all your management needs.</p>
</div>
Now save and run the application by clicking on the Green arrow. You should see the initial web page with a new message.
Close the web browser.
Click the Save button on the toolbar to save the changes.
Step 2: Add a Salary Calculator
Now that you have added a simple message to the index page, we would like to add a more complex web page. First we will add some data to the controller. This is not the ideal way to add data, but this exercise will illustrate how controllers and actions work. In the following weeks, we will add models that are a much better way of defining data. Open the HomeController.cs.
You will see several actions here. The Index() action is the action that runs when we run the program (Home/Index). We will add a new action called Salary. After the Index() action code, add the following code:
public IActionResult Salary()
{
return View();
}
The return View() will return a View Result Object for the view associated with this Action (the Salary view). We do not have a Salary view yet so we need to create one.
Go to Views/Home. Then right click and choose Add-> View.
Pick Razor-View Empty. Then name the view Salary.cshtml
The Salary View starts as a blank page. Add one <h1> tag to the salary.cshtml page. It should look like this:
@*
For more information on enabling MVC for empty projects, visit https://go.microsoft.com/fwlink/?LinkID=397860
*@
@{
}
<h1>Salary Calculator</h1>
To illustrate how controllers work, we will now run this program. Click run to run your application in a Web browser. You will notice that your page has an address similar to the following:https://localhost:44359/ (Note: your port number may be different than this one).
Now navigate to https://localhost:44359/Home/Salary by adding /Home/Salary to the end of your web page.
The page should look like the following:
The controller is the Home controller and the action is the Salary action. The view rendered is Salary.cshtml.
Let’s add more code to our Salary action to illustrate the HTTP Get action.
Open the HomeController.cs and modify the salary action to the following. Note that you are now passing three variables to your Salary action.
public IActionResult Salary(string name, int hours, int payRate)
{
ViewData[“Title”] = “Salary Calculator”;
ViewData[“Message”] = “Salary calculator for employee: ” + name;
ViewData[“Hours”] = hours;
ViewData[“PayRate”] = payRate;
return View();
}
We are passing a name, hours, and pay rate as arguments to Salary. These values will be passed in the querystring when we run our program. In later weeks we will explore a more secure method of passing data. This code also sets several key properties of ViewData. These properties are dynamically created so you can set any properties you want. To set a property you would use the code: ViewData[“myClass”] = “ASP.NET”. The key can be any value you want. Then to call the method in the view you would use: @ViewData[“myClass”]. The ViewBag is similar to ViewData and can also dynamically set keys and values.
Now we will modify our Salary.cshtml to display the ViewData properties and calculate the salary. Add the following code to your salary.cshtml
<div class=”container”> <h1 class=”mt-3″>@ViewData[“Title”]</h1>
<main>
<h2>@ViewData[“Message”]</h2>
<div align=”center”>
<table>
<tr>
<th>Hours Worked: </th>
<td>@ViewData[“Hours”] </td>
</tr>
<tr>
<th>Pay Rate: </th>
<td>@ViewData[“PayRate”] </td>
</tr>
<tr>
<th>Salary: </th>
<td>@(((int)ViewData[“Hours”]*(int)ViewData[“PayRate”]).ToString(“C2”))</td>
</tr>
</table>
</div>
</main>
</div>
Now we are ready to run our program. Try running the program and again navigating to /Home/Salary. You will notice that all the data values are 0
This is due to the fact that the Salary action is looking for three properties that are passed in the query string. Try running the program again and passing in three variables. The example below shows how you can pass the variables in the querystring. Please note your port number will be different than mine:https://localhost:44359/Home/Salary?name=Gina&hours=40&payRate=15
In this string the name is set to Gina, hours to 40 and payRate to 15. Enter your own name, hours, and payrate.
Take a screenshot of your web page showing your name, pay rate, and hours
Step 3: On Your Own
Add another ViewData object in your controller and display it in your salary.cshtml page. You do not need to pass it in the query string. This object will be similar to the Title. See example below with ViewData[“Description”]. Remember you need to change it in both the controller and the view.
CIS363A Lab 1 Create an Online Resume, CIS363A Lab 2 Create a Website Using Dreamweaver, CIS363A Lab 3 Create a Web Page Using CSS, CIS363A Lab 4 Create a Website with Slideshow, CIS363A Lab 5 HTML Form with Validation and Proper Designing, CIS363A Lab 6 JavaScript For New Year’s Eve,
