What many don’t know: List & Label Enterprise customers have exclusive access to the daily updated source files of the .NET component. This opens up numerous possibilities, such as simply looking up or checking how combit has implemented one of the numerous .NET data providers to get inspiration for your own data provider using the IDataProvider Interface. Or the simple debugging of a certain code to derive an observed behavior and to give the combit team valuable input for future adjustments.
How can the source files be used?
First of all, the current source files must be obtained from the download area of the combit user account, as they are not directly included in the installation scope. These are available daily under “Current Source Files of the .NET Component”.
It is necessary that a Visual Studio version matching the List & Label version is used for the later build to be successful:
List & Label 25: Visual Studio 2019
List & Label 24: Visual Studio 2017
Depending on the .NET technology used, there are different projects in the List & Label .NET source files. For example, add the project
combit.ListLabel.NetFx40to the solution if you have a .NET Framework 4 application. Or the project
combit.ListLabel.Coreif you have a .NET Core application.
Once the appropriate project is found and added to your Visual Studio solution as an existing project, the existing List & Label reference in your application must be removed and the added project selected as the new reference.
During the first build there is a message that the file “listlabel.snk” could not be found, which is used for signing the components but is not included in the source files. Therefore the ‘Sign the assembly’ option in the project settings must be disabled.
With the integration of the source files of the List & Label .NET component into your own project, they can now be used as a debug target for possible analysis etc.