VB/C#

Need Help in Visual Basic and C# Assignments?
We can help you if you are having difficulty with your Visual Basic Assignment. Just email your assignments at support@assignmentcache.com.
We provide help for students all over the world.

Items 41 to 50 of 170 total

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

Grid  List 

Set Ascending Direction
  1. POS 409 Week 1 C# Program Friends Name GUI

    POS 409 Week 1 C# Program Friends Name GUI

    Regular Price: $12.00

    Special Price: $10.00

    POS 409 Week 1 C# Program Friends Name GUI


    Design, implement, test, and debug a C# program that displays a Friend's name when button is clicked.


    Create a graphical user interface (GUI) with a button labeled "Friend's name".
    When the Friend's Name button is clicked, the program will display the name of the Friend in a label on the form.
    Add a button that will exit the program.
    Your name, date, project description and class name must be in the code as comments (similar to an APA title page).
    Your project must be properly documented (describe the use of variables, describe how a function or routine works, use proper naming conventions for a variables and labels).


    Options:
    Add a button that will change the color of the name label.
    Add a button that will change the location of the name label.
    Cycle through multiple names when the Friend's Name button is selected.


    Zip the files of the project together and submit the zipped file.

    Learn More
  2. POS 409 Week 2 Card Game War C# Program

    POS 409 Week 2 Card Game War C# Program

    Regular Price: $20.00

    Special Price: $15.00

    POS 409 Week 2 Card Game War C# Program


    Design, implement, test, and debug a C# program to simulate playing the card game War. Utilizing the C# random number generator, deal 26 sets of 2 cards each. This should be accomplished with only one click of a button. The "cards" should be values 1 through 13; 1 is an ace, two is a two, etc.; and 11 is a jack, 12 is a queen, and 13 is a king. Keep two counters - one for player 1 and one for player 2. As you deal the cards (ie, generate the numbers in a loop), if the first card is larger than the second, add 1 to player 1's counter. If the second card is larger than the first, add 1 to player 2's counter. For the purposes of this program, a 2 will beat an ace. Also, as you deal the cards, write the results to a text file. The results should contain the values of both cards dealt and which player won that deal. For example, the record written to the text file could say "Player 1 dealt 3, player 2 dealt 11, player 2 wins". It is not necessary to translate a 1 into "ace", an 11 into "jack", a 12 into "queen", or a 13 into "king". After 26 deals of cards, the results will be read from the text file and displayed on the form. Remember to utilize concepts learned in this week's reading (especially chapters 4 and 5 of Starting Out with Visual C#). The type of application to be developed is a Windows Forms application. Please note that graphics are not needed. This program is only a simulation; it is not intended to actually look like the user is dealing cards. Also please note that no complicated algorithms or logic is needed. You do not need to do any logic to ensure that 52 unique cards are dealt or anything related to the suit of the card. The assignment is simply to see how you do with the key concepts for this week.


    When the user clicks a Deal Cards button, the program will write the values of the cards "dealt" to each of the players as noted above. If I open the text file written, I should see 26 records, with three things on each record (the value of each card and the winner of the deal). If the deal is a tie, note it in the results.
    Notify the user in some way that the game is done and the file is written.


    After the file is written, the user may click a Display Game Results button to read the items back in and display the results in a textbox or listbox. When I look at the form after I click the Display Game Results button, I should see 26 entries on the form. Also create 2 labels on the form. In the first label, display the number of deals won by player 1 (such as "Player 1 won 10 deals"). In the second label, display the number of deals won by player 2.


    Include identifying information in the form of block comments at the top of each class in the project (programmer name, date, program description). Include adequate comments throughout the program, utilize meaningful names for controls, variables, fields, and forms. Include white space for readability purposes in the code. The focus of the project is on learning the C#.Net syntax. However, ensure the form is simple and easy to understand for the user. Refer to the Individual Assignment grading form to view grading criteria.
    Design a GUI for the program that will be intuitive for a novice user.


    Write the code for the program and test the results.


    Zip the files of the project together and submit the zipped file

    Learn More
  3. POS409 Week 3 Rolling Dice

    POS 409 Week 3 Option B Rolling Dice C# Program

    Regular Price: $15.00

    Special Price: $12.00

    POS 409 Week 3 Option B Rolling Dice C# Program


    Design, implement, test, and debug a C# project to show the frequencies of the sum of two dice for 100 rolls. The program will read the file you created in the dice simulation in Week Two.


    Include the following:
    Declare an array that represents the possible results of throws of two dice. (2, 3, 4, 5, 6, 7, 8, 9, 10, 11 or 12)
    For each entry in the file, increment the element of the array corresponding to that result.
    Last, display the frequency count for that simulation. Show the 11 possible values and the frequency that the sum occurs in your file.


    Zip the files of the project together and submit the zipped file.

    Learn More
  4. CIS407 Lab 5 PayrollSystem ASP.NET Application frmPersonnel

    CIS407 Lab 5 PayrollSystem ASP.NET Application

    Regular Price: $12.00

    Special Price: $10.00

    CIS407 Lab 5 PayrollSystem ASP.NET Application


    STEP 1: Modify the clsDataLayer to Use a Two-Step Process
    1. Open Microsoft Visual Studio.NET.
    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 of 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, in which 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 here
            strSQL = "Insert into tblPersonnel " +
            "(FirstName, LastName, PayRate, StartDate, EndDate) values ('" +
            FirstName + "', '" + LastName + "', " + PayRate + ", '" + StartDate +
            "', '" + EndDate + "')";
            // Add your comments here
            command.CommandType = CommandType.Text;
            command.CommandText = strSQL;
            // Add your comments here
            command.ExecuteNonQuery();
    Modify it so that it reads as follows:
    // Add your comments here
            strSQL = "Insert into tblPersonnel " +
            "(FirstName, LastName) values ('" +
            FirstName + "', '" + LastName + "')";
            // Add your comments here
            command.CommandType = CommandType.Text;
            command.CommandText = strSQL;
            // Add your comments here
            command.ExecuteNonQuery();
            // Add your comments here
            strSQL = "Update tblPersonnel " +
            "Set PayRate=" + PayRate + ", " +
            "StartDate='" + StartDate + "', " +
            "EndDate='" + EndDate + "' " +
            "Where ID=(Select Max(ID) From tblPersonnel)";
            // Add your comments here
            command.CommandType = CommandType.Text;
            command.CommandText = strSQL;
            // Add your comments here
            command.ExecuteNonQuery();
    5. 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 previously. To test it, 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 entered data values, including the PayRate, StartDate, and EndDate, were stored correctly. Close the browser window.
    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:
     
    6. Now, when you click Submit, the frmPersonnelVerified form should display a message indicating that the record was not saved:
     
    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.
    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
    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 and underlined.
    // This function saves the personnel data
        public static bool SavePersonnel(string Database, string FirstName, string LastName,
                                         string PayRate, string StartDate, string EndDate)
        {
            bool recordSaved;
    // ** NEW ** Add your comments here
             OleDbTransaction myTransaction = null;
            try
            {
                // Add your comments here
                OleDbConnection conn = new OleDbConnection("PROVIDER=Microsoft.ACE.OLEDB.12.0;" +
                                                           "Data Source=" + Database);
                conn.Open();
                OleDbCommand command = conn.CreateCommand();
                string strSQL;
                // ** NEW ** Add your comments here
     myTransaction = conn.BeginTransaction();
      command.Transaction = myTransaction;
                // Add your comments here
                strSQL = "Insert into tblPersonnel " +
                         "(FirstName, LastName) values ('" +
                         FirstName + "', '" + LastName + "')";
                // Add your comments here
                command.CommandType = CommandType.Text;
                command.CommandText = strSQL;
                // Add your comments here
                command.ExecuteNonQuery();
                // Add your comments here
                strSQL = "Update tblPersonnel " +
                         "Set PayRate=" + PayRate + ", " +
                         "StartDate='" + StartDate + "', " +
                         "EndDate='" + EndDate + "' " +
                         "Where ID=(Select Max(ID) From tblPersonnel)";
                // Add your comments here
                command.CommandType = CommandType.Text;
                command.CommandText = strSQL;
                // Add your comments here
                command.ExecuteNonQuery();
                // ** NEW ** Add your comments here
     myTransaction.Commit();
                // Add your comments here
                conn.Close();
            recordSaved = true;
            }
            catch (Exception ex)
            {
                // ** NEW ** Add your comments here
                myTransaction.Rollback();
                recordSaved = false;
            }
            return recordSaved;
        }
    8. Run your Web application. First, enter valid data in all 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 items, the successfully saved message should appear, indicating that the transaction was committed.
     
    Click the View Personnel button and verify that the new record was in fact added to the database table correctly.
     
    9. 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.
     
    Click the View Personnel button and verify that this time, as desired, an incomplete record was not added to the database table.
     
    10.  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 that you added in the frmPersonnel code and add a try/catch with logic to prevent an invalid date from causing a server error.
    11.  In the Week 3 Lab, 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.
    12.  Add validation controls to the frmPersonnel form as follows: For the first,  last name, and pay rate, make sure each field has data in it. Use the RequiredFieldValidator for this task. Add the control to the right of the text box that you are validating. The location of the validator control is where the error message (if there is one) will appear for the control to which you link the validator. You will be adding one validator control for each text box that 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.
    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$
    13.  Remove the View Personnel and Cancel buttons from the frmPersonnel form, because they will cause a Postback and invoke the client-side editing that 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.
    14.  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. Open up frmMain and add a new main form option called Edit Employees. Add the link and image for it. This option will take the user to a new form called frmEditPersonnel.
    15.  Add the new form frmEditPersonnel. On frmEditPersonnel, add the ACIT logo at the top of the form. Add a label that says Edit Employees. Add a GridView control with an ID of grdEditPersonnel.
    16.  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).
    17.  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).
    18.  There is a small > indicator in the Design View of the SQL Data Source control that 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.
    19.  Press the New Connection button and browse for the database.
    20.  Press the Next button.
    21.  When asked if you want to save the connection in the application configuration file, check the Yes check box and press Next.
    22.  Select the tblPersonnel table.
    23.  Select all columns (you can use the * for this).
    24.  Press the Advanced button and check the Generate Insert, Update, and Delete option and press the OK button.
    25.  Press the Next button.
    26.  Press the Test Query button and make sure that you see all records in the database like the image below. If it does not, repeat the above steps to make sure that you did everything properly (and selected the correct database - if you are not sure, open the database in Windows Explorer to be sure that it is the one with data in tblPersonnel). Press the Finish button.
    27.  Click on the grid that 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!
     
    STEP 3: Test and Submit
    28. Once you have verified that everything works as it is supposed to work, 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) and for any code you write, or else a 5-point deduction per item (form, class, function) will be made.

    Learn More
  5. Microsoft Visual Basic 2015 Reloaded Diane Zak Chapter 3 Pink Elephant Photo Studio

    Microsoft Visual Basic 2015 Reloaded Diane Zak Chapter 3 Pink Elephant Photo Studio Solution

    Regular Price: $20.00

    Special Price: $15.00

    Create an application that allows the owner of the Pink Elephant Photo Studio to enter the studio's quarterly sales amount. The application should display the amount of state, country, and city sales taxes the studio must pay. It should also display the total sales tax. The sales tax rates for the state, country, and city are 2.5%, 0.5%, and 0.25%, respectively. Each sales tax is calculated by multiplying the appropriate rate by quarterly sales amount. Use the following names for the solution and project, respectively: Pink Elephant Solution and Pink Elephant Project. Save the application in the VbReloaded2015\Chap03 folder. Change the form file's name to Main Form.vb. Display the sales taxes with a dollar sign and two decimal places. You can either create your own interface or create the one shown in Figure 3-64. Be sure to include comments and the Option statements. (1-8)

    Learn More
  6. Microsoft Visual Basic 2015 Chapter 9 Case 8 Moores Laws

    Microsoft Visual Basic 2015 Chapter 9 Case 8 Moores Laws

    Regular Price: $15.00

    Special Price: $12.00

    Microsoft Visual Basic 2015 Chapter 9 Case 8 Moore's Laws


    Moore's Laws
    Create a requirements document and a Use Case Definition document, and then create a Web application, based on the case project shown in Figure 9-93.


    Create a Web application that displays Moore's Law, which states that the computing power or the number of transistors within the same silicon processor doubles every months. In other words, computing speed doubles every months. As shown in the following table, allow the user to enter the current average speed in GHz and display the next 15 years of project speed. Use the validation controls to make sure the entry is filled in and that the decimal entered is between 1.0 and 10.0.

    Learn More
  7. Microsoft Visual Basic 2015 Chapter 8 Case 9 Job Growth in The Information Technology Field

    Microsoft Visual Basic 2015 Chapter 8 Case 9 Job Growth in The Information Technology Field

    Regular Price: $15.00

    Special Price: $12.00

    Microsoft Visual Basic 2015 Chapter 8 Case 9 Job Growth in The Information Technology Field


    Job Growth in The Information Technology Field
    Create a requirement document and a Use Case definition document and then design a Windows application based on the case project shown in Figure 8-120. Before writing the code, create an event planning document for each event in the program:


    The US department of Labor has projected that the Information Technology job sector is growing. Enter the information from the following table into Notepad and save the text file.


    Job Title Jobs in 2015 Jobs Projected for 2020
    Computer Developers 875000 1181000
    Computer Support 862000 1016000
    System Analyst 504000 650000
    Database Administrators 119000 154000
    Network Administrators 262000 402000
    IT Managers 205000 307000


    Calculate the changes in job numbers for each position and display the values. Compute the average number of positions that will be available in these fields each year during the period shown. Fill a ListBox object with the job titles so that the user can select a position and see the number of available jobs for the year 2015 and 2020 on the second form.

    Learn More
  8. CIS339 Week 7 Object-Oriented Application Coding

    CIS339 Week 7 Object-Oriented Application Coding

    Regular Price: $15.00

    Special Price: $12.00

    CIS339 Week 7 Object-Oriented Application Coding


    Your demonstrations of how to create both method contract and the method specification for the GetCourseByCourseID() method of the CourseList class were very well received by your team members. They then asked you for one final demonstration of how to implement the method specification using an object-oriented (OO) programming language and see the method actually execute.


    You realize that it is easy to implement the method specification in an OO programming language, but it is hard to test it because the rest of the application is not developed yet. You decided, therefore, to write two pieces of code.


    Code that implements the GetCourseByCourseID() method
    Code that implements a unit test for that method alone (outside of any other application code)
    This way you can demonstrate the method implementation and also verify its correct behavior.


    You are under a deadline constraint for this deliverable, so you asked some of your peer architects for help. They each are well versed in different OO languages like VB.NET, C#, and Java and they all have done unit testing before so they are familiar of how to construct one.


    Your peer architects provided you with partially-completed shells for your demonstration. Each shell contains:
    complete code for the Course class; partially completed code for CourseList class; and complete code for the CourseListTest class that unit tests the CourseList.GetCourseByCourseID() method.
    Your task is now easy. Just select one of these shells and complete the code for the partially completed CourseList by coding it GetCourseByCourseID() method. When you compile and run the shell, it will automatically test your GetCourseByCourseID() code to ensure its correct behavior



    Deliverables
    A copy of the code you wrote for the GetCourseByCourseID method() of the CourseList class in your favorite OO programming language
    A screen shot of the output of running the provided unit test in the shell (the CourseListTest class) showing that your code works as expected. Note that these unit tests only print out messages of testing problems. If your code is correct, the unit tests will succeed silently without any success messages.
    a zip file of the completed shell after you added your code so that the shell could be executed on a different machine.
    Verification and validation of your work
    Explanation of your work


    Download the iLabWeeklySubmissionTemplate. You are going to use this template for all of your iLab submissions throughout this course. This template is available in week1 iLab.
    Decide on your OO programming language that you will use for this lab and then download the corresponding shell from the following.
    Visual Basic Shell
    C# Shell
    Java Shell
    Both the Visual Basic and C# shells are Visual Studio projects while the Java shell include only the *.java source files that could be loaded into any Java IDE.


    Code and unit test the CourseList.GetCourseByCourseID() method in your favorite programming language. You only need to add code for the GetCourseByCourseID() method and then run the application (the unit test will automatically test your code), then print out problem messages, if any
    Using the iLabWeeklySubmissionTemplate, copy and paste the following into the template:
    code text of your CourseListGetCourseByCourseID() method
    a screenshot of running the unit test of CourseListGetCourseByCourseID() method
    a *.zip file of all the coding project files

    Learn More
  9. CIST2311 - Visual Basic Programming I Project 1 Employees Weekly Pay

    CIST2311 - Visual Basic Programming I Project 1 Employees Weekly Pay

    Regular Price: $20.00

    Special Price: $15.00

    CIST2311 - Visual Basic Programming I Project 1 Employees Weekly Pay


    Create a program that will calculate employee’s weekly pay as follows:
    Inputs:
    1) Name
    2) Hourly Rate of Pay ($ / hour)
    3) Marital Status (Married, Single)
    4) # of Dependents
    5) Healthcare (Yes or No)
    6) Hours worked


    Outputs:
    1) Gross pay (Hours over 40 are paid at time and ½)
    2) Health Insurance Amount
    3) Federal Tax, calculated as follows:
    A. From gross taxable pay subtract $70 for each dependent
    B. From value in A subtract appropriate value in Standard Deduction Column from table below to give taxable gross.
    C. Tax at rate of 10% appropriate amount in 10% Column from table below.
    D. Tax at rate of 15% appropriate amount in 15% Column from table below.
    E. Tax at rate of 25% appropriate amount in 25% Column from table below.
    F. Tax at rate of 35% remaining amount (if any) in 35% Column from table below.
    Marital Status Deductions Tax Rates
    Medical Standard 10% 15% 25% 35%
    Single $60 $75 <=$100 $101-$250 $251-$400 >$400
    Married $100 $150 <=$200 $201-$500 $501-$800 >$800
    4) Net Pay (Gross Pay – Health Care Deduction (if any) – Federal Tax).
    5) If any of the inputs are unreasonable, tell user with a message and force reentry of the data.


    Additional Requirements:
    1) Name any control that is referenced in code with a meaningful name
    2) Use functions for major tasks
    a. Calculate Gross Pay
    b. Calculate Health Deductions
    c. Calculate Tax
    3) Other than constants, do NOT use global variables (e.g. You need to pass variable between functions through the argument list and the return value).
    4) Comment each function and variable and major sections of code.
    5) Submitting a program that does not compile is an automatic 20 point deduction.


    Tax Calculation Pseudocode
    The following is one possible pseudocode for calculating the tax. There are many ways to implement this code, any that work are acceptable.


    Assume that variable GrossPay is the calculated total pay for individual. All the constants are from the table on the previous page:
    If married
    TaxablePay = GrossPay – 150 – 70.0 * NumberDependents
    if healthcare
    TaxablePay = TaxablePay – 100
    if TaxablePay > 800
    Tax = (TaxablePay - 800) * .35 + (800 - 500) * .25 + (500 - 200) * .15 +200 * .10
    else if TaxablePay > 500 Tax = (TaxablePay - 500) * .25 + (500 – 200) * .15 +200 * .10
    else if TaxablePay > 200 Tax = (TaxablePay - 200) * .15 +200 * .10
    else Tax = TaxablePay * .10
    else TaxablePay = GrossPay – 75 – 70.0 * NumberDependents
    if healthcare TaxablePay = TaxablePay – 60
    if TaxablePay > 400 Tax = (TaxablePay - 400) * .35 + (400 - 250) * .25 + (250 - 100) * .15 +100 * .10
    else if TaxablePay > 250 Tax = (TaxablePay - 250) * .25 + (250 – 100) * .15 +100 * .10
    else if TaxablePay > 100 Tax = (TaxablePay - 100) * .15 +100 * .10
    else Tax = TaxablePay * .10


    Examples:
    1. A married employee with 45 hours at $20.00/hour, 2 dependents and health care:
    A. Gross Pay: 40 * 20.00 + 5 * 20.00 * 1.5 = $950.00
    B. Minus Standard Deduction of $150.00 = 800.00
    C. Minus Medical Deduction of $100.00 = $700.00
    D. Minus 2 dependents (@$70) = $560.00
    E. Tax at 10% Bracket = 200 * .10 = $20.00
    F. Tax at 15% Bracket ($500 – $200) = 300 * .15 = $45.00
    G. Tax at 25% Bracket ($560 – $500) = $60.00 * .25 = $15.00
    H. Total Tax = $20 + $45 + $15.00 = $80.00
    I. Net Pay = 950.00 - $100.00 (Medical) - $80.00 (Tax) = $770.00
    2. A single employee with 45 hours at $20.00/hour, 1 dependent and no health care:
    A. Gross Pay: 40 * 20.00 + 5 * 20.00 * 1.5 = $950.00
    B. Minus Standard Deduction of $75.00 = 875.00
    C. Minus 1 dependent (@$70) = $805.00
    D. Tax at 10% Bracket = 100 * .10 = $10.00
    E. Tax at 15% Bracket ($250 – $100) = $150.00 * .15 = $22.5
    F. Tax at 25% Bracket ($400 – $250) = $150.00 * .25 = $37.5
    G. Tax at 35% Bracket ($805 - $400) = $405 * .35 = $141.75
    H. Total Tax = $10 + $22.50 + $37.50 + 141.75 = $211.75
    I. Net Pay = 950.00 - $0.00 (Medical) - $211.75 (Tax) = $738.25

    Learn More
  10. POS 409 Week 5 Regular Expression

    POS 409 Week 5 Regular Expression

    Regular Price: $15.00

    Special Price: $12.00

    POS 409 Week 5 Regular Expression


    Design, implement, test, and debug a C# Windows Form Application to demonstrate input validation using regular expression. The program should validate at least one type of data - you are free to choose a commonly used data format such as Social Security Number (999-9999-99), or phone number (999-999-9999), or a custom format that you designed.

    Learn More

Items 41 to 50 of 170 total

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

Grid  List 

Set Ascending Direction