Export (0) Print
Expand All

IComSoapPublisher.GetAssemblyNameForCache Method

Returns the full path for a strong-named signed generated assembly in the SoapCache directory.

Namespace:  System.EnterpriseServices.Internal
Assembly:  System.EnterpriseServices (in System.EnterpriseServices.dll)

void GetAssemblyNameForCache(
	string TypeLibPath,
	out string CachePath
)

Parameters

TypeLibPath
Type: System.String

The path for the file that contains the typelib.

CachePath
Type: System.String

When this method returns, this parameter contains the full path of the proxy assembly in the SoapCache directory.

ExceptionCondition
ArgumentNullException

TypeLibPath is null.

SecurityException

The caller does not have the required permission.

ArgumentException

The file name is empty, contains only white spaces, or contains invalid characters.

UnauthorizedAccessException

Access to TypeLibPath is denied.

PathTooLongException

The specified path, file name, or both exceed the system-defined maximum length. For example, on Windows-based platforms, paths must be less than 248 characters, and file names must be less than 260 characters.

NotSupportedException

TypeLibPath contains a colon (:) in the middle of the string.

For an unmanaged COM+ component to be published through .NET remoting as a SOAP endpoint, a proxy needs to be generated to make the unmanaged components available to the .NET Framework. This is done by programmatically performing the same steps as Type Library Importer (Tlbimp.exe), the Windows Software Development Kit (SDK) tool that is used to convert unmanaged COM+ type libraries to proxy metadata assemblies. For client activation over SOAP to succeed, however, client and server machines must share the same strong-named signed metadata proxies. For this reason, when a managed proxy assembly is generated for an unmanaged COM+ component, a strong name key is also generated and used to sign the proxy assembly.

.NET Framework

Supported in: 4.5, 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Show:
© 2014 Microsoft