This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

Note

Understand that the CLR will load the very first assembly it finds during the probing process. For example,

if the C:\MyApp folder did contain a copy of 

CarLibrary.dll

, it will be loaded into memory, while the copy under

MyLibraries is effectively ignored.

Configuration Files and Visual Studio 2008

While you are always able to create XML configuration files by hand using your text editor of choice,

Visual Studio 2008 allows you create a configuration file during the development of the client pro-

gram. To illustrate, load the CSharpCarClient solution into Visual Studio 2008 and insert a new

Application Configuration File item using the Project ➤ Add New Item menu selection. Before you

click the OK button, take note that the file is named App.config (don’t rename it!). If you look in the

Solution Explorer window, you will now find App.config has been inserted into your current project

(see Figure 15-13).

Figure 15-13.

The Visual Studio 2008 App.config file

At this point, you are free to enter the necessary XML elements for the client you happen to be

creating. Now, here is the cool thing. Each time you compile your project, Visual Studio 2008 will

automatically copy the data in App.config to the \bin\Debug directory using the proper naming

convention (such as CSharpCarClient.exe.config). However, this behavior will happen only if your

configuration file is indeed named App.config.

Using this approach, all you need to do is maintain App.config, and Visual Studio 2008 will

ensure your application directory contains the latest and greatest configuration data (even if you

happen to rename your project).