Publish.GetAssemblyNameForCache(String, String) Method

Reference

Definition

Namespace:: System.EnterpriseServices.Internal

Assembly:: System.EnterpriseServices.dll

Important

Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

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

public:
 virtual void GetAssemblyNameForCache(System::String ^ TypeLibPath, [Runtime::InteropServices::Out] System::String ^ % CachePath);

public void GetAssemblyNameForCache (string TypeLibPath, out string CachePath);

abstract member GetAssemblyNameForCache : string * string -> unit
override this.GetAssemblyNameForCache : string * string -> unit

Public Sub GetAssemblyNameForCache (TypeLibPath As String, ByRef CachePath As String)

Parameters

TypeLibPath: String

The path for the file that contains the typelib.

CachePath: String

When this method returns, this parameter contains the name of the SoapCache directory.

Implements

GetAssemblyNameForCache(String, String)

Exceptions

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.

NotSupportedException

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

Remarks

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 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.

Applies to