Bug 55920 - msbuild doesn't copy .nib and .storyboard files from referenced library
Summary: msbuild doesn't copy .nib and .storyboard files from referenced library
Alias: None
Product: Tools
Classification: Mono
Component: msbuild ()
Version: unspecified
Hardware: PC Mac OS
: Low normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2017-05-03 15:44 UTC by Martin Baulig
Modified: 2017-06-09 18:55 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

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.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Martin Baulig 2017-05-03 15:44:03 UTC
Using this test project: https://github.com/baulig/upgraded-adventure

It's a Xamarin.Mac app, which references a Xamarin.Mac library.  The library defines a storyboard, a main window and main menu.

When using xbuild, the relevant resources are added to the .app directory.  This does not happen with msbuild.

See the https://github.com/baulig/upgraded-adventure/blob/master/filelist-msbuild.txt and
Comment 1 Martin Baulig 2017-05-03 15:57:39 UTC
I worked around the problem by explicitly source-linking all the files in my app instead of using a library.
Comment 2 Jeffrey Stedfast 2017-06-09 18:55:50 UTC
This has been fixed (duplicate of another bug, too lazy to find it right now)