Importing .NET assemblies – PB Docs 2017

You can import .NET assemblies into .NET targets from the .NET
Assemblies page in the Properties dialog box for the target.
(Right-click on the target and select .NET Assemblies from the pop-up
menu.)

Click the Browse button to open the Browse for a .NET Assembly
dialog box, from which you can browse to import private assemblies
with the .dll, .tlb, .olb, .ocx, or .exe extension. To import an
assembly, select it and click Open. To import multiple assemblies, you
must select and import them one at a time.

Click the Add button to open the Import .NET Assembly dialog
box, from which you can import a shared assembly into your target.
Assemblies must have a strong name. A strong name includes the
assembly’s identity as well as a public key and a digital signature.
For more information about assemblies and strong names, see the
Microsoft library at https://msdn.microsoft.com/en-us/library/wd40t7ad(v=vs.100).aspx.

To import an assembly, select it and click OK. To import
multiple assemblies, you must select and import them one at a
time.

You can also use the Import .NET Assembly dialog box to import
recently used assemblies.

System Tree display

The System Tree shows the classes, methods, structures, and
enumerations for C# assemblies that you import into your .NET targets.
However, a language-related limitation affecting managed C++
assemblies prevents the System Tree from displaying members of
classes, structures, and enumeration types. It also causes managed C++
classes to display as structures.

By default, the full name of each class in an assembly is
displayed in the System Tree. If you prefer to show only the final
name, add the following line to the [PB] section of your pb.ini
file:

For example, with this setting the
Microsoft.SQLServer.Server.DataAccessKind class in System.Data.dll
displays as DataAccessKind. You can right-click the class and select
Properties from the pop-up menu to display the full class name.