# Shared assets dilemna

**URL:** <https://forum.kirupa.com/t/shared-assets-dilemna/284201>\
**Category:** Uncategorized\
**Created:** [March 16, 2009, 4:01pm UTC](https://forum.kirupa.com/t/shared-assets-dilemna/284201 "2009-03-16T16:01:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jenny\_flash](https://avatars.discourse-cdn.com/v4/letter/j/e79b87/32.png) [@jenny\_flash](https://forum.kirupa.com/u/jenny_flash)\
**Post date:** [March 16, 2009, 4:01pm UTC](https://forum.kirupa.com/t/shared-assets-dilemna/284201/1 "2009-03-16T16:01:35Z")

</div>

I’m trying to analyze the pros/cons of different ways of handling shared assets and am hoping for feedback on the best option or perhaps an option I haven’t yet thought of…

1. create gui fla with assets set to export for sharing  
import the needed assets into the destination flas

CONS  
need to update/republish destination flas every time a shared asset is updated

1. create an swc and link to it in the destinations

PROS  
do not need to update destinations  
single gui where assets can be managed

CONS  
must load entire gui instead of just the needed gui items

Is there any way to get the best of both worlds here? It would be very cumbersome to republish all the dependent flas every time a gui asset is updated, but I don’t want to load the entire gui every time an asset is used from it…

Any help appreciated! Thanks.

Jenny