Opens in a new tab
WEBINAR
Streamlining Citrix Application Management
Request a Demo
post
Cloudpger
Storefronts

Application Dependencies for Cloudpager Storefronts

Rory Monaghan
Senior Technologist

Configure Application Dependencies to Eliminate Broken Deployments

In 2025, we released Application Dependencies for Cloudpager Workpods, enabling administrators to easily manage dependent applications and incompatibilities. When a given application is added to a Workpod, Cloudpager automatically adds ancillary applications and plugins it is dependent on.

This capability is now being extended to Cloudpager Storefronts, simplifying the management of application dependencies in a self-service context. Users simply click on the application they need and the entire suite of applications and dependencies will be added to their devices, eliminating unintended errors, reducing help desk calls.

Application Dependencies in Cloudpager Storefronts

The way the feature works is that administrators can identify and set application dependencies when publishing applications in a Cloudpager tenant. For example; you can package Visual Studio extensions or project types separately to help reduce overall application size for developers and speed up application delivery of Visual Studio, then set Visual Studio as a dependency for its respective extensions and project types. 

When a given extension or project types is published by an Admin and an employee launches from the Cloudpager Storefront, the dependency will always be delivered first. In this case, Visual Studio will be launched, followed by the applications, extensions, or plugins launched by the employee.

Storefront Dependencies

This process works great for suites of applications, as well as interdependent applications. If you have a Java Web application and employees only ever launch that applet, not Java Web Start itself then this also works great for that use case. You can set Java Web Start or an open-source alternative like Open Web Start as a dependency. When an employee launches the Java Web application, Java Web Start (or Open Web Start) will get dynamically added to their machine before Cloudpager launches the applet on the end user’s endpoint.

The result is applications launching exactly as the end user expects without requiring them to install (or even know about) the prerequisite itself.

Conclusion

Proactively managing application dependencies helps eliminate helpdesk calls by delivering everything needed by applications at time of launch. We hope you’re just as excited about this development as we hare.

We have been enhancing all the Storefront types available in Cloudpager the past few months, including Cloudpager Citrix Storefronts, App Attach Storefronts, and Intune Storefronts. Learn more about how Cloudpager can provide one storefront for all your applications and sign up for our newsletter below so you don’t miss out on the latest Cloudpager updates.

On this page
Share
Stay in the loop
Get the next Numecent post in your inbox — no more than twice a month.
Rory Monaghan
Senior Technologist
Rory has spent his career at the intersection of end-user computing, application delivery, and the Microsoft ecosystem — from packaging shops in Dublin to enterprise architecture in Silicon Valley. He writes about what actually breaks in the wild, and what to do about it.

Related reading

All posts
post
Jul 23, 2026

Self-Service Workpod Enrollment in Cloudpager Storefronts

One of the biggest challenges in enterprise IT isn’t just delivering applications, it’s delivering the right applications, configurations, integrations,…

Learn more
post
Jul 08, 2026

Application Dependencies for Cloudpager Storefronts

Configure Application Dependencies to Eliminate Broken Deployments In 2025, we released Application Dependencies for Cloudpager…

Learn more
post
May 26, 2026

Cloudpager Storefronts Provide On-Demand Access to All Applications

Provide self-service application access for all Windows software anywhere, anytime. When it comes to truly…

Learn more