You’re offline. This is a read only version of the page.
4
Hi all,
I'm trying to figure out what the best practices are to share and maintain component libraries across a tenant.
What I would ideally like to achieve is the following:
Create a component library that all users in my tenant can access so they can use the components in their apps. Whenever I make a change to the original component library, I want all apps that make use of the component library to be prompted to update to the latest version.
What I'm struggling with in particular, is what setup would be needed to make this work across multiple environments. In MSFT documentation I only find reference to sharing and maintaining components libraries within the same environment. Is there a way to share component libraries on tenant level?
To illustrate (simplified):
1. Environment A (DEV): Original component library (Unmanaged Solution)
2. Environment B (PRD): Original component library (Managed Solution) -> All users have access to this environment
3. Environment C (DEV): User imports the CL from step 2 in his development environment + uses components in app
4. Environment D (PRD): User deploys app (and CL) to production environment
When I make changes to the component library and deploy a new version to environment B, is there a way to (soft) push these changes to all environments (C and D) in which there is an instance of my component library?
Many thanks in advance!
Hello @thomass19,
Yes, it is possible to develop a component library in one environment and then to push/import it to other environments.
Generally, you would have one environment in which you develop the solution as unmanaged (env A in your example above), and multiple environments in which you consume the managed solution (envs B, C, D...).
Depending on your level of expertise and the frequency with which you update the solutions, you have two options:
I'm guessing you are quite familiar with unmanaged and managed solutions, but if you want to read up, here is a link.
If you want to automate the ALM process (highly recommended), you have multiple options:
Referencing the solution from envs C and D that you imported into env B is not possible - you would have to import the managed solution into every environment where you want to use the components.
#1
WarrenBelz
791
Most Valuable Professional
#2
MS.Ragavendar
410
#3
mmbr1606
275
Super User 2025 Season 1
Share
Report
All responses (
Answers (
