Create an Application Manifest to Reference a Private Copy of UccAPI.Dll
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
A .NET application accesses the UccApi.dll library through the wrapper classes defined in the primary interoperable assembly (Microsoft.Office.Interop.UccApi.dll), the reference to which must be added to the .NET application project. The UccApi.dll library in turn depends on the Microsoft Visual C++ development system library.
To reference a private copy of the UccApi.dll assembly (that is, a copy not installed in the system’s Global Assembly Cache), the client application must include an application manifest as part of its resources to explicitly specify these dependent assemblies. The following .NET Framework code example shows a Unified Communications Client API client application manifest for a Unified Communications Client API client.
For information about adding your new application manifest a project, see Create a Visual Studio Project for a Unified Communications Client API Client.
The following example is a sample application manifest. The example assumes that .NET Framework 2.0 or 3.0 is used for the application development where the dependent Visual C++ library is built in the Microsoft.VC80.CRT assembly. If .NET Framework 3.5 is used, the name of the dependent assembly of the Visual C++ library should be replaced with Microsoft.VC90.CRT. The version number of this dependent assembly should be changed to "9.x.yyyyyy.z" depending on the version of the Visual C++ run-time library installed in the local development environment.
In this example, the Unified Communications Client API client application executable file name is UccApi_client.exe. The corresponding application manifest file name must be UccApi_client.exe.manifest and be included as the application’s resource. By default, application resources are placed in the same directory where the application executable is placed.
For more information, see Application Manifests.
Example
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
<assemblyIdentity
version="1.1.0.0"
processorArchitecture="x86"
name="UccApi_client.exe"
type="win32"
/>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.VC80.CRT"
version="8.0.50608.0"
processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"
/>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity
version="2.0.0.0"
processorArchitecture="x86"
name="UCCAPI"
type="win32"
/>
</dependentAssembly>
</dependency>
</assembly>