Welcome to AssignmentCache!

Search results for 'GU 371'

Items 21 to 30 of 326 total

per page
Page:
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5

Grid  List 

Set Ascending Direction
  1. WEB460 Lab 2 of 7 Creating and Using Master Pages Checkout Page

    WEB460 Lab 2 of 7: Creating and Using Master Pages

    Regular Price: $12.00

    Special Price $10.00

    WEB460 Lab 2 of 7: Creating and Using Master Pages

    Scenario/Summary
    In this Lab, you create a master page for our bookstore website and then modify the checkout and order confirm pages from last week's lab to use the master page.

    Deliverables
    The deliverables for this week's lab are the following:
    pgCheckOut.aspx
    pgCheckOut.aspx.cs
    pgConfirm.aspx
    pgConfirm.aspx.cs
    Web460Store.master
    Web460Store.master.cs
    web.config
    Please zip and submit the entire web project folder.

    Lab Steps
    STEP A: Create a New Web Site Project
    In this step, we set up a new project and copy the files from the Week 1 Lab into it. This allows us to begin our lab this week where we left off last week and to add common elements to both pages.
    1. To start this week's project, create a new Empty Web Application project.
    2. Copy the four files from last week's Lab into the folder for this new project. Be careful not to move the files. We want to work on a copy of last week's lab and leave the original untouched. The website folder should have the following files:
    pgCheckOut.aspx
    pgCheckOut.aspx.cs
    pgConfirm.aspx
    pgConfirm.aspx.cs
    web.config
    web.Debug.config ( optional: it depends on the version of Visual Studio you are using)
    3. Set pgCheckOut.aspx as the start page and test your application. It should perform just as it did last week.

    STEP B: Create a Master Page
    In this step, we add a master page to our project.
    1. Right-click on the name of your project and select Add => Add New Item ...
    2. Select Master Page as the type of item to add. Be sure that Place code in separate file. is checked.
    3. Name the master page Web460Store.master and click OK to create the maser page for our site.

    STEP C: Design Your Master Page
    Our master page contains elements that we want common to all pages on our website, such as the header, the footer, and two side-by-side content areas. We mark areas that content pages can fill with the ContentPlaceHolder tag.
    We also want a Label control that our content pages can modify to display messages directed to the user. Making the Label accessible to content pages requires editing the C# code for the master page, which we do in the next step.
    1. View the source for Web460Store.master. We first set the title and a content area in the head of the master page. Make any changes necessary to the <head> tag so that it matches the code below:
    <head runat="server">
    <title>WEB460 Book Store</title>
    <asp:ContentPlaceHolder id="HeadPlaceHolder" runat="server">
    </asp:ContentPlaceHolder>
    </head>
    2. Next we create the page template in the <body> of the master page. We use a table to assist with the layout. The first row of the table is the header for our page, displaying the company name and motto. It also contains the Label we will use to send messages to the user. The second table row has two content areas side by side for the website pages to place content and additional controls. The last row of the table is the page footer.
    Edit the <body> of your master page so that it looks like the following block of code:
    <body>
    <form id="form1" runat="server">
    <table style="padding: 10px; border: 1px solid black;">
    <tr style="background-color:lightcyan; text-align: center;">
    <td colspan="2">
    <!-- page header -->
    <h1>WEB 460 Book Store</h1>
    <h2>Providing you 100% more than 360 degrees</h2>
    <!-- Label for content pages to display user message -->
    <strong><span style="color:red;">
    <asp:Label ID="lblUserFeedBack" Runat="server">Welcome Traveler!</asp:Label>
    </span></strong>
    </td>
    </tr>
    <tr style="vertical-align: top;">
    <td>
    <!-- Left content area -->
    <asp:ContentPlaceHolder ID="ContentPlaceHolder1" Runat="server">
    </asp:ContentPlaceHolder>
    </td>
    <td>
    <!-- right content area -->
    <asp:ContentPlaceHolder ID="ContentPlaceHolder2" Runat="server">
    </asp:ContentPlaceHolder>
    </td>
    </tr>
    <tr style="background-color:lightgrey; text-align: center;">
    <td colspan="2">
    <!-- page footer -->
    Copyright DeVry University<br />
    <strong>User's GUID:
    <asp:Label ID="lblGUID" Runat="server" /></strong>
    </td>
    </tr>
    </table>
    </form>
    </body>

    STEP D: Expose the Label Control to Content Pages
    In this step, we modify the C# code file for our master page, Web460Store.master.cs, to modify text displayed on the Label controls.
    1. We need to establish set properties for the Label lblUserFeedback so that our content pages can change the message displayed to the user. Add the following method to the class Web460Store:
    public Label UserFeedBack
    {
    get { return lblUserFeedBack; }
    set { lblUserFeedBack = value; }
    }
    2. To provide a tool we can use for security in the future, we want to display the user GUID (globally unique identifier) for this page call. We only want to generate the GUID the first time the page is loaded (not on postback). We can accomplish this by adding the following code to the master page's Page_Load method:
    if (!Page.IsPostBack)
    {
    lblGUID.Text = System.Guid.NewGuid().ToString();
    }

    STEP E: Modify pgCheckOut to Use Our Master Page
    In this step, we modify pgCheckOut.aspx to use the master page we created earlier. Since the master page contains <head>, <body>, and <form> tags, we do not need those in our content page, so we will be removing them as part of this step. We also must map the content on this page to the ContentPlaceHolder controls on the master page.
    1. We begin by adding MasterPageFile="~/Web460Store.master" to the page directive to indicate that this page references our master page:
    <%@ Page Language="C#" AutoEventWireup="true" MasterPageFile="~/Web460Store.master" CodeFile="pgCheckOut.aspx.cs" Inherits="pgCheckOut" %>
    2. So we have access controls the master page has exposed to us, such as the Label for user feedback. We need to add the following directive next:
    <%@ MasterType VirtualPath ="~/Web460Store.master" %>
    3. We can then remove the <!DOCTYPE>, <html>, and <head> tags because we will be using the ones defined in the master page. Also remove the <body> and <form> tags, but leave the content.
    4. Next we map the body content to the two ContentPlaceHolder controls on the master page. The customer name, address, and phone number should be in the left content area (ContentPlaceHolder1) and the credit card information in the right content area ( ContentPlaceholder2 ). We bracket the content for each with an ASP.NET Content control.
    5. Before the Label control for the customer's first name, place the line:
    <asp:Content ID="ContentArea1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
    6. Just after the line for the phone number TextBox control, close the first content area with the line:
    </asp:Content>
    7. On the next line, we begin the second content area the same way as the first begins:
    <asp:Content ID="ContentArea2" ContentPlaceHolderID="ContentPlaceHolder2" Runat="Server">
    8. We close the second content area at the end of the file, after the submit button:
    </asp:Content>
    At this point, the pgCheckOut.aspx design view should look similar to the following:

    STEP F: Update the Master Page User Feedback Label
    On pgCheckOut.aspx we want the user to enter billing information. We can modify the master page Label lblUserFeedback by updating the master page's UserFeedBack property we setup earlier. So this happens when the page is loaded, making the Page_Load method in pgCheckOut.aspx.cs look like this:
    protected void Page_Load(object sender, EventArgs e)
    {
    Master.UserFeedBack.Text = "Please enter billing information.";
    }

    STEP G: Modify pgConfirm to Use the Site Master Page
    In this step, we transform the confirmation page pgConfirm to use the website master page in a similar way to how we modified pgCheckOut.
    First, modify pgConfirm.aspx:
    1. Remove unneeded HTML tags and modify the page directives as necessary.
    2. The left content area should contain the customer's name and address.
    3. The right content area should contain the customer credit card information and the Submit Order button.
    4. Remove the status label lblStatus because we will use the master page's user feedback Label.
    Then, because we removed lblStatus, we need to modify pgConfirm.aspx.cs:
    5. When the page first loads, it should display the user feedback message:
    Please confirm your billing information.
    6. After the user presses the Submit Order button, the user feedback should be:
    Your order has been submitted for processing.
    7. If there is an exception thrown by PreviousPage.IsCrossPagePostBack, it should display the message:
    Sorry, there was an error processing your request.
    When the application is rTuonpning, pgConfirm should appear similar to the following:

    STEP H: Finalize Your Lab
    1. Save your work!
    2. Test it!
    3. Make changes as appropriate until it works.
    4. Remember to add comments for each step being performed.

    Learn More
  2. WEB460 Lab 1 of 7 Basic ASP Page and Cross-Page Posting CheckOut Page

    WEB460 Lab 1 of 7: Basic ASP Page and Cross-Page Posting

    Regular Price: $12.00

    Special Price $10.00

    WEB460 Lab 1 of 7: Basic ASP Page and Cross-Page Posting

    Scenario/Summary
    In this week's lab assignment, we'll be developing credit card information checkout pages of an online book store. Such pages are necessary in any developed e-commerce application. In these pages, users are required to enter information related to their payment and shipping options.
    We will develop two pages. On the first page, the user provides personal, payment, and shipping information for the order submitted. The second page summarizes the user's input and requires the user to confirm.

    Learning Objectives
    Create an ASP.NET web project in Visual Studio 2010 or Visual Studio 2012.
    Create and design ASP.Net web forms.
    Cross-page posting in ASP.NET
    How to use ASP.NET web server controls (DropDownList, TextBox, RadioButtonList, Label, and Button)
    Exception handling

    Deliverables
    A zip archive of the ASP.NET Application implementing cross-page posting consisting of the following files:
    – pgCheckOut.aspx web form with all server controls defined in requirements
    – pgCheckOut.aspx.cs with code for cross-page posting
    – pgConfirm.aspx web form with all server controls defined in requirements
    – pgConfirm.aspx.cs with code for cross-page posting and exception handling

    Lab Steps
    STEP A: Create a New Web Site Project
    1. Go to the File menu and select New. From the New sub-menu, select Web Site to create a new Web Site project.
    2. In the New Web Site dialog box, select the language you want to use in developing your web application; for our applications choose Visual C#.
    3. Select ASP.NET Empty Web Site to create a project with only a web.config file.
    4. Then specify the location of your project or website. Note that in ASP.NET, you have the option of creating your website in different locations, whether in any folder on your local file system, on the local IIS server you have on your computer, or on a remote HTTP or FTP server. ASP.NET has an integrated IIS server with the Visual Studio .Net IDE.
    I recommend using the default Web Sites folder in the Visual Studio project folder. This allows the development of web applications without the hassle of setting up an IIS server on your computer. If you don't have IIS server installed on your computer, this is the best option to select for your lab.

    STEP B: Create and Design a New Web Form, pgCheckOut.aspx
    1. Add the first web form to the web application by right-clicking on the project name and selecting Add New Item. Name the web form pgCheckOut.aspx.
    2. Add the controls in the table below to the form. If desired, you can visually layout the form using HTML and CSS after adding the controls.
    The first column in the table shows the data the control represents or their label, the second column is the type of control, and the last column is the ID or name of the actual control. If the Visual Studio web form Toolbox Pane is not displayed, you can show it by going to the View menu and selecting Toolbox. All of these controls can be found in the Toolbox Pane.
    Data or Label Control Type Control ID or Name
    First Name TextBox txtFirstName
    Last Name TextBox txtLastName
    Street TextBox txtStreet
    City TextBox txtCity
    State TextBox txtState
    Payment Method RadioButtonList rblCCType
    Credit Card Number TextBox txtCCNumber
    Submit Button btnSubmit
    Phone Number TextBox txtPhone

    3. When the user clicks on the submit button, pgConfirm.aspx should be displayed. This is done with cross-page posting. To implement this, set the PostBackUrl property of the Submit button to ~/pgConfirm.aspx. This will cause the pgCheckOut.aspx to post user requests to the web page pgConfirm.aspx, which we will create shortly.

    STEP C: Add Code to the pgCheckOut.aspx Form (to Read User Input and Implement Cross-page Posting)
    Implement public methods in the pgCheckOut.aspx.cs code file to expose the form's control values to other pages. The code below is an example of how to retrieve the value of the txtFirstName and txtLastName.
    Sample Method to Get Control Values
    public TextBox FirstName
    { get { return txtFirstName; } }
    public TextBox LastName
    { get { return txtLastName; } }

    STEP D: Create and Design Another Web Form, pgConfirm.aspx
    1. Add the second web form to your web application. Name the form pgConfirm.aspx.
    2. Add label controls to display the user input values for the name, address, credit card type, and credit card number.
    This allows the user to review and confirm order information before final submission. Add the controls in the table below to the form. The application will fill in the text displayed by the labels, so you don't need to. You should provide additional labels that describe these values for the user.
    Control Type Control ID or Name Control Purpose
    Label lblName Holds the concatenation string of first name and last name entered in pgChekout.aspx
    Label lblAddress Holds the concatenation of all address-related fields user input in pgCheckOut.aspx
    Label lblCCType Displays the credit card type the user selected in pgCheckOut.aspx
    Label lblCCNumber Displays the credit card number the user entered in pgCheckOut.aspx
    Label lblStatus Displays the message of any run time exception that might happen during run time
    Button btnSubmit When the user clicks on the submit order button, this displays a note to the user that his or her order was submitted successfully. You should use the status label to display the message.

    STEP E: Add Code to the pgConfirm.aspx Form (to Allow User to Verify Order Input and Submit for Final Processing)
    1. In the pgConfirm.aspx page, add the following code to the PreviousPageType directive to the pgConfirm.aspx file, and set it to the pgCheckOut.aspx.
    <%@ Page Language="C#" AutoEventWireup=“true" CodeFile="pgConfirm.aspx.cs" Inherits="pgConfirm" %>
    <%@ PreviousPageType VirtualPath="~/pgCheckOut.aspx" %>
    2. Next, in the Page_Load() event of the pgConfirm.aspx.cs code page, check whether there is any cross-page posting by checking whether there is a cross-page postback, and set the values of the label controls with the corresponding user input values from the previous page as shown below. Be sure to implement for all controls on the form.
    3. Enclose your code in a try/catch block to handle any run time exception thrown by the application for any reason, as shown below.
    4. Add code to have lblStatus display the message of any thrown exception. Don't forget to add comments explaining what each line of code does.
    pgConfirm Page_Load method
    protected void Page_Load(object sender, EventArgs e)
    {
    try
    {
    if (PreviousPage.IsCrossPagePostBack)
    {
    lblName.Text = PreviousPage.FirstName.Text + " " + PreviousPage.LastName.Text;
    // Your code to set other form labels goes here
    }
    }
    catch (Exception error )
    {
    lblStatus.Text = error.Message;
    }
    }

    STEP F: Compile, Test, Save, and Submit Your Project
    1. Save your work!
    2. Test it! Make changes as appropriate until it works.
    3. Remember to add comments for each step being performed.
    4. Please zip and submit the entire web project folder.

    Learn More
  3. ITSD322 Unit 4 Java Billboard Sign console program

    ITSD322 Unit 4 Java Billboard Sign console program

    Regular Price: $20.00

    Special Price $15.00

    ITSD322 Unit 4 Java Billboard Sign console program

    One of the most useful features of any programming language is recursion and control structures, decisions and loops. Recursion and loop structures allow programs to repeat actions without duplicating code.

    This console application focuses on your understanding of object oriented programming, control structures, and arrays.

    Create an application that manipulates a billboard sign. Use the following guidelines:

    Main Program:
    The main program must create an object of Billboard class (see below for details).
    The main program must include a menu to allow a user to select a function of the Billboard object.
    The menu must repeat (using a loop) until the user exits the program.
    The application must exit upon user request.

    Billboard Class:
    The program must include a Billboard class (separate from the main program class) that is able to store and display the text for the completed Billboard advertisement.
    The Billboard class must include variables for data input.
    The Billboard class must allow the user to define a custom message.
    The Billboard class must include 3-4 predefined messages that can be set as the message in the billboard.
    Add one method of your choice that can be used to manipulate the message in some way, such as reversing the text or capitalizing the letters.

    Completion Tasks:
    Use comments in your code to demonstrate your understanding of each statement.
    Make sure the program runs correctly before submission. (Your instructor is here to help!)
    ZIP your project folder and submit the file to the portal for grading. (There is no Word document for this assignment.)

    Learn More
  4. CIS115 Course Project Guess The Number

    CIS115 Course Project Guess The Number

    Regular Price: $15.00

    Special Price $12.00

    CIS115 Course Project Guess The Number

    You will create a program that will ask the user to guess a number between 1 and 10. The pseudocode is below. Be sure to import random at the beginning of your code and use a comment block explaining what your program does

    #Guess the number week 4
    #Name:
    #Date:
    #Random number, loop while true
    #ask user for number.
    #if number is too high or too low, tell user, if they guessed it break out of loop

    Display "Welcome to my Guess the number program!"
    random mynumber
    while True
     Display "Guess a number between 1 and 10"
     Get guess
     if (guess<mynumber)
      Display "Too low"
     else if (guess>mynumber)
      Display "Too high"
     else if (guess==mynumber)
      Display "You guessed it!"

    When you run your program the result should be something like this:
    Welcome to my Guess the number program!

    Please guess a number between 1 and 10: 5
    Too high
    Please guess a number between 1 and 10: 4
    Too high
    Please guess a number between 1 and 10: 3
    Too high
    Please guess a number between 1 and 10: 2
    You guessed it!

    Be sure to submit your assignment

    Learn More
  5. CIS407 Lab 7 of 7 Error Notification Via E-Mail

    CIS407 Lab 7 of 7: Error Notification Via E-Mail

    Regular Price: $12.00

    Special Price $10.00

    CIS407 Lab 7 of 7: Error Notification Via E-Mail

    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.

    STEP 1: Business Layer Functionality

    1. Open Microsoft Visual Studio.NET.

    2. Click the ASP.NET website named PayrollSystem to open it.

    3. Create a new class called clsBusinessLayer.

    4. Add the following code in the clsBusinessLayer class:
    // **** Add the following at the top of the class file,
    // Add your comments here
    using System.Net.Mail;
    //**** Add the following code inside the body of public class clsBusinessLayer ****
    public static bool SendEmail(string Sender, string Recipient, string bcc, string cc,
    string Subject, string Body)
    {
    try {
    // Add your comments here
    MailMessage MyMailMessage = new MailMessage();
    // Add your comments here
    MyMailMessage.From = new MailAddress(Sender);
    // Add your comments here
    MyMailMessage.To.Add(new MailAddress(Recipient));
    // Add your comments here
    if (bcc != null && bcc != string.Empty) {
    // Add your comments here
    MyMailMessage.Bcc.Add(new MailAddress(bcc));
    }
    // Add your comments here
    if (cc != null && cc != string.Empty) {
    // Add your comments here
    MyMailMessage.CC.Add(new MailAddress(cc));
    }
    // Add your comments here
    MyMailMessage.Subject = Subject;
    // Add your comments here
    MyMailMessage.Body = Body;
    // Add your comments here
    MyMailMessage.IsBodyHtml = true;
    // Add your comments here
    MyMailMessage.Priority = MailPriority.Normal;
    // Add your comments here
    SmtpClient MySmtpClient = new SmtpClient("localhost");
    //SMTP Port = 25;
    //Generic IP host = "127.0.0.1";
    // Add your comments here
    MySmtpClient.Send(MyMailMessage);
    // Add your comments here
    return true;
    } catch (Exception ex) {
    // Add your comments here
    return false;
    }
    }     

    STEP 2: Integration

    5. Open the frmLogin Web form code behind the file and add the following code to the body of the if (dsUserLogin.tblUserLogin.Count < 1) statement, just above the return statement:
    // Add your comments here
    // Add your comments here
    if (clsBusinessLayer.SendEmail("youremail@yourdomain.com",
    "receiver@receiverdomain.com", "", "", "Login Incorrect",
    "The login failed for UserName: " + Login1.UserName +
    " Password: " + Login1.Password))
    {
    Login1.FailureText = Login1.FailureText +
    " Your incorrect login information was sent to receiver@receiverdomain.com";
    }
    NOTE: Change the youremail@yourdomain.com (Links to an external site.)Links to an external site. and receiver@receiverdomain.com (Links to an external site.)Links to an external site. to your e-mail and someone else's e-mail for testing.

    6. Optional: Perform this step only if you are doing this lab using Visual Studio installed on your own computer and you have administrative rights on your computer. If you are doing this lab using the Lab (Citrix) server, or if you do not have access to IIS, skip to Step 8.

    7. In previous versions of Windows, the SMTP server was built into IIS. Now we will need to get a separate one. On the Microsoft Codeplex site is an SMTP server called smtp4dev, specifically designed for development environments. Pages 652–653 in the text discuss how to download and use smtp4dev. The site is http://smtp4dev.codeplex.com. Click on Downloads. Another example is Papercut, downloadable at:http://papercut.codeplex.com/ You can use either smtp server.
     
    Test the e-mail by logging in as someone other than Mickey or Minnie. You should receive an email to the SMTP client.
     
    8. 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 that we are doing for the user role, but it still allows a user to get to pages that 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. For example:
    if (Session["SecurityLevel"] != "A")
    {
    Response.Redirect("frmLogin.aspx");
    }

    9. 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.configfile before the </system.web> tag.
    <authentication mode="Forms">
    <forms loginUrl="frmLogin.aspx" />
    </authentication>
    <authorization >
    <deny users="?" />
    </authorization>

    10. 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, 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);
    If you receive an error when you enter this in the code, right click on the line and choose Resolve->Using System.Web.Security

    11. 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 that 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 visit. Once you log in 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 username that is not Mickey or Minnie (i.e., a username that is not found in tblUserLogin). An e-mail should be sent to the recipient@recipientdomain.com (Links to an external site.)Links to an external site. e-mail address.

    13. Test that frmMain reconfigures properly based on user role. Make sure that the user cannot bypass the login page.
    Once you have verified that everything works, save your website, zip up all files, and submit them.
    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 Lab (Citrix) server for this lab or if you were not able to download and install smtp4dev.
    NOTE: Make sure that 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.

    Learn More
  6. CIS407 Lab 6 of 7 login and security levels Login Page

    CIS407 Lab 6 of 7: login and security levels

    Regular Price: $12.00

    Special Price $10.00

    CIS407 Lab 6 of 7: login and security levels

    STEP 1: Login Form

    1. In order to do this lab, we need to assign a primary key to the tblUserLogin table. This will allow us to modify the user login table from our Manage Users form that we will create later. Go to Windows Explorer and open the PayrollSystem_DB.accdb. Set the UserID as the Primary key and save the table. Close the database.

    2. Open Microsoft Visual Studio.NET.

    3. Click the ASP.NET website named PayrollSystem to open it.

    4. Create a new Web form named frmLogin.

    5. Add the ACIT logo to the top of the frmLogin page. Do not hyperlink the logo.

    6. Under the login controls, you will see Login. Drop the Login control onto the form. 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 in to the system.
     
    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.
     
    If you receive an error, add the following code to the web.config file right above the </configuration> line:
    <appSettings>
    <add key="ValidationSettings:UnobtrusiveValidationMode" value="None" />
    </appSettings>

    STEP 2: Login Check

    9. Create a new DataSet called dsUser. Use the table tblUserLogin as the database table for this dataset. Do this in the same way that you added datasets in the previous labs.

    10. Open the clsDataLayer and add the following function:
    // This function verifies a user in the tblUser table
    public static dsUser VerifyUser(string Database, string UserName, string UserPassword)
    {
    // Add your comments here
    dsUser DS;
    OleDbConnection sqlConn;
    OleDbDataAdapter sqlDA;
    // Add your comments here
    sqlConn = new OleDbConnection("PROVIDER=Microsoft.ACE.OLEDB.12.0;" +
    "Data Source=" + Database);
    // Add your comments here
    sqlDA = new OleDbDataAdapter("Select SecurityLevel from tblUserLogin " +
    "where UserName like '" + UserName + "' " +
    "and UserPassword like '" + UserPassword + "'", sqlConn);
    // Add your comments here
    DS = new dsUser();
    // Add your comments here
    sqlDA.Fill(DS.tblUserLogin);
    // Add your comments here
    return DS;
    }   

    11. Double-click on the login control that you added. Add the following code to the login control Authenticate event handler:
    // Add your comments here
    dsUser dsUserLogin;
    // Add your comments here
    string SecurityLevel;
    // Add your comments here
    dsUserLogin = clsDataLayer.VerifyUser(Server.MapPath("PayrollSystem_DB.accdb"),
    Login1.UserName, Login1.Password);
    // Add your comments here
    if (dsUserLogin.tblUserLogin.Count < 1)
    {
    e.Authenticated = false;
    return;
    }
    // Add your comments here
    SecurityLevel = dsUserLogin.tblUserLogin[0].SecurityLevel.ToString();
    // Add your comments here
    switch (SecurityLevel)
    {
    case "A":
    // Add your comments here
    e.Authenticated = true;
    Session["SecurityLevel"] = "A";
    break;
    case "U":
    // Add your comments here
    e.Authenticated = true;
    Session["SecurityLevel"] = "U";
    break;
    default:
    e.Authenticated = false;
    break;
    }

    STEP 3: User Authentication, Test and Submit

    12. Open the frmPersonnel form and add the following code to its Page_Load() function:
    // Add your comments here
    if (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 ID
    Annual Salary Calculator linkbtnCalculator imgbtnCalculator
    Add New Employee linkbtnNewEmployee imgbtnNewEmployee
    View User Activity linkbtnViewUserActivity imgbtnViewUserActivity
    View Personnel linkbtnViewPersonnel imgbtnViewPersonnel
    Search Personnel linkbtnSearch imgbtnSearch
    Edit Employees linkbtnEditEmployees imgbtnEditEmployees

    16. Modify the main form so that the following options are turned off for nonadmin users:
    - Add New Employee
    - View User Activity
    - 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 ACIT logo that is hyperlinked as you did in previous assignments.
    - For the security level of the user, use a dropdown list control to allow the user to select from A or U.
    - Name the controls with names that make sense.
    - Add code as appropriate to the code behind and clsDataLayer. Note: You will need to create a SaveUser function that is very similar to the SavePersonnel function. Use the following as a guide:
    public static bool SaveUser(string Database, string UserName, string Password, string SecurityLevel)
    When creating the SaveUser function, be sure to insert the data into the tblUserLogin table with columns: userName, UserPassword, and SecurityLevel.

    19. Hints:
    - Make sure you reestablish your database connection if you copied the files from a previous lab.
    - Update any DataSource controls that you added with the new Payroll database location.
    - You can turn a control on or off by setting its Visible property.
    - You can add a data entry form for new users and a grid displaying all users all on the same form.
    - To force a gridView to refresh, call its DataBind method in the btnAddUser_click event handler. For example, use the following code in the btnAddUser_click (be sure to include an Else condition as well if the user was not added successfully):
    if (clsDataLayer.SaveUser(Server.MapPath("PayrollSystem_DB.accdb"), txtUserName.Text, txtPassword.Text,ddlSecurityLevel.SelectedValue))
    {
    lblError.Text = "The user was successfully added!";
    grdUsers.DataBind();
    }

    20. Test your application to make sure that you are logging in with a valid user ID. Try to log in with both Minnie and Mickey and make sure that the UI adjusts by the role properly. Make sure that 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 it.
    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 5-point deduction per item (form, class, function) will be made.

    Learn More
  7. WEB240 Week 1 HTML Basics

    WEB/240 Week 1 HTML Basics

    Regular Price: $8.00

    Special Price $5.00

    WEB/240 Week 1 HTML Basics

    Using the course software and Week One Template as a starting point, create a new HTML webpage and include the following:
    Write a code to display your name in the largest-size heading element.
    Write the markup language code for an unordered list to display the days of the week.
    Write the markup language code for an ordered list that uses uppercase letters to order the items. This ordered list will display the following: Spring, Summer, Fall, and Winter.
    Modify the following code snippet to indicate that the bolded text has strong importance:
     <p>A diagram of the organization of a website is called a <b>site map</b> or <b>storyboard</b>. Creating the <b>site map</b> is one of the initial steps in developing a website.</p>

    Submit your assignment.

     

    Learn More
  8. DAT 210 Week 1 Create an algorithm using pseudocode

    DAT 210 Week 1 Create an algorithm using pseudocode

    Regular Price: $10.00

    Special Price $8.00

    DAT 210 Week 1 Create an algorithm using pseudocode

    You work in the IT group of a department store and the latest analytics shows there is a bug that allows customers to go over their credit limit. The company's president has asked you to develop a new algorithm to solve this problem.

    Create your algorithm using pseudocode that determines if a department store customer has exceeded their credit limit. Be sure you gather the following inputs from the user:

    Account number
    Balance of the account
    Total cost of all the products the customer is looking to purchase
    Allowed credit limit

    After you gather the inputs, make sure your algorithm calculates if the user can purchase the products and provides a message to the user indicating if the purchase is approved or declined.

    Document your answers in a Microsoft® Word document.

    Review "Understanding Object-Oriented Programming" with Jungwoo Ryoo from Lynda.com® for additional guidance.

    Submit your document.

    Learn More
  9. Microsoft Visual Basic 2012 Shelly Cashman Chapter 6 Case Problem 8 Galaxy Hotel

    Microsoft Visual Basic 2012 Shelly Cashman Chapter 6 Case Problem 8 Galaxy Hotel

    Regular Price: $20.00

    Special Price $15.00

    Microsoft Visual Basic 2012 Shelly Cashman Chapter 6 Case Problem 8 Galaxy Hotel

    Create a requirements document and a Use Case Definition document, and design a Windows application based on the case project shown in Figure 6-135:

    The Galaxy Hotel ask you to write a Windows application that computes the occupancy rate of the hotel. Occupancy rate is a percentage that is equal to the number of rooms sold divided by the total number of room available. The hotel has seven floors. The user should use an InputBox function to respond to two questions about each floor. How many rooms are occupied on that floor? How many rooms on floor are vacant? Display which floor you are asking about in each question. Display how many rooms are occupied and vacant on each floor in a ListBox object. After the user has entered all the information, display the following results: the total number of rooms at hotel, the number of occupied rooms, the number of vacant rooms. Also display the occupancy rate as a percentage, such as 61%. Nonnumeric values should not be accepted. Do not accept negative numbers. Publish the application after testing it.

    Learn More
  10. Microsoft Visual Basic 2012 Shelly Cashman Chapter 6 Case Problem 5 Distance Traveled Calculator

    Microsoft Visual Basic 2012 Shelly Cashman Chapter 6 Case Problem 5 Distance Traveled Calculator

    Regular Price: $20.00

    Special Price $15.00

    Microsoft Visual Basic 2012 Shelly Cashman Chapter 6 Case Problem 5 Distance Traveled Calculator

    Design a Windows application and write the code that will execute according to the program requirements shown in Figure 6-132. Before writing the code, create an event planning document for each event in the program. Create a Use Case Definition document for the application.

    REQUIREMENTS DOCUMENT
    Date submitted: December 5, 2014
    Application title: Vacation Distance Calculator Windows Application

    Purpose: This application computes the number of miles traveled given the speed limit and the number of days traveled while driving cross country.

    Program Procedures: In a Windows application, enter the speed limit and the number of days you plan to travel across the country. You will enter the number of hours you would like to drive for each of the days, based on places you plan to visit as you drive and other factors. For example, the first day you plan to drive only 4 hours because you are driving after work. The application displays the distance that you are able to travel for the entire trip based on the speed limit and the hours driven.

    Algorithms, Processing, Conditions:
    1. The application opens displaying a title. The user enters the speed limit and the and number of days you plan to drive.
    2. The user clicks the Distance button to request the number of hours you plan to drive each day. The result of the total number of miles you plan to drive over the entire trip will be displayed.
    3. A File menu contains a Clear and an Exit option. The Clear menu item clears the result and the entered number of miles per hour and time traveled. The Exit menu item closes the application.

    Notes and Restrictions:
    1. Nonnumeric values should not be accepted.
    2. The number of hours for one day of travel should not exceed 20 hours.

    Comments:
    1. The application allows decimal entries.

    Learn More

Items 21 to 30 of 326 total

per page
Page:
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5

Grid  List 

Set Ascending Direction
[profiler]
Memory usage: real: 15204352, emalloc: 14749472
Code ProfilerTimeCntEmallocRealMem