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

■

I N T R O D U C I N G   . N E T  A S S E M B L I E S

510

8849CH15.qxd  10/22/07  1:46 PM  Page 510

---

Once you have compiled your client application, navigate to the directory that contains

SharedCarLibClient.exe using Windows Explorer and notice that Visual Studio 2008 has not copied

CarLibrary.dll to the client’s application directory. When you reference an assembly whose

manifest contains a .publickey value, Visual Studio 2008 assumes the strongly named assembly will

most likely be deployed to the GAC, and therefore does not bother to copy the binary.

As a quick side note, if you wish to have Visual Studio 2008 copy a shared assembly to the client

directory, you can select an assembly from the References node of Solution Explorer and set the

Copy Local property to True using the Properties window (see Figure 15-23). Once you do, the *.dll

will be copied to the client folder upon the next compilation.

Figure 15-23.

The Copy Local property can force a copy of a strongly named code library.