Bug 42415 - Breaking change in build - namespace 'Xamarin' could not be found
Summary: Breaking change in build - namespace 'Xamarin' could not be found
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 9.8 (tvOS / C7)
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2016-07-08 00:00 UTC by Gregh
Modified: 2016-08-04 09:32 UTC (History)
3 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 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.

Related Links:

Description Gregh 2016-07-08 00:00:20 UTC
An existing project that used to build via both Xamarin Studio on iOS and Visual Studio on 2015 now fails to build with error message "The type or namespace name 'Xamarin' cuold not be found. Are you missing an assembly reference?"

As part of the core product, this simply should not be missing.
Comment 1 Sebastien Pouliot 2016-07-08 13:39:01 UTC
Please attach the full build log that shows this issue.
Comment 2 Manuel de la Peña [MSFT] 2016-08-04 09:32:10 UTC
We have not received the requested information. If you are still 
experiencing this issue please provide all the requested information 
and re-open the bug report. Thanks!