Case Study
Here's the Case-Study of some of our works we'd like you to see...
EazyFuel
The EazyFuel enterprise fleet fuel card management platform, built on .NET Framework 4.7, consists of multiple interconnected applications and shared libraries. As new features were added, differences in shared library versions began causing system instability. These issues affected multiple modules and slowed down reliable feature delivery. The situation highlighted the need for tighter dependency management across the platform.
The Challenge
During the development of new functionality, the engineering team upgraded a commonly used JSON serialization NuGet package to a newer version to support enhanced capabilities in selected modules.
While the upgrade worked correctly in some components, it caused runtime compatibility issues in others that relied on shared .NET Framework 4.7 libraries. The challenges included:
- Runtime exceptions caused by assembly version mismatches
- Binding redirect conflicts across application configuration files
- Inconsistent behavior between BackOffice, APIs, and reporting modules
- Regression risks when attempting configuration-based fixes
Due to the limitations of dependency resolution in the .NET Framework, relying on binding redirects alone proved unreliable and introduced further instability across the ecosystem.
The Solution
A detailed root-cause analysis was performed using dependency graph inspection and targeted runtime testing across all applications.
The investigation revealed that the core issue stemmed from incompatible NuGet package versions being referenced across multiple .NET Framework 4.7 projects.
To resolve the issue and stabilize the platform:
- The JSON serialization library was standardized to the lowest version fully compatible with .NET Framework 4.7
- All shared libraries and consuming applications were aligned to use the same dependency version
- Legacy compatibility was preserved without blocking ongoing feature development
Rather than chasing the latest package releases, the focus shifted to stability, compatibility, and predictability across the entire solution.
By enforcing strict dependency version alignment across all .NET Framework 4.7–based projects, the EazyFuel platform achieved stable runtime behavior across all components, eliminated recurring assembly binding failures, enabled faster and safer delivery of new features, and significantly improved the maintainability of shared enterprise libraries.
Technology Stack
