SIT232 - Object Oriented Development - IT Assignment Help

Assignment Task

General Instructions
This practical task introduces you to error handling and covers a number of most common .NET Framework exception types that you will likely encounter as soon as you start developing larger applications. Exceptions that you will meet in practice can be thrown either by the runtime or the application’s code. The latter case represents a class of exceptions that are defined by the application’s developer. Some exceptions can be caused by a faulty program code, while other exceptions can result from an incorrect input that has not been accounted for in the application's code. When any of these errors occur, the system catches the error and
raises an exception.
The process of generating and signalling an error is referred to as throwing an exception. This is done using the ‘throw’ keyword followed by a new instance of a class derived (inherited) from System.Exception. There are standard exception types provided by the .NET framework that you can use ratherthan creating a custom exception.
Remember that execution failure occurs whenever a program (or its part) cannot do what it was designed to do. For example, if the OpenFile method cannot return a file handler to the caller, it would be considered an execution failure. Exceptions are the primary means of reporting errors in applications. Therefore, you must adhere to a number of rules when you throw or handle exceptions. Here are several basic rules that you should follow and always think about them when you work on your application.

• Report execution failures by throwing exceptions.
• Do not use exceptions for the normal flow of control, if possible.
• Consider terminating the program by calling System.Environment.FailFast method instead of throwing an exception if your code encounters a situation where it is unsafe for further execution.
• Consider the performance implications of throwing exceptions. Throw rates above 100 per second are likely to noticeably impact the performance of most applications.
• Do not have public members that can either throw or not based on some option.
• Do not have public members that return exceptions as the return value.
• Do not throw exceptions from exception filter blocks (i.e. the ‘catch’ block of the ‘try?catch’ statement).
• Avoid explicitly throwing exceptions from ‘finally’ blocks.

This list is by no means exhaustive and there are more rules and strategies. Remember that exception handling is an art which once you master grants you immense powers.
1. In this task, you will need to conduct a small research about every exception presented in the following list:
a) NullReferenceException
b) IndexOutOfRangeException
c) StackOverflowException
d) OutOfMemoryException
e) InvalidCastException

f) DivideByZeroException
g) ArgumentException
h) ArgumentOutOfRangeException
i) SystemException

This SIT232 - IT Assignment has been solved by our IT experts at My Uni Paper. Our Assignment Writing Experts are efficient to provide a fresh solution to this question. We are serving more than 10000+ Students in Australia, UK & US by helping them to score HD in their academics. Our Experts are well trained to follow all marking rubrics & referencing style.
Be it a used or new solution, the quality of the work submitted by our assignment experts remains unhampered. You may continue to expect the same or even better quality with the used and new assignment solution files respectively. There’s one thing to be noticed that you could choose one between the two and acquire an HD either way. You could choose a new assignment solution file to get yourself an exclusive, plagiarism (with free Turnitin file), expert quality assignment or order an old solution file that was considered worthy of the highest distinction.