Basic Instructions:
===================

The .NET plug-in bridge allows you to invoke plug-in assemblies written in .NET from a running InstallAware setup or the InstallAware IDE. Since managed code cannot be invoked directly from native code, a pair of native code bridge DLLs are provided which may be configured to load any managed .NET plug-in assemblies. There is no need to register the plug-in assemblies using either gacutil or regasm. The bridge DLLs work without any pre-registration as described below.

The file RunTime_NetBridge.dll is the bridge DLL for the runtime plug-in assembly. You must rename it using a unique library name. The RunTime_NetBridge.ini file must also be renamed to match the new name of the runtime plug-in assembly.

Similary, the file DesignTime_NetBridge.dll is the bridge DLL for the design time plug-in assembly. It too must be renamed to avoid conflicts with third party plug-in libraries. The corresponding DesignTime_NetBridge.ini file must also be renamed, matching the new name of the design time plug-in assembly.

Both of the INI files must be configured correctly to indicate the name of the actual plug-in assemblies to load, as well as the internal name spaces to use. This is how the bridge determines what exactly to load.

The plug-in assemblies must be placed inside the same folder as the bridge DLLs, together with their INI files.

Important:
==========

When creating Windows registry keys for the managed plug-in, make sure to specify the bridge DLLs and not the plug-in assemblies.

The build routine inside the plug-in assemblies must copy the plug-in assembly files (both design time and runtime), as well as the bridge DLLs and INI files.

The correct version of .NET MUST be pre-installed on the target system BEFORE any .NET based plug-in assemblies are invoked by setup at runtime.