01 / THE CHALLENGE
Understanding the problem.
During a Citrix Cloud migration, developers depended on a legacy application with an old VBScript launch wrapper. The code, its dependencies and the way those pieces combined to deliver the launch experience were no longer understood. Replacing it required first reconstructing how the existing solution worked.
- 01Legacy VBScript dependencies
- 02PowerShell GUI + endpoint logic
- 03Seamless Citrix delivery
02 / MY INVESTIGATION
Following the evidence.
I pulled apart the launcher and its dependencies, read through the VBScript and traced how the components worked together. That gave me the understanding needed to rebuild the behaviour the developers relied on.
A central requirement was how the destination endpoint was constructed. The developers had established naming conventions for their AWS-hosted resources, and the launcher needed to dynamically assemble the intended endpoint from those conventions.
The replacement also had to fit the Citrix delivery model. Its graphical interfaces, launch dependencies and connection workflow needed to operate as a seamless published application.
03 / IMPLEMENTATION
Putting the work into practice.
- 01
Rewrote the legacy launch-wrapper dependencies in PowerShell, translating the understood behaviour into the replacement implementation.
- 02
Developed graphical user interfaces for the developer launch workflow.
- 03
Implemented dynamic endpoint construction using the developers' naming conventions, supporting the workflow for secure access to external resources hosted in AWS.
- 04
Packaged and deployed the application for seamless delivery within Citrix.
04 / OUTCOME & EVIDENCE
What the work delivered.
Rebuilt the launch workflow in PowerShell and delivered it as a packaged, seamless Citrix application for developers accessing AWS-hosted resources.
Recovered understanding
Reverse engineered the VBScript, dependencies and launch behaviour of a previously poorly understood solution.
Replacement implementation
PowerShell launch logic and graphical interfaces, including naming-convention-driven endpoint assembly.
Citrix delivery
The replacement workflow was packaged and deployed as a seamless application for developers.
05 / ENGINEERING PERSPECTIVE
What I take forward.
Modernising a legacy tool starts with understanding the behaviour people depend on. In this case, the job connected code investigation, user-interface development, endpoint logic and the practical requirements of virtual application delivery.
Organisation names are generalised. These accounts describe my work without publishing client systems, internal logs or proprietary source code.