The Console Application Project - Coursework Example

I ignored the error and tried running the new program and still there was a notification from the dialogue box that there were build errors. I only realized that I was running a different version from what I wanted after a series of procedures. In fixing this error, I realized that I had misspelled the data type so I had to generate a new class by going to generate a new type, and from a list of classes, delegates, interfaces, enumerators, and structures, I chose a class and through the dialogue box, I defined the new class in a new file (Utley, 2009).

Runtime errors are characterized by causing application crashes. During my project, this had the unassigned data type (ten to one hundred). When I added a value that exceeded the available range of data types, I got information that the application has stopped working (crashed).To fix that, I moved to System Overflow Exceptions which then directed me to Visual Studio and showed me the code line which triggered the exception, and through the Call Stack panel, I was able to fix the error (Utley, 2002).

However much it was quite demoralizing at this stage of the project, I was able to fix the problem accurately. Logic errors finally, another error challenge I met in my project was the Logic error. This type of error hinders the normal operation of a program by either producing the unintended output or the undesired result. In my project, I realized that I had incorrect type casting, miscoded fragments, and variable scoping, and to fix these errors, I used the w-Command –Line option which produced a message about the questionable codes and took the necessary procedure to fix the errors (Utley, 2002).

To be satisfied that all the logic errors were fixed, I again carried out the built-in debugger to help me examine all the variable values as needed.