Embed deployment license automatically into your applications
You’ve built the app. Now you need to ship it — fast, clean, and licensed. With 4D 20 R10, you can automatically embed your deployment license into your application builds — no manual setup, no machine-specific paths. Built for OEM and 4D Desktop – Business Edition licenses, this feature relies on just one setting to make your build file portable, version-controlled, and shareable across machines. License checks now run before the build starts, the logs show which licenses were used, and your settings stay intact if anything goes wrong.
One simple tweak, and deployment becomes one less thing to worry about.
Enhancing macOS Privacy and Security with Application UUID
With the Sequoia update, macOS now relies on the UUID of applications for various privacy and security controls, such as network access. This new feature of macOS could cause issues on the end-user side, such as having to often re-authorize the built 4D applications. To address this, starting from 4D 20 R9, each 4D application built for macOS now has its own application UUID. This change ensures better-tuned access controls. Let’s delve into the details.
Building evaluation applications
In previous versions of 4D, developers could request evaluation licenses for development purposes, but providing end users with evaluation versions of built applications—whether standalone or client/server—was challenging or even impossible.
Starting with 4D 20.7 and 20 R8, you can now create evaluation versions of your applications. When a user runs an evaluation application for the first time on a new machine, it will automatically contact a 4D service to obtain a 14-day evaluation license—without any manual action required from the user.
This blog post will guide you through the process of creating an evaluation version of your application for demo purposes.
How to Implement Continuous Integration with 4D: A Step-by-Step Guide
In the world of software development, a new concept has appeared in recent years called “Continuous Integration.” The definition we see or hear everywhere is :
“CI is a process that automates the compilation, testing, and delivery of an application on a regular and frequent basis.”
Having understood this definition, which expresses an interesting and promising process, what do I need to do to implement it in 4D? If you search the Internet, you’ll find that there are many CI tools and frameworks available.
However, there are several prerequisites before using these CI tools.
Create a Client/Server Application with Build4D tool
Introducing the latest iteration of the Build4D component, now accessible on GitHub. In previous blog posts, we discussed the possibilities with a compiled project, a component, and a standalone application.
Now you can create a script for your Client/Server application from A to Z. And easily integrate it with continuous integration tools.
Let’s see how.
Create a standalone application with the Build4D component
A new build4D component has been available on GitHub for a few months. It empowers you to effortlessly create a compiled project or a component. Things are getting even better; this new component version will enable you to generate a single-user application, expanding the possibilities for your development workflow.
So with tool4D available since v20, integrating the application generation process into your CI (Continuous Integration) tools has become remarkably convenient.
Let’s delve into the details!
Build your Compiled Structure or Component with Build4D
With the introduction of the project mode, it’s pretty easy to manipulate the components of your projects.
In the last few feature releases, we have added several functionalities that allow you to create your own build chain adapted to your team, your working methods, and your needs.
For example:
- Launch a compilation by programming,
- Zip/unzip files and folders with these commands,
- Easily Manage your Application’s Information,
- Headless 4D applications to integrate it into a build tool.
To help you create your own build chain or integrate 4D into a continuous integration tool, we have developed a component named Build4D, available on GitHub with the sources.
For this first step, Build4D allows you to create a compiled structure and a component. We will continue to enrich it to enable you to manage a single-user application, client application, or server application.
Contact us
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!
* Your privacy is very important to us. Please click here to view our Policy