iPack to aPack Modernization Path
Move from .NET Compact Framework and Windows CE-era applications to modern Microsoft .NET, Avalonia UI, and Embedded Linux.
This is not a direct component-by-component migration from iPack to aPack. It is a modernization path where the existing application is analyzed, reusable managed code is preserved where possible, and the graphical user interface is rebuilt using Avalonia UI and modern Microsoft .NET.
Analyze Existing App
Identify application logic, UI code, native dependencies, third-party libraries, and hardware-specific parts.
Separate Logic from UI
Separate reusable C# application logic from the original .NET Compact Framework graphical user interface.
Move to Microsoft .NET
Port reusable managed code from .NET Compact Framework / .NET Framework concepts to modern Microsoft .NET.
Rebuild the UI
Rewrite the graphical user interface using Avalonia UI, optionally using Bee Mobile aPack controls and components.
Prepare Embedded Linux
Build or configure Embedded Linux so that it includes Microsoft .NET and the prerequisites required by Avalonia.
Replace Native Code
Replace Windows CE native dependencies with Linux-compatible libraries, wrappers, drivers, or board-specific integration code.
Deploy and Test
Deploy the modernized application, validate UI behavior, hardware integration, performance, and long-term maintainability.
Need Help?
Bee Mobile can help evaluate your application, modernize the UI, prepare Embedded Linux, and port native dependencies.
Modernization Strategy
Reuse Application Logic
- Business rules
- Data processing code
- Communication logic
- Reusable C# classes and libraries
Rewrite Graphical UI
- Replace .NET Compact Framework UI
- Use Avalonia UI layouts and controls
- Consider Bee Mobile aPack components
- Redesign screens for modern devices
Modernize Platform
- Embedded Linux
- Microsoft .NET runtime
- Avalonia UI framework
- Linux-compatible native libraries
Modernized Application on Embedded Linux
Reused C# application logic + Avalonia UI + optional aPack components + Microsoft .NET + Embedded Linux
A cleaner long-term platform for modern embedded user interfaces.
From iPack to Avalonia and aPack
The iPack to aPack path is different from the iPack to iDesk path. aPack is not a direct replacement for iPack. Instead, it belongs to a modern application stack based on Microsoft .NET, Avalonia UI, and Embedded Linux.
This path is suitable for customers who want to move away from the legacy .NET Compact Framework / Windows CE application model and use the migration as an opportunity to modernize the application architecture, the graphical user interface, and the target operating system.
Applications where the existing C# application logic is still valuable, but the graphical user interface can be redesigned and rebuilt using Avalonia UI and modern Microsoft .NET.
What can usually be reused?
Many iPack-based applications contain valuable application logic written in C# or another managed .NET language. This code may include business rules, calculations, communication protocols, data processing, validation logic, file handling, or other non-visual parts of the application.
- Business logic written in C#
- Non-visual application services
- Data models and validation logic
- Communication and protocol handling code
- Parts of managed libraries that do not depend on .NET Compact Framework-specific APIs
What usually has to be rewritten?
The graphical user interface layer of the original application will usually have to be replaced. User interfaces originally written for .NET Compact Framework, Windows CE, or Windows Mobile cannot be moved directly to Avalonia UI. They should be redesigned and implemented again using Avalonia layouts, styles, controls, and application patterns.
- Original .NET Compact Framework forms and controls
- iPack-specific UI code
- Screen layouts optimized for old Windows CE devices
- Touch interaction patterns tied to old hardware
- Platform-specific UI assumptions
Why consider this path?
This modernization path makes sense when the customer wants to move toward a current software platform. Microsoft .NET can be installed on Embedded Linux, and Avalonia UI can run on top of it. This makes it possible to build modern C# applications for embedded devices while still preserving selected parts of the existing application logic.
| Advantages | Challenges |
|---|---|
| Moves the application to modern Microsoft .NET. | The original graphical user interface usually has to be rewritten. |
| Allows the use of Avalonia UI on Embedded Linux. | The migration is more of a modernization project than a direct port. |
| Can preserve valuable C# application logic. | Code tied to .NET Compact Framework-specific APIs must be reviewed and adapted. |
| Creates a cleaner long-term architecture for future development. | Native Windows CE dependencies still need Linux-compatible replacements. |
| Allows selected Bee Mobile aPack controls and components to be used in the new UI. | aPack is a small component set, not a full replacement for the complete iPack product. |
Modernization support
Need help modernizing your iPack application?
We can help evaluate your existing application, identify reusable C# code, redesign the graphical user interface with Avalonia UI, prepare Embedded Linux with Microsoft .NET, and replace Windows CE native dependencies with Linux-compatible alternatives.