EXERCISE TOPIC▼
- Access exercises (91)
- C# exercises (79)
- Excel exercises (278)
- Power Apps exercises (13)
- Power Automate exercises (18)
- Power BI exercises (139)
- Power Platform exercises (157)
- Python exercises (28)
- Report Builder exercises (141)
- SQL exercises (198)
- SSAS exercises (51)
- SSIS exercises (46)
- SSRS exercises (99)
- VBA exercises (85)
- Visual Basic exercises (46)
C# EXERCISES▼
VISUAL C# EXERCISES▼
- Creating forms (4)
- Coding form events (1)
- Laying out your code (2)
- C# variables (4)
- Enumerations and constants (2)
- Conditions (2)
- Modular code (3)
- Arrays (2)
- Looping (2)
- Files and folders (3)
- Properties in C# (3)
- Using lists (3)
- Validating forms (6)
- Toolbars, menus and status bars (1)
- FileDialogs and StreamReaders (1)
- Debugging and trapping errors (1)
- Introduction to DataGridViews (1)
- DataGridView events (3)
- Complex DataGridViews (2)
- Creating classes (4)
- The form as a class (1)
- Data structures (6)
- Inheritance (5)
- Interfaces (2)
- Delegates and events (2)
- Writing LINQ (2)
- Advanced LINQ (2)
- Entity Frameworks (1)
- LINQ with Entity Frameworks (4)
- Grouping using LINQ (2)
- LINQ to SQL (2)
Visual C# | C# variables exercise | Practice in converting C# variable types
This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.
| Software ==> | Visual C# (79 exercises) |
| Version ==> | Any version of C# |
| Topic ==> | C# variables (4 exercises) |
| Level ==> | Average difficulty |
| Subject ==> | C# training |
You need a minimum screen resolution of about 700 pixels width to see our exercises. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.
The idea behind this exercise is to create a dating agency application form (we'll call it frmMoneySpent). The agency only collects two bits of information per applicant: the person's name, and the amount of money they require to be spent on them on their date:
£2,000 a date puts Bob in the high-class escort category
The dating agency imposes a ceiling of £100 per date. Attach code to the OK button to display a suitable error message if an applicant gets too greedy:
Check that the amount entered is a number, then compare this with the £100 limit
On the other hand, your event-handling code should display a nice reassuring message if the amount entered is within limits:
The message should include the person's name
Try out the various scenarios (invalid amount, too much, etc.) to check everything works, then close down your form.