After VS update, can no longer link release build

[Gerry]

Stay away from Visual Studio update 15.7.2, it is a project killer. Anyone have any ideas how to fix this?

 

1>Foobar.Android -> C:\Apps\foobar-telerik-mobile-app\foobar\Android\bin\Release\foobar.Android.dll<br>1>No way to resolve conflict between "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.<br>1>The "LinkAssemblies" task failed unexpectedly.<br>1>Mono.Linker.MarkException: Error processing method: 'System.Void Telerik.XamarinForms.DataGrid.RadDataGridResourceDictionary::InitializeComponent()' in assembly: 'Telerik.XamarinForms.DataGrid.dll' ---> Mono.Cecil.ResolutionException: Failed to resolve System.Func`2<System.String,System.String> Xamarin.Forms.Internals.ResourceLoader::get_ResourceProvider()

[Gerry]

I also posted on StackOverflow; somebody posted the solution is to go into Android Options and set "Linking" to "None". Weird.

[Gerry]

Problem now is output apk is over 100 Mb

[Lance | Manager Technical Support]

Hello Gerry,

This issue is rooted in the issue that I replied about in your other forum post that I just replied to. The same Feedback Portal item will notify you when we apply the fix for it. I will also return here and update you as soon as I learn more from the development team.

The method signature I was speaking about is the Func<string, string> you see in the stack trace (Xamarin changed it to Func<AssemblyName, string, string>). We are working on a way to fix this, and are hoping to introduce the least amount if breaking changes at the same time. 

Note:
Yes, not using the linker will prevent build error, but you'll have significantly larger app size and still may experience runtime issues when that ResourceDictionary is needed at runtime, because the function won't work as expected.

Regards,
Lance | Tech Support Engineer, Sr.
Progress Telerik

[Lance | Manager Technical Support]

Hi Gerry,

I have an update on this for you, you can see it in the original thread. For your convenience, I'll paste my reply here:

Here's where we stand now:

- I was able to isolate the problem in a 'vanilla' Xamarin.Forms reproducible (i.e. no Telerik UI for Xamarin)
- I reported this to the Xamarin.Forms developers in a Xamarin.Forms Issue and they've confirmed the bug as a regression
- I have escalated this to the Microsoft program manager responsible for Xamarin.Forms (we're in direct contact and are working to resolve this quickly)

If you'd like to read my report, see the reproducible and follow the discussion, go here: https://github.com/xamarin/Xamarin.Forms/issues/2835.

If you'd like to add your voice to the discussion, you can use the "Thumbs Up" button on my initial post (click the smiley face at the top), there's no need to add another post to the thread as they're aware and working on it now.


Next Steps

I will come back here and post another update as soon as I have more news to share. If all goes well, a fix could be released in the next release of Xamarin.Forms 3.0, (no Telerik UI for Xamarin update necessary). However, if they are not able to provide a fix, we are still working on upgrading Telerik UI for Xamarin to use Xamarin.Forms 3.0.

Regards,
Lance | Tech Support Engineer, Sr.
Progress Telerik

[Lance | Manager Technical Support]

Hello Gerry,

I just replied to your other forum thread about the Linker and that Xamarin has fixed the underlying problem that causes the Failed to resolve System.Func`2<System.String,System.String>  build error.

For this thread's reply I also wanted to bring your attention to yesterday's Visual Studio 2017 update (15.7.3). There were a bunch of Xamarin and Xamarin.Forms project issue fixes, here are the release notes: https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#15.7.3

Regards,
Lance | Tech Support Engineer, Sr.
Progress Telerik