Aml.Engine
1.0.3
See the version list below for details.
dotnet add package Aml.Engine --version 1.0.3
NuGet\Install-Package Aml.Engine -Version 1.0.3
<PackageReference Include="Aml.Engine" Version="1.0.3" />
paket add Aml.Engine --version 1.0.3
#r "nuget: Aml.Engine, 1.0.3"
// Install Aml.Engine as a Cake Addin #addin nuget:?package=Aml.Engine&version=1.0.3 // Install Aml.Engine as a Cake Tool #tool nuget:?package=Aml.Engine&version=1.0.3
AMLEngine2.1
AutomationML 2.1 Application Programming Interface
The AMLEngine2.1 has changed its namespace naming in the move from the older version v3.x.x, which is still availabe as the nuget package AMLEngine. The AMLEngine2.1 is published under the package identifier Aml.Engine which matches the new namespace used in the code.
- The former used namespace CAEXClassModel is now divided into Aml.Engine.CAEX and Aml.Engine.CAEX.Extensions. These namespaces provide basic CAEX processing features.
- The former namespaces AMLEngineExtensions and AML are replaced with Aml.Engine.AmlObjects and Aml.Engine.AmlObjects.Extensions. These namespaces provide AutomationML specific processing features.
- Some extensions formerly contained in the CAEXClassModel and AMLEngineExtensions name spaces have been moved to the Aml.Engine.Services package. This package implements services. It is optional and may be excluded.
Special features like split and merge, schema transformation and others are implemented using services. The AMLEngine implements the service locator pattern to recognize a registered service and use its services. One consequence of the service locator pattern is, that there are no different query methods for fast and XPath based queries anymore. A query is performed by the currently located query service.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net47 is compatible. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
.NETFramework 4.7
- No dependencies.
NuGet packages (10)
Showing the top 5 NuGet packages that depend on Aml.Engine:
Package | Downloads |
---|---|
Aml.Toolkit
The Aml.Toolkit provides basic UI controls based on WPF to visualize AutomationML data. The Toolkit is used in the AutomationML Editor and is available to implement PlugIns for the AutomationML Editor. |
|
Aml.Editor.Plugin.Contract
This Package contains a contract DLL and defines Interface Classes which have to be implemented by AutomationML Editor - PlugIn Developers. When implemented, the PlugIn Class should EXPORT its Interface with Microsoft Extensibility Framework (MEF). |
|
Aml.Engine.Services
Additional services to support the processing of AutomationML documents in addition to the functions of the Aml.Engine. The Aml.Engine recognizes registered services and uses them, for example, for queries or when generating unique names. |
|
Aml.Engine.Services.Signing
AutomationML Application Programming Interface supporting the addition and verification of signatures to AutomationML objects using an ECDSA signature algorithm. |
|
Aml.Editor.API
This API can be used when developing plugins for the AutomationML Editor. The API requires at least version 5.6 of the editor. |
GitHub repositories (1)
Showing the top 1 popular GitHub repositories that depend on Aml.Engine:
Repository | Stars |
---|---|
admin-shell-io/aasx-package-explorer
C# based viewer / editor for the Asset Administration Shell
|
Version | Downloads | Last updated |
---|---|---|
4.0.2 | 122 | 11/4/2024 |
4.0.1 | 202 | 10/21/2024 |
4.0.0 | 170 | 10/19/2024 |
3.3.3 | 951 | 7/30/2024 |
3.3.2 | 204 | 7/16/2024 |
3.3.1 | 779 | 7/1/2024 |
3.3.0 | 209 | 6/28/2024 |
3.2.3 | 2,753 | 5/23/2024 |
3.2.2 | 932 | 3/24/2024 |
3.2.1 | 6,108 | 12/22/2023 |
3.2.0 | 554 | 11/29/2023 |
3.1.7 | 1,841 | 8/15/2023 |
3.1.6 | 2,098 | 6/1/2023 |
3.1.5 | 203 | 5/24/2023 |
3.1.4 | 208 | 5/21/2023 |
3.1.3 | 1,867 | 4/24/2023 |
3.1.2 | 351 | 4/14/2023 |
3.1.1 | 990 | 2/22/2023 |
3.1.0 | 480 | 2/20/2023 |
3.0.3 | 796 | 1/17/2023 |
3.0.2 | 832 | 12/17/2022 |
3.0.1 | 833 | 12/15/2022 |
3.0.0 | 939 | 12/15/2022 |
2.0.9 | 8,034 | 10/5/2022 |
2.0.8 | 7,336 | 6/9/2022 |
2.0.7 | 3,793 | 4/30/2022 |
2.0.5 | 1,007 | 4/14/2022 |
2.0.4 | 884 | 3/31/2022 |
2.0.3 | 611 | 3/28/2022 |
2.0.2 | 705 | 3/24/2022 |
2.0.1 | 568 | 3/9/2022 |
2.0.0 | 3,065 | 3/5/2022 |
1.7.4 | 7,337 | 3/4/2022 |
1.7.3 | 465 | 3/4/2022 |
1.7.2 | 10,700 | 11/19/2021 |
1.7.1 | 439 | 11/19/2021 |
1.7.0 | 846 | 10/15/2021 |
1.6.5.2 | 2,131 | 9/11/2021 |
1.6.5.1 | 471 | 9/10/2021 |
1.6.4 | 533 | 8/23/2021 |
1.6.3 | 747 | 8/3/2021 |
1.6.2 | 653 | 7/29/2021 |
1.6.1 | 567 | 7/20/2021 |
1.6.0 | 491 | 7/18/2021 |
1.5.9 | 2,627 | 6/3/2021 |
1.5.8 | 1,278 | 3/5/2021 |
1.5.7 | 3,648 | 2/18/2021 |
1.5.6 | 473 | 2/3/2021 |
1.5.5 | 495 | 1/31/2021 |
1.5.4 | 413 | 1/31/2021 |
1.5.3 | 452 | 1/29/2021 |
1.5.2 | 496 | 1/18/2021 |
1.5.1 | 560 | 1/4/2021 |
1.5.0 | 576 | 12/5/2020 |
1.4.5 | 613 | 11/18/2020 |
1.4.4 | 610 | 11/11/2020 |
1.4.3 | 915 | 6/21/2020 |
1.4.2 | 598 | 6/15/2020 |
1.4.1 | 904 | 5/30/2020 |
1.4.0 | 7,285 | 5/24/2020 |
1.3.6 | 9,213 | 11/22/2019 |
1.3.5 | 627 | 11/16/2019 |
1.3.4 | 680 | 10/13/2019 |
1.3.3 | 619 | 10/5/2019 |
1.3.1 | 736 | 8/18/2019 |
1.3.0 | 924 | 7/26/2019 |
1.2.7 | 667 | 7/5/2019 |
1.2.6 | 656 | 7/4/2019 |
1.2.2 | 5,488 | 5/21/2019 |
1.2.0 | 700 | 5/14/2019 |
1.1.2 | 724 | 5/13/2019 |
1.1.1 | 1,514 | 2/13/2019 |
1.1.0 | 1,141 | 10/9/2018 |
1.0.21 | 1,079 | 8/1/2018 |
1.0.20 | 967 | 7/25/2018 |
1.0.19 | 999 | 7/20/2018 |
1.0.16 | 1,117 | 7/18/2018 |
1.0.15 | 1,041 | 7/12/2018 |
1.0.14 | 1,199 | 6/7/2018 |
1.0.13 | 1,171 | 5/14/2018 |
1.0.12 | 1,071 | 5/4/2018 |
1.0.11 | 1,163 | 5/2/2018 |
1.0.10 | 1,092 | 4/24/2018 |
1.0.9 | 1,298 | 4/9/2018 |
1.0.8 | 1,092 | 4/4/2018 |
1.0.7 | 1,077 | 3/23/2018 |
1.0.6 | 1,155 | 3/18/2018 |
1.0.5 | 1,141 | 2/28/2018 |
1.0.4 | 1,148 | 2/28/2018 |
1.0.3 | 1,075 | 2/5/2018 |
1.0.2 | 1,099 | 1/31/2018 |
1.0.1 | 1,202 | 1/15/2018 |
1.0.0 | 1,385 | 1/10/2018 |
Fixed an issue, where the LookupService could run into a deadlock situation when called during a lookup table update.
ValidatorService should not complain about missing IDs in SystemUnitClass objects. ID is not mandatory for SystemUnitClass objects.