HAKOM PowerTSM® Documentation
3.11.3.2 3.11.3.1 3.11.3.0 3.11.2.3 3.11.2.2 3.11.2.1 3.11.2 3.11.1 3.11.0.1 3.11.0 3.10.6.6 3.10.6.5 3.10.6.4 3.10.6.3 3.10.6.2 3.10.6.1 3.10.5.5 3.10.5.4 3.10.5.1 3.10.4.7 3.10.3 3.10.2.2 3.10.1.1 3.10.0 3.9.2.12 English Deutsch
3.11.3.2 3.11.3.1 3.11.3.0 3.11.2.3 3.11.2.2 3.11.2.1 3.11.2 3.11.1 3.11.0.1 3.11.0 3.10.6.6 3.10.6.5 3.10.6.4 3.10.6.3 3.10.6.2 3.10.6.1 3.10.5.5 3.10.5.4 3.10.5.1 3.10.4.7 3.10.3 3.10.2.2 3.10.1.1 3.10.0 3.9.2.12 English Deutsch

TSM .NET API


Using the TSM .NET API effectively requires that you have access to an already prepared database. A guide for setting up the database can be found here: Installing a TSM Database

Using the Framework with Visual Studio

Create new Package Source

If not already available, create a new package source under Tools - Options - Nuget Package Manager.

image2018-7-13_11-25-20.png


Afterwards copy the provided file "HAKOM.Framework.Core.{version}.nupkg" in the given folder.

Integrate HAKOM Framework in a Project

image2018-7-13_11-32-24.png
image2018-7-13_11-33-21.png


The Nuget package has to be added as a package reference, otherwise the compiling of formula time series will result in assembly binding problems.

The default package format can be configured here in Visual Studio:

image2019-5-14_15-8-6.png

Here you can find instructions on how to migrate from packages.config to PackageReference: Migrate from packages.config to PackageReference

Adding HAKOM.Config and HAKOM.License

A textfile called "HAKOM.Config" as well as a valid "HAKOM.License" file has to be added to the project and copied into the output folder during compilation.

image2018-7-13_11-38-22.png
image2018-7-13_11-41-21.png

Adding EvalComponents (optional)

The default EvalComponents are copied automatically since version 3.7.6. Other optional or custom-made functions need to be added as follows:

image2018-7-13_11-38-22.png

For each file the option "Copy to Output Directory" "Copy if newer" has to be configured.

image2018-11-13_8-53-20.png