The .NET assemblies are available for .NET 10, .NET 11 and .NET Framework 4.8.
First a reference to the List & Label assembly has to be added to the project. If possible, references to the .NET assemblies should be added via the NuGet package manager. This ensures that all required dependencies are added as well. You can find our NuGet packages at https://www.nuget.org/profiles/combit.
Note: Please note that the List & Label NuGet packages and their dependencies use Semantic Versioning 2.0.0, and therefore the following prerequisites apply:
- NuGet 4.3.0+
- Visual Studio 2017 version 15.3+
- Visual Studio 2015 with NuGet VSIX v3.6.0
- dotnet: dotnetcore.exe (.NET SDK 2.0.0+)
The assemblies themselves are located in the respective "Assemblies" subdirectory under "Development\Microsoft .NET\" of the installation.
In the second step an instance of the component can be created. This can be done either by the development environment directly by dragging the ListLabel component onto a form. Alternatively, the component can also be created dynamically:
combit.Reporting.ListLabel LL = new combit.Reporting.ListLabel();
Generally the namespaces combit.Reporting and combit.Reporting.DataProviders are prereferenced by "using" for the whole file. This saves a lot of typing later.
using combit.Reporting;
using combit.Reporting.DataProviders;
When using dynamic creation, the component should be released by the Dispose method after its use, so that the unmanaged resources can be released as soon as possible.
LL.Dispose();
Due to performance reasons, it is recommended that you always keep an instance of the ListLabel object in memory globally for the dynamic creation as well. It can be created in the Load event of the application's main window and released again in the FormClosed event for example. The essential advantage is that the List & Label modules won't be loaded and released for every new instance, which can lead to undesirable delays of frequent calls or e.g. multiple prints.
