Bug 13666 - Mono version 3.2.1 breaks Unit testing of PCL-Projects
Summary: Mono version 3.2.1 breaks Unit testing of PCL-Projects
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Configuration ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Martin Baulig
Depends on:
Reported: 2013-07-31 16:10 UTC by Urs Keller
Modified: 2016-11-11 09:35 UTC (History)
2 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 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.

Related Links:

Description Urs Keller 2013-07-31 16:10:03 UTC
After upgrading to 3.2.1 the portable class library projects are built against MonoTouch framework, this prevents a dependent NUnit-Test-Project from loading the assembly.

Looking at the file:
On presence of a MonoAndroid or a MonoTouch licence the build is always performed against one of those 2 target frameworks.

This seemed to have worked quite differently in 3.2.1, was this the hotfix or just a side effect?
Comment 1 Martin Baulig 2016-11-11 09:35:38 UTC
Closing ancient bugs, please reopen if you're still having this problem.