Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Alan, could you look at this patch for System.IO packaging?
We would want to get the fix in 2-10 and master.
Do you have a testcase for where this breaks something? I'll have to read up on the docs to see when Default is used and when Override is used. At the moment we do unconditionally write 'override', but there must be some logic used to decide which one to use.
Ok, so a quick test shows me that if i had three files with the same extension and three different content types, the extension+content type is used in a <Default> node to set the default content type for all files of that extension. Subsequent files which have the same extension and a different content type use the <override> node to explicitly set a new content type. We need to support this.
Though i should also mention that what mono does *should* be fine, so if you have a testcase where a mono package with all <Override> elements fails, I'd love to have it.
I've committed a fix for this so that we write out a <Default> tag the first time we see each file extension. We already had full support for reading files which used both <Default> and <Override> nodes. I'd still love to know why/how the existing method was failing for you though. If you can't remember or there's no simple test, it's fine. I'll just mark the bug as closed as the actual issue is gone now.
Info was provided in an email, so we're all good now!