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 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.
Are we to expect the sample projects listed on the "Embedded Frameworks" page at http://developer.xamarin.com/guides/ios/advanced_topics/embedded_frameworks can be compiled in Xamarin for Visual Studio?
I am using Xamarin 184.108.40.2069 in Visual Studio, and when I try to compile the simpleapp-with-framework.csproj, a project in the solutions downloaded from https://github.com/rolfbjarne/embedded-frameworks, I get the error during compile:
"C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.ObjCBinding.CSharp.targets(88,3): error : Tool exited with code: 255. Output:"
Line 88 in this file is where the "Zip" action runs inside the "_CompressFrameworks" build target.
Is it possible the bug is that the compression tool "zip" cannot be found for some reason, when compiling from Visual Studio? Where does the path "/usr/bin/zip" to the zip file get expressed for the build to find and run it, when run from Visual Studio?
That could be the case. The IDE support (both XS and VS) for the feature was not complete for 4.0 (C6, it's a C7 target) so it was not tested on Windows.
Will this be fixed? I'm still seeing this on stable C7(220.127.116.11).
As we've added several improvements to our build system and deploying/debugging mechanism since the bug was reported, I'm resolving it tentatively as Fixed.
That said, if you're still facing this issue with current bits, please feel free to reopen the bug.