v1.0.11

What's Changed

Features

• Support NuGet servers, which only support api keys. For this kind of servers, in the login dialog you can now leave the Username empty and write the Apikey into the Password field
• If a NuGet server was used to host packages other than PLC libraries, this library would show up in the catalog. Now this kind of packages are filtered away to avoid clutter and having packages, which ultimately can not be installed on the TwinCAT system.

Bugfixes

• When using multiple NuGet repositories (this included Beckhoff repositories, because they are essentially NuGet repositories with some tweaks), an error would show up after successfully installing a package, if the repository was not the first configured NuGet repository.

Full Changelog: v1.0.10..v1.0.11

v1.0.10

What's Changed

Features

• Support for parameters /CLI /TCXAE15 /TCXAE17, which can be used together with /SILENT for running a 'silent' installation (no prompts)
  • /CLI install command-line utilities in the (default) installation folder (C:\Program Files (x86)\Zeugwerk GmbH\Twinpack)
  • /TCXAE15 integrate Twinpack into TcXaeShell 32-bit
  • /TCXAE17 integrate Twinpack into TcXaeShell 64-bit

Full Changelog: v1.0.9..v1.0.10

v1.0.9

What's Changed

Bug Fixes

• Uncompiled packages on a custom NuGet server could not be installed, because the implementation had the flag for compiled hardcoded. Now the flag is evaluated by checking the tags of the NuGet package for the tag tp-compiled-library and by default packages are uncompiled for NuGet packages. Closes #138

Full Changelog: v1.0.8..v1.0.9

v1.0.8

What's Changed

Features

• The version of Twinpack is now shown in the Visual Studio Output Window, if no update is available the version is also shown in the Catalog instead of the 'new release is available hint' (#130)

Bug Fixes

• When using a NuGet Server, the Login dialog would not close unless login was successful (#135, #136)
• When using a NuGet Server, the download counter could be null, causing a nullpointer exception. Made download counter nullable and hide it in the catalog if it is 'null' or '0' (#137). Thanks @dfreiberger for this contribution

Full Changelog: v1.0.7..v1.0.8

v1.0.7

What's Changed

Bug Fixes

• fix: switches branches was no longer possible in certain situations (affected feature branches of Zeugwerk Packages)
• fix: installing latest version of a package as a placeholder was suggesting to use the latest version of a specific branch rather than the latest available

Full Changelog: v1.0.5..v1.0.7

v1.0.5

What's Changed

New Features

• feat: support for multiple package servers
• feat: support for NuGet protocol!
• feat: support Beckhoff repositories as known since TwinCAT 4026's TcPkg
• feat: packages can now be added to a PLC using always the Latest version (In TwinCAT this is indicated by *
• feat: packages can now be added as
  • qualified only: Library modules (and variables) are called in the project only with prepended namespace paths.
  • optional: The selected library is treated as optional. When downloading the project that references the library, no error is reported, even if the library is not available in the library repository.
  • publish all IEC symbols: If the current project is later included as a library in another project, the IEC symbols of the selected library reference are published in this project as if the selected library reference were directly included in the project. You can address the library function blocks unambiguously if you use the corresponding namespace path. This consists of the namespace of the "parent" library and its own namespace and precedes the function block name.
• feat: improved error messages and in general make logs easier to read
• feat: close dialogs by pressing ESC

Bug Fixes

• fix: package configuration are not resolved on reload

Full Changelog: v0.8.0..v1.0.5

v0.8.1

What's Changed

New Features

• feat: support TwinCAT 3.1.4026.x
• feat: improved catalog loading and refreshing speed
• feat: update catalog after reset to have fresh feedback on installed libraries
• feat: improved migration support in case that config.json is broken
• feat: added option to TwinpackCli to skip pushing if a package already exists
• feat: Twinpack registry support dependencies
• feat: added support for xtis that contain PLCs when creating a configuration file

Bug Fixes

• fix: fixed exception in some cases when filtering is active
• fix: when creating a config from a sln file, projects are ignored
• fix: multiple projects per solution are handled correctly now
• fix: problems when providing relative paths
• fix: in some cases plcproj paths are not handled correctly
• fix: ignore empty plcs when loading a solution
• fix: handling with tokens on refresh
• fix: TwinCAT x64 shell is more strict about the threads that are used

v0.6.4

What's Changed

New Features

• TwinpackCli push command can now be used without a config.json file. All mandatory information for publishing is extracted directly from the .library file(s). The config file can still be used for optional meta data.
• Introducing Twinpack Registry, which allows to publish packages directly from GitHub releases. To make a package available on Twinpack simply create a PR in this repository, which adds your GitHub project to the repositories.txt file.
• Package binaries (.library files) can now be downloaded from arbitrary locations. For instance, directly from a GitHub release. When publishing with Twinpack Registry this is the new default.
• Twinpack now stores a hash for every package version. Together with arbitrary download locations, this is used to check if a binary has been tempered with after publishing and the user is warned.
• Implemented a Library Reader that can reliably extract meta information from .library files
• Improved User experience when searching packages, it is much faster now and packages already fetched are available instantly
• Asynchronous operations now all use cancellation tokens so the can be aborted, which can be triggered in the Visual Studio Extension

Bug Fixes

• Fixed a crash of Visual Studio / XAE Shell, which occurs if a function block of a library is displayed and the library simultaneously updated by closing all library related windows before performing an update.
• Installing dependencies now is recursively
• Installing Runtime Licenses now is recursively
• License Dialogs now is recursively
• The catalog is now properly locked during updates
• The “Load More” button now is only visible in the catalog view
• Create config now also works correctly if the config.json only covers some of the PLCs in the project

v0.4.2

What's Changed

New Features

• Preliminary support for TwinCAT 4026.x, which is still in beta phase. This means that Twinpack now works in Visual Studio 2022 and the upcoming Twincat XAE Shell
• Introducing Twinpack CLI. At the moment the main purpose of the command line interface is for CI servers: There it can be used to push packages that are built on the CI server to the Twinpack Server and/or pull packages from the Twinpack Server before building. At the moment we do not plan to add other CLI commands - if you want such a feature create a feature request in "Issues".
• Zeugwerk's CI tool zkbuild-action now fully integrates with Twinpack CLI. This means that any PLC on GitHub can use the action for CI as long as it only uses dependencies that ship with TwinCAT or packages that are available on TwinPack.
• Twinpack DLL is now a strong-named assembly
• By default Twinpack now adds all dependencies of a package as references to the PLC, this behavior can be switched off with a checkbox
• Twinpack Packages can now be categorized in Frameworks

Bug Fixes

• Icon scaling was weird for non-square icons
• Download counter was not shown in some cases and in some cases not updated correctly when switching between views
• Errorhandling if Twinpack is not available (i.e. no internet connection)

v0.2.15

feat: allow to continue if no solution is found
fix: do not load available packages if it is not needed
fix: files on a different drive than the solution could not be loaded. (related to #88)
fix: potential null pointer if non-PLC projects are in the solution
fix: if check all objects fails there is no visual indication about it besides the log
fix: added log messages on failed push or login
fix: added twinpack servers to list before connecting to any servers
fix: handle errors if connection to twinpack server can not be established (closes #89)