Bug 36172 - Error: Error executing task DetectSdkLocations: Unknown TargetFrameworkIdentifier: .NETFramework (iECDDatasource)
Summary: Error: Error executing task DetectSdkLocations: Unknown TargetFrameworkIdenti...
Alias: None
Product: iOS
Classification: Xamarin
Component: MSBuild ()
Version: XI 9.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: C6SR1
Assignee: Bugzilla
Depends on:
Reported: 2015-11-23 16:44 UTC by Jon Goldberger [MSFT]
Modified: 2015-11-24 15:43 UTC (History)
3 users (show)

Tags: BZSRC6S1
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 Jon Goldberger [MSFT] 2015-11-23 16:44:15 UTC
## Description

After updating to Xamarin 4 (customer's version info in private comment  below), customer got the following error on build:

>/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets: Error: Error executing task DetectSdkLocations: Unknown TargetFrameworkIdentifier: .NETFramework (iECDDatasource)

I found this internal bug report that _may_ be related:

I do not have steps to reproduce as no test project was provided. 

Further info from customer is in private comment below.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2015-11-24 04:30:54 UTC
This is most likely something wrong with the customer's project file (i.e. a dup of bug #35890).

Would it be possible to get access to the project that's failing to build (and a diagnostic build log)?
Comment 5 Jon Goldberger [MSFT] 2015-11-24 15:33:10 UTC
Customer was able to figure this out. 

From the customer:

"In the project properties there is a property called “iOS SDK Version.” After the Xamarin install it was set to “iOS 9.0 (Not Installed)”

Setting the property to iOS 9.1 fixed the issue. In my mind if there is only one SDK present then it should automatically be set to iOS 9.1 after the Xamarin installation. Please add this to your next build."

Setting status to RESOLVED INVALID

However my understanding is that if a SDK Version is set explicitly, it will not (and perhaps should not) be changed with an update. If the compile SDK is set to "Default" in the project options then the newly updated SDK from XCode will be used.