Tektronix TPI.NET and PlugIn Documentation free download

File name TPI.NET_and_PlugIn_Documentation.zip

TLA Plug-In Design Guide October 9, 2009 1 Introduction ... 2 2 Implementing Plug-Ins ... 4 2.1 Software Implementation ... 4 2.2 Plug-In User Interfaces ... 6 2.3 Generic, or "Tool," Plug-Ins... 8 2.4 Data Window Plug-Ins... 8 2.5 Data Source Plug-Ins ... 10 October 9, 2009 Page 1 of 12 TLA Plug-In Design Guide 1 Introduction Plug-Ins Defined Plug-ins are managed .NET classes that implement the IPlugIn interface or an interface derived from it. The IPlugIn interface is defined by the TLA application software. Since plug-ins must implement specific interfaces defined by the application, they have a subset of known properties, methods, and events. The application uses these known members to initialize and interact with plug-in instances. In turn, plug-in instances extend the functionality of the TLA application. As managed types, plug-ins implementations are contained within assembly DLLs. A plug-in class becomes "plugged-in" when the assembly containing it is placed into the TLA700\System\PlugIns directory of the application installation. Development Overview Plug-ins are developed by creating managed classes that implement specific .NET interfaces. Before a plug-in can be fully implemented, the following items are needed by the developer: A .NET enabled compiler, Visual Studio .NET for example. A copy of TlaNetInterfaces.dll. All plug-in developers must use .NET-enabled compilers, which can create assemblies with code that executes under the Common Language Runtime. The NET interface specifications for the TLA application have been written with the expectation that plug-ins will be developed most often with Microsoft's Visual Basic, C#, or Managed C++. In order to create a plug-in class, the developer must have a copy of TlaNetInterfaces.dll, which is a DLL present in every V5.0 TLA software installation. It is an assembly that contains metadata for all plug-in interfaces and TPI.NET types. The file holds the compiled definitions of all .NET types that are currently described in "DotNet Interfaces UIS.doc." Both the TLA ap