|
Microsoft Visual C#: |
|
|
Exception Handling in File Processing |
|
Finally |
|
In previous lessons, to handle exceptions, we were using the try, catch, and throw keywords. These allowed us to perform normal assignments in a try section and then handle an exception, if any, in a catch block. We also mentioned that, when you create a stream, the operating system must allocate resources and dedicate them to the file processing operations. Additional resources may be provided for the object that is in charge of writing to, or reading from, the stream. We also saw that, when the streaming was over, we should free the resources and give them back to the operating system. To do this, we called the Close() method of the variable that was using resources. |
|
More than any other assignment, file processing is in prime need of exception handling. During file processing, there are many things that can go wrong. For this reason, the creation and/or management of streams should be performed in a try block to get ready to handle exceptions that would occur. Besides actually handling exceptions, the C# language provides a special keyword used free resources. This keyword is finally. The finally keyword is used to create a section of an exception. Like catch, a finally block cannot exist by itself. It can be created following a try section. The formula used would be: try
{
}
finally
{
}
Based on this, the finally section has a body of its own, delimited by its curly brackets. Like catch, the finally section is created after the try section. Unlike catch, finally never has parentheses and never takes arguments. Unlike catch, the finally section is always executed. Because the finally clause always gets executed, you can include any type of code in it but it is usually appropriate to free the resources that were allocated previously. In the same way, you can use a finally section to free resources used when reading from a stream. Here are examples: using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.IO;
namespace FileProcessing1
{
public partial class Exercise : Form
{
public Exercise()
{
InitializeComponent();
}
private void btnSave_Click(object sender, EventArgs e)
{
string Filename = "Employees.spr";
FileStream fstPersons = new FileStream(Filename,
FileMode.Create);
BinaryWriter wrtPersons = new BinaryWriter(fstPersons);
try
{
wrtPersons.Write(txtPerson1.Text);
wrtPersons.Write(txtPerson2.Text);
wrtPersons.Write(txtPerson3.Text);
wrtPersons.Write(txtPerson4.Text);
txtPerson1.Text = "";
txtPerson2.Text = "";
txtPerson3.Text = "";
txtPerson4.Text = "";
}
finally
{
wrtPersons.Close();
fstPersons.Close();
}
}
private void btnOpen_Click(object sender, EventArgs e)
{
string Filename = "Employees.spr";
FileStream fstPersons = new FileStream(Filename, FileMode.Open);
BinaryReader rdrPersons = new BinaryReader(fstPersons);
try
{
txtPerson1.Text = rdrPersons.ReadString();
txtPerson2.Text = rdrPersons.ReadString();
txtPerson3.Text = rdrPersons.ReadString();
txtPerson4.Text = rdrPersons.ReadString();
}
finally
{
rdrPersons.Close();
fstPersons.Close();
}
}
}
}
Of course, since the whole block of code starts with a try section, it is used for exception handling. This means that you can add the necessary and appropriate catch section(s) (but you don't have to).
In the previous lesson as our introduction to file processing, we behaved as if everything was alright. Unfortunately, file processing can be very strict in its assignments. Based on this, the .NET Framework provides various Exception-oriented classes to deal with almost any type of exception you can think of. One of the most important aspects of file processing is the name of the file that will be dealt with. In some cases you can provide this name to the application or document. In some other cases, you would let the user specify the name of the path. Regardless of how the name of the file would be provided to the operating system, when this name is acted upon, the compiler is asked to work on the file. If the file doesn't exist, the operation cannot be carried. Furthermore, the compiler would throw an error. Here is an example: private void btnOpen_Click(object sender, EventArgs e)
{
string Filename = "contractors.spr";
FileStream fstPersons = null;
BinaryReader rdrPersons = null;
fstPersons = new FileStream(Filename, FileMode.Open);
rdrPersons = new BinaryReader(fstPersons);
try
{
txtPerson1.Text = rdrPersons.ReadString();
txtPerson2.Text = rdrPersons.ReadString();
txtPerson3.Text = rdrPersons.ReadString();
txtPerson4.Text = rdrPersons.ReadString();
}
finally
{
rdrPersons.Close();
fstPersons.Close();
}
}
Here is an example of an error that this would produce:
There are many other exceptions that can thrown as a result of something going bad during file processing: FileNotFoundException: This exception is thrown when a file has not been found. Here is an example of handling it: private void btnOpen_Click(object sender, EventArgs e)
{
string Filename = "contractors.spr";
try
{
FileStream fstPersons = new FileStream(Filename, FileMode.Open);
BinaryReader rdrPersons = new BinaryReader(fstPersons);
try
{
txtPerson1.Text = rdrPersons.ReadString();
txtPerson2.Text = rdrPersons.ReadString();
txtPerson3.Text = rdrPersons.ReadString();
txtPerson4.Text = rdrPersons.ReadString();
}
finally
{
rdrPersons.Close();
fstPersons.Close();
}
}
catch(FileNotFoundException ex)
{
Console.Write("Error: " + ex.Message);
MessageBox.Show(" May be the file doesn't exist or you typed it wrong!");
}
}
Here is an example of what this would produce:
IOException: As mentioned already, during file processing, anything could go wrong. If you don't know what caused an error, you can throw the IOException exception.
In its high level of support for file processing, the .NET Framework provides the FileInfo class. This class is equipped to handle all types of file-related operations including creating, copying, moving, renaming, or deleting a file. FileInfo is based on the FileSystemInfo class that provides information on characteristics of a file.
The FileInfo class is equipped with one constructor whose syntax is: public FileInfo(String fileName); This constructor takes as argument the name of a file or its complete path. If you provide only the name of the file, the compiler would consider the same directory of its project. Here is an example: public partial class Exercise : Form
{
private void btnSave_Click(object sender, EventArgs e)
{
FileInfo flePeople = new FileInfo("People.txt");
}
}
Alternatively, if you want, you can provide any valid directory you have access to. In this case, you should provide the complete path.
The FileInfo constructor is mostly meant only to indicate that you want to use a file, whether it exists already or it would be created. Based on this, if you execute an application that has only a FileInfo object created using the constructor as done above, nothing would happen. To create a file, you have various alternatives. If you want to create one without writing anything in it, which implies creating an empty file, you can call the FileInfo.Create() method. Its syntax is: public FileStream Create(); This method simply creates an empty file. Here is an example of calling it: private void btnSave_Click(object sender, EventArgs e)
{
FileInfo flePeople = new FileInfo("People.txt");
flePeople.Create();
}
The FileInfo.Create() method returns a FileStream object. You can use this returned value to write any type of value into the file, including text. If you want to create a file that contains text, an alternative is to call the FileInfo.CreateText() method. Its syntax is: public StreamWriter CreateText(); This method returns a StreamWriter object. You can use this returned object to write text to the file. When you call the FileInfo.Create() or the FileInfo.CreateText() method, if the file passed as argument, or as the file in the path of the argument, exists already, it would be deleted and a new one would be created with the same name. This can cause the right file to be deleted. Therefore, before creating a file, you may need to check whether it exists already. To do this, you can check the value of the Boolean FileInfo.Exists property. This property holds a true value if the file exists already and it holds a false value if the file doesn't exist or it doesn't exist in the path.
As mentioned earlier, the FileInfo.Create() method returns a FileStream object. You can use this to specify the type of operation that would be allowed on the file. To write normal text to a file, you can first call the FileInfo.CreateText() method. This method returns a StreamWriter object. The StreamWriter class is based on the TextWriter class that is equipped with the Write() and the WriteLine() methods used to write values to a file. The Write() method writes text on a line and keeps the caret on the same line. The WriteLine() method writes a line of text and moves the caret to the next line. After writing to a file, you should close the StreamWriter object to free the resources it was using during its operation(s). Here is an example:
private void btnSave_Click(object sender, EventArgs e)
{
FileInfo flePeople = new FileInfo("People.txt");
StreamWriter stwPeople = flePeople.CreateText();
try
{
stwPeople.WriteLine(txtPerson1.Text);
stwPeople.WriteLine(txtPerson2.Text);
stwPeople.WriteLine(txtPerson3.Text);
stwPeople.WriteLine(txtPerson4.Text);
}
finally
{
stwPeople.Close();
txtPerson1.Text = "";
txtPerson2.Text = "";
txtPerson3.Text = "";
txtPerson4.Text = "";
}
}
You may have created a text-based file and written to it. If you open such a file and find out that a piece of information is missing, you can add that information to the end of the file. To do this, you can call the FileInfo.AppenText() method. Its syntax is: public StreamWriter AppendText(); When calling this method, you can retrieve the StreamWriter object that it returns, then use that object to add new information to the file.
As opposed to writing to a file, you can read from it. To support this, the FileInfo class is equipped with a method named OpenText(). Its syntax is: public StreamREader OpenText(); This method returns a StreamReader object. You can then use this object to read the lines of a text file. Here is an example: using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
namespace FileProcessing2
{
public partial class Exercise : Form
{
public Exercise()
{
InitializeComponent();
}
private void btnSave_Click(object sender, EventArgs e)
{
FileInfo flePeople = new FileInfo("People.txt");
StreamWriter stwPeople = flePeople.CreateText();
try
{
stwPeople.WriteLine(txtPerson1.Text);
stwPeople.WriteLine(txtPerson2.Text);
stwPeople.WriteLine(txtPerson3.Text);
stwPeople.WriteLine(txtPerson4.Text);
}
finally
{
stwPeople.Close();
txtPerson1.Text = "";
txtPerson2.Text = "";
txtPerson3.Text = "";
txtPerson4.Text = "";
}
}
private void btnOpen_Click(object sender, EventArgs e)
{
string Filename = "People.txt";
FileInfo flePeople = new FileInfo(Filename);
StreamReader strPeople = flePeople.OpenText();
if (flePeople.Exists == true)
{
try
{
txtPerson1.Text = strPeople.ReadLine();
txtPerson2.Text = strPeople.ReadLine();
txtPerson3.Text = strPeople.ReadLine();
txtPerson4.Text = strPeople.ReadLine();
}
finally
{
strPeople.Close();
}
}
else
MessageBox.Show("There is no file named People.txt " +
"in the indicated location");
}
}
}
|
|
|
||
| Previous | Copyright © 2008-2009, yevol.com | Next |
|
|
||