Bug 60781 (vs-557313) - [Asset Editor] Import button should let you import multiple .imageset
Summary: [Asset Editor] Import button should let you import multiple .imageset
Alias: vs-557313
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in (show other bugs)
Version: Trunk
Hardware: PC Mac OS
: Low enhancement
Target Milestone: 15.7
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2017-11-20 22:39 UTC by Vincent Dondain [MSFT]
Modified: 2018-02-23 18:28 UTC (History)
3 users (show)

See Also:
Tags: vs-sync
Is this bug a regression?: ---
Last known good build:


Description Vincent Dondain [MSFT] 2017-11-20 22:39:03 UTC
I wanted to explain how to move all assets from an iOS library project's asset catalog to an iOS project with an existing asset catalog (and assets inside it) but it turns out the import button has some limitation.

1. It doesn't seem possible to select multiple .imageset (inside a .xcassets). You can only import them 1 by 1 which is not ideal if you need to import 600 images sets.

2. It's possible to import the .imageset itself but that seems to mess-up the hierarchy (an xcasset inside an xcasset). The import should not try to include the the .xcasset folder but only its content.

Steps to repro:

- Create an iOS project.
- Create 3 image sets (open asset editor, right click the left section, select new image set and add random images).
- Create a new iOS project, open the asset editor, right click the left section and select import.

Expected behavior:

- Select multiple .imageset or when selecting a .xcasset it only imports the .imageset inside it.

Version information: https://gist.github.com/VincentDondain/6002340cf70279cdf93d086ae67d5220
Comment 1 Jeffrey Stedfast 2018-01-29 16:20:17 UTC
PR: https://github.com/xamarin/md-addins/pull/2840

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Note You need to log in before you can comment on or make changes to this bug.