Cannot build projects with latest mono 2018-04 #1845

garuma · 2018-06-18T19:12:53Z

Either a normal build or invoking msbuild /restore will error-out with the following:

/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(654,2): error MSB3644: The reference assemblies for framework "MonoAndroid,Version=v1.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.

This issue is reproducible with build from mono/mono@07c8f25 but not with earlier build mono/mono@33a9dca which could suggest mono/mono@543b687 is the culprit

The text was updated successfully, but these errors were encountered:

kdubau · 2018-06-28T14:52:03Z

@radical any updates here? This is blocking a lot of testing.

GouriKumari · 2018-07-03T17:39:32Z

nuget restore of a solution is failing with the same error and this blocks the building of iOS projects in solution.

nuget restore "/Users/xamarinqa/agent/_work/r26/a/xamarin-forms-book-samples/Chapter14/AbsoluteDemo/AbsoluteDemo.sln"
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(654,2): error MSB3644: The reference assemblies for framework "MonoAndroid,Version=v1.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. [/Users/xamarinqa/agent/_work/r26/a/xamarin-forms-book-samples/Chapter14/AbsoluteDemo/AbsoluteDemo/AbsoluteDemo.Droid/AbsoluteDemo.Droid.csproj]

MSuild/mono on osx supports a fallback search path for Target frameworks: `/Library/Frameworks/Mono.framework/External/xbuild-frameworks` This was earlier implemented in mono/msbuild via the app.config, but then was changed to be specified via the property `$(TargetFrameworkFallbackSearchPaths)`. And passed to `GetReferenceAssemblyPaths` task via a new task parameter `TargetFrameworkFallbackSearchPaths`. This also means that if any user of `GetReferenceAssemblyPaths` does not use this new parameter, then on osx, msbuild won't be using any fallback search path. MSBuild sets a default value for that property (`$(TargetFrameworkFallbackSearchPaths)`) on osx, but XA's use of GRAP task needs to pass that property as an argument for the new parameter. Since, there is a change in behavior in msbuild, this brings up multiple cases: ``` XA mono/msbuild old/existing older (with old behavior) => No change required old/existing newer (new param+prop) => Change required in msbuild to not break this [1] newer older (with old behavior) => Use GRAP task w/o the new parameter newer newer (new param+prop) => Use GRAP task with the new parameter+property ``` The last two cases are what need changes in XA and this PR does that. 1. if we are running on a version that doesn't support the new param, then don't use it 2. if we are running on a version that does support the new param on GRAP task, then use that and pass the property `$(TargetFrameworkFallbackSearchPaths)` as an argument. The *version* (value of `$(MSBuildVersion)`) above also has two cases: 1. On mono, version older than the one for the commit that introduced the change 2. And on full framework/windows, anything newer than 15.8 preview 3, since preview4 will have the GRAP task change. Fixes dotnet#1845 . --- 1. To avoid breaking older versions of XA which don't use pass the new property to the task, msbuild internally uses the default path for osx if none was specified. This behavior can be disabled by setting `DISABLE_FALLBACK_PATHS_HACK_IN_GRAP_OSX`.

.. fallback paths. MSuild/mono on osx supports a fallback search path for Target frameworks: `/Library/Frameworks/Mono.framework/External/xbuild-frameworks` This was earlier implemented in mono/msbuild via the app.config, but then was changed to be specified via the property `$(TargetFrameworkFallbackSearchPaths)`. And passed to `GetReferenceAssemblyPaths` task via a new task parameter `TargetFrameworkFallbackSearchPaths`. This also means that if any user of `GetReferenceAssemblyPaths` does not use this new parameter, then on osx, msbuild won't be using any fallback search path. MSBuild sets a default value for that property (`$(TargetFrameworkFallbackSearchPaths)`) on osx, but XA's use of GRAP task needs to pass that property as an argument for the new parameter. Since, there is a change in behavior in msbuild, this brings up multiple cases: ``` XA mono/msbuild old/existing older (with old behavior) => No change required old/existing newer (new param+prop) => Change required in msbuild to not break this [1] newer older (with old behavior) => Use GRAP task w/o the new parameter newer newer (new param+prop) => Use GRAP task with the new parameter+property ``` The last two cases are what need changes in XA and this PR does that. 1. if we are running on a version that doesn't support the new param, then don't use it 2. if we are running on a version that does support the new param on GRAP task, then use that and pass the property `$(TargetFrameworkFallbackSearchPaths)` as an argument. The *version* (value of `$(MSBuildVersion)`) above also has two cases: 1. On mono, version older than the one for the commit that introduced the change 2. And on full framework/windows, anything newer than 15.8 preview 3, since preview4 will have the GRAP task change. Fixes dotnet#1845 . --- 1. To avoid breaking older versions of XA which don't use pass the new property to the task, msbuild internally uses the default path for osx if none was specified. This behavior can be disabled by setting `DISABLE_FALLBACK_PATHS_HACK_IN_GRAP_OSX`.

.. fallback paths. MSuild/mono on osx supports a fallback search path for Target frameworks: `/Library/Frameworks/Mono.framework/External/xbuild-frameworks` This was earlier implemented in mono/msbuild via the app.config, but then was changed to be specified via the property `$(TargetFrameworkFallbackSearchPaths)` [1]. And passed to `GetReferenceAssemblyPaths` task via a new task parameter `TargetFrameworkFallbackSearchPaths`. This also means that if any user of `GetReferenceAssemblyPaths` does not use this new parameter, then on osx, msbuild won't be using any fallback search path. MSBuild sets a default value for that property (`$(TargetFrameworkFallbackSearchPaths)`) on osx, but XA's use of GRAP task needs to pass that property as an argument for the new parameter. Since, there is a change in behavior in msbuild, this brings up multiple cases: ``` XA mono/msbuild old/existing older (with old behavior) => No change required old/existing newer (new param+prop) => Change required in msbuild to not break this [2] newer older (with old behavior) => Use GRAP task w/o the new parameter newer newer (new param+prop) => Use GRAP task with the new parameter+property ``` The last two cases are what need changes in XA and this PR does that. 1. if we are running on a version that doesn't support the new param, then don't use it 2. if we are running on a version that does support the new param on GRAP task, then use that and pass the property `$(TargetFrameworkFallbackSearchPaths)` as an argument. The *version* (value of `$(MSBuildVersion)`) above also has two cases: 1. On mono, version older than the one for the commit that introduced the change 2. And on full framework/windows, anything newer than 15.8 preview 3, since preview4 will have the GRAP task change. Fixes dotnet#1845 . --- 1. mono/msbuild@bdad9e6 2. To avoid breaking older versions of XA which don't use pass the new property to the task, msbuild internally uses the default path for osx if none was specified. This behavior can be disabled by setting `DISABLE_FALLBACK_PATHS_HACK_IN_GRAP_OSX`.

TargetFrameworks on osx have a default fallback search path: `/Library/Frameworks/Mono.framework/External/xbuild-frameworks` This was earlier implemented in mono/msbuild via the app.config, but then was changed to be specified via the property `$(TargetFrameworkFallbackSearchPaths)`. And passed to `GetReferenceAssemblyPaths` task via a new parameter `TargetFrameworkFallbackSearchPaths`. This also means that if any user of `GetReferenceAssemblyPaths` does not use this new parameter, then on osx, msbuild won't be using any fallback search path. In msbuild's targets files, we pass the new property as argument for the new GRAP task parameter. Accordingly, any non-msbuild users(targets) will need to update their use of GRAP task to get the search path. But this would break any existing/older users which are not using the new parameter and suddenly find that projects won't build because of the missing search path. Existing versions of Xamarin.Android are one example. To ensure that they can continue working, we internally use the fallback path if nothing is passed to the task. This can be disabled by setting `DISABLE_FALLBACK_PATHS_HACK_IN_GRAP_OSX` env var. Fixes dotnet/android#1845

.. once, msbuild has an updated branch for 2018-06/master, then this will point to that. This also picks up fix for dotnet/android#1845 .

Pick up fix for dotnet/android#1845 .

.. once, msbuild has an updated branch for 2018-06/master, then this will point to that. This also picks up fix for dotnet/android#1845 .

Pick up fix for dotnet/android#1845 .

TargetFrameworks on osx have a default fallback search path: `/Library/Frameworks/Mono.framework/External/xbuild-frameworks` This was earlier implemented in mono/msbuild via the app.config, but then was changed to be specified via the property `$(TargetFrameworkFallbackSearchPaths)`. And passed to `GetReferenceAssemblyPaths` task via a new parameter `TargetFrameworkFallbackSearchPaths`. This also means that if any user of `GetReferenceAssemblyPaths` does not use this new parameter, then on osx, msbuild won't be using any fallback search path. In msbuild's targets files, we pass the new property as argument for the new GRAP task parameter. Accordingly, any non-msbuild users(targets) will need to update their use of GRAP task to get the search path. But this would break any existing/older users which are not using the new parameter and suddenly find that projects won't build because of the missing search path. Existing versions of Xamarin.Android are one example. To ensure that they can continue working, we internally use the fallback path if nothing is passed to the task. This can be disabled by setting `DISABLE_FALLBACK_PATHS_HACK_IN_GRAP_OSX` env var. Fixes dotnet/android#1845 (cherry picked from commit 8af44c5)

garuma assigned radical Jun 18, 2018

manish added the regression label Jul 19, 2018

radical mentioned this issue Jul 27, 2018

[mono] Fix regresion for XA (issue #1845) mono/msbuild#69

Merged

radical mentioned this issue Aug 1, 2018

Bump msbuild to track mono-2018-04 mono/mono#9834

Merged

radical pushed a commit to radical/mono that referenced this issue Aug 1, 2018

[msbuild] Bump to point to HEAD of mono-2018-04 msbuild …

2c83c7c

.. once, msbuild has an updated branch for 2018-06/master, then this will point to that. This also picks up fix for dotnet/android#1845 .

radical mentioned this issue Aug 1, 2018

[msbuild] Bump to point to HEAD of mono-2018-04 msbuild … mono/mono#9846

Merged

radical pushed a commit to radical/mono that referenced this issue Aug 1, 2018

Bump msbuild to track mono-2018-04

ad5b6a6

Pick up fix for dotnet/android#1845 .

akoeplinger pushed a commit to mono/mono that referenced this issue Aug 1, 2018

[msbuild] Bump to point to HEAD of mono-2018-04 msbuild … (#9846)

e59ebf5

.. once, msbuild has an updated branch for 2018-06/master, then this will point to that. This also picks up fix for dotnet/android#1845 .

akoeplinger pushed a commit to mono/mono that referenced this issue Aug 1, 2018

Bump msbuild to track mono-2018-04 (#9834)

07ac089

Pick up fix for dotnet/android#1845 .

jonpryor closed this as completed in 90edf81 Aug 8, 2018

radical mentioned this issue Aug 28, 2018

[mono] Fix regresion for XA (issue #1845) (#69) mono/msbuild#72

Merged

ghost locked as resolved and limited conversation to collaborators Jun 8, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot build projects with latest mono 2018-04 #1845

Cannot build projects with latest mono 2018-04 #1845

garuma commented Jun 18, 2018

kdubau commented Jun 28, 2018

GouriKumari commented Jul 3, 2018

Cannot build projects with latest mono 2018-04 #1845

Cannot build projects with latest mono 2018-04 #1845

Comments

garuma commented Jun 18, 2018

kdubau commented Jun 28, 2018

GouriKumari commented Jul 3, 2018