How Do I...? Common Tasks QuickStart Tutorial
How Do I...Change the search path for private assemblies?
Private assemblies are assemblies that are visible to only one application. The .NET Framework enables
developers to build applications that are isolated from changes made to the system by other applications.
Private assemblies must be deployed in the directory structure of the containing application and are found
during runtime through a process called probing, which is simply a mapping from an assembly's identity to
a file on disk that contains the manifest.
By default, probing for private assemblies is done in the application base (the root directory of the
application) and the subdirectories that follow naming conventions based on assembly name and culture. You can customize this behavior by specifying a privatePath in your application's configuration file.
The privatePath is a semi-colon delimited list of directories in which the common language runtime will search for private assemblies.
These directory names are relative to the application base - they cannot point outside the
application base. The directories on privatePath will be searched after the application base itself.
The following configuration file adds a bin directory to the assembly search path:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="bin"/>
</assemblyBinding>
</runtime>
</configuration>
Example
VB Config Example
[This sample can be found at H:\Home\WU_000036_efe47225c86ca62f325a01d8519bc002\Webs\aspnet.sk\quickstarts\QuickStartv20\howto\samples\assemblies\searchpath\
To build this sample, open the SDK command prompt and navigate to the above path. Build the sample using the build tool msbuild
passing the solution file as the first parameter: msbuild mySample.sln. The compiled executable will be found in the sub directory \bin
directory.]
Microsoft .NET Framework SDK QuickStart Tutorials Version 2.0
Copyright � 2005 Microsoft Corporation. All rights reserved.
|