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.
Created attachment 9330 [details]
The attached sample will not build from command line after updating to the unified API.
**Steps to Reproduce:**
1. Open terminal to the directory path of the attached project files
2. Run this command
> /Applications/Xamarin\ Studio.app/Contents/MacOS/mdtool build -t:build "-c:Debug:iPhoneSimulator" -p:mdtool_bug/mdtool_bug.sln
Fails to compile
> AppDelegate.cs(25,4): error CS0103: The name `iOSAppExtension1' does not exist in the current context
> AppDelegate.cs(26,4): error CS0103: The name `iOSAppExtension2' does not exist in the current context
No compilation issues
**Build Date & Platform:**
Was not an issue using the classic API. Solution builds fine in Xamarin Studio.
Unified applications requires `msbuild` (not the old, custom addin-based, build tools that mdtool can invoke). Just typing `xbuild` + ENTER works fine (as it picks up the .sln and the default project/config).
note: I'm not sure if mdtool can invoke msbuild automatically (but that would only be slower).
Same result when launch xbuild from Xcode build phase.
I'm not sure what you mean by launching "xbuild from Xcode". Do you mean you're running this XI build from another build, run by Xcode ? and getting the same errors as above ?
That's likely because the environment (e.g. PATH) differs from your terminal (but first ensure it works from a terminal window).
A full (maximum diagnostics) build log that shows every steps will be needed to duplicate the issue.
I send to support mail with updated environment to reproduces this issue at January 14, 2015 at 11:48 AM.
Temporary workaround: env -i xbuild build-parameters.