GitHub Build Actions - WPF Studio, Themes, and Shared Library for WPF Forum

The latest build of this product (v25.1.0) was released 26 days ago, which was before this thread was created.

Posted 4 days ago by Mark Tannehill

Hello,

I currently have the license on my machine to develop, test and build our WPF applications. We are using GitHub Actions to run unit testing, sonarqube scans and we have GitHub build the product and publish it to Artifactory. We're experiencing issues when publishing with this approach. Our WPF application will build appropriately, but when it comes time to run, it will fail and shows error messages about not having a license.

I'd really hope and expect we don't need another license for the build server.

What are some methods to get the GitHub Action environment the appropriate license information to build this product and allow users to run it?

Many thanks,

Mark

[Modified 4 days ago]

Comments (1)

Posted 4 days ago by Actipro Software Support - Cleveland, OH, USA

Hi Mark,

It depends on which form of licensing you use with our WPF Controls. Both of the options are described in the Licensing documentation topic.

The RegisterLicense method way of licensing is now the recommended way moving forward since it's compatible with everything and doesn't require installs. It's a simple invocation at app startup before UI is created. Keep in mind that if your unit tests also create our controls, you would need to call RegisterLicense as those unit tests begin as well.

The older licenses.licx way of licensing only works with classic .NET Framework, and requires that a machine building the controls has the WPF Controls installer run on it. For a remote build server, this way is not ideal. There are some workarounds but we'd recommend the first option instead.

Actipro Software Support

Add Comment

Please log in to a validated account to post comments.