Creating Custom Dlls

PowerTCP components can be used within a standard desktop application (EXE), a Web Service, a Windows Service, an ASP.NET application, and your own custom dynamic-link library (DLL). It is not necessary to provide licensing information for the custom dll, however it is necessary for any application which uses the custom dll. For example, if you have a dll ("Helper.dll") that uses a PowerTCP component it is not necessary to provide licensing info for the dll. However, if you have an an application ("App1.exe") that references "Helper.dll", the application will have to have a "licenses.licx" file containing the component information for the PowerTCP component (see Creating the Licenses.licx File for more information about creating "licenses.licx" files). In addition, "App1.exe" must be compiled on a machine that has a properly registered PowerTCP component.

In This Section

Creating a Project: This topic demonstrates how to create a new Windows project in Visual Studio .NET.
Placing Components on a Form: This topic demonstrates how to create and use a control using Visual Studio .NET.
Creating Components Dynamically: This topic demonstrates how to add a component as a reference using Visual Studio .NET.
Creating Custom Dlls: Discusses the steps required when creating a dll that uses a PowerTCP control.
Using Components Outside of Visual Studio: This topic discusses the use of the components without Visual Studio.
Using Events within the Visual Studio .NET Environment: Describes how to use PowerTCP events within the Visual Studio .NET environment.
Using Events when a Component is Created Dynamically: Describes the extra steps required to use events when using a PowerTCP component as a reference.

Send comments on this topic.

Documentation version 1.1.2.0.