🚀 Running Your Uniface 10.4 Applications: A Simple Guide

Posted on by — No Comments ↓

⚠️ This blog post was created with AI assistance

If you’re working with Uniface 10.4, one of the first things you need to know is how to actually run your applications. Let’s break this down into easy-to-understand steps! 💡

📋 What You Need to Know

Uniface applications run through the Uniface runtime engine, which is the uniface.exe file. Think of it as the motor that powers your application. There are two main ways to execute your Uniface application:

🎯 Method 1: Using uniface.exe Directly

The first and most straightforward method is to use uniface.exe with your application shell as a parameter.

Example:

uniface.exe myapp

In this example, myapp is your application shell name. The runtime engine will look for your application and start it. Simple as that! ✨

⚙️ Configuration Files

Before running your application, you might need to create two important configuration files:

  • .ini file – This is your configuration file where you can customize things like icons and logos for your application
  • .asn file – This is your assignment file that tells Uniface where to find resources

Pro tip: You can use the [APPLICATION] section in the .ini file to make your application look unique with custom icons and logos! 🎨

🎯 Method 2: Creating a Custom Executable

The second method gives your application its own identity by creating a dedicated executable file.

How it works:

  1. Copy uniface.exe to a new file with your application’s name
  2. For example: Copy uniface.exe to myapp.exe
  3. When you run myapp.exe, Uniface automatically looks for an application called “myapp”

Example:

copy uniface.exe myapp.exe
myapp.exe

When you double-click myapp.exe, Uniface will automatically search for:

  • myapp.ini (configuration file)
  • myapp.asn (assignment file)
  • An application shell named “myapp”

⚠️ Important Difference!

Here’s something crucial to remember: Only the original uniface.exe can run different applications as parameters. 🔑

What this means:

  • ✅ uniface.exe myapp works
  • ✅ uniface.exe anotherapp works
  • ❌ myapp.exe anotherapp does NOT work

Once you’ve copied uniface.exe to myapp.exe, that executable is locked to running only “myapp”. It won’t accept other application names as parameters.

🎓 Quick Summary

Method Command Flexibility
Direct Execution uniface.exe myapp Can run any application
Custom Executable myapp.exe Runs only “myapp”

🎪 When to Use Each Method?

Use Method 1 (uniface.exe with parameters) when:

  • You’re developing and testing multiple applications
  • You need flexibility to switch between different applications
  • You’re running applications from scripts or command line

Use Method 2 (custom executable) when:

  • You’re deploying a production application
  • You want your application to have its own branded executable
  • You want users to simply double-click an icon to launch your app

🎬 Final Thoughts

Running Uniface applications doesn’t have to be complicated! Whether you choose to use the generic runtime engine or create a branded executable, both methods are straightforward once you understand the basics. Remember to set up your configuration files properly, and you’ll be up and running in no time! 🚀

Happy coding! 👨‍💻👩‍💻

Leave a Reply