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
Developer Community or GitHub 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.
There is a bug in the Mono implementation of System.IO.Compression.ZipArchive.CreateEntry where it ignores the CompressionLevel argument altogether. It does not translate "NoCompression" into "Store", which means invalid entries get created for zero-byte streams.
Anyway, because of this, I wanted to use the corefx version, available on NuGet, which is entirely managed and does not in turn depend on ICSharpCode.
However, either via the MSBuild targets for mmp, the Xamarin.Mac FX version is always ultimately copied into the .app bundle, effectively clobbering the NuGet version.
This is a "full framework" (desktop) app:
I just confirmed this is also an issue with the supported mobile profile:
This may be at least partially related to bug #48743.
However, if I manually edit the csproj to give System.IO.Compression a correct hint path, we can still see that mmp is given the target framework path for the assembly, and not the NuGet path.
I'm blocking this bug on XS's bug (since mmp isn't even getting the right path to mess up).
@Abock - Since https://bugzilla.xamarin.com/show_bug.cgi?id=48743 got close answered, is this still an issue?
@Abock any comments about this? Should we close the bug?
I think this can be closed. The System.IO.Compression NuGet targets 4.6. If 4.5 is the target, the hint path is not set by XS, so mmp would have no way to know how to resolve the NuGet version.