Bug 43346 - Sample CustomRenderers/ContentPage fails in Visual Studio. (Could not load assembly...)
Summary: Sample CustomRenderers/ContentPage fails in Visual Studio. (Could not load as...
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-08-15 12:30 UTC by Gerald Hoops
Modified: 2016-08-16 08:42 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 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 Gerald Hoops 2016-08-15 12:30:09 UTC
Download sample from here:

Correct Konfiguration Manager settings to run on Android. 
Try to run app in Android Simulator.

Receive following error:
Schweregrad	Code	Beschreibung	Projekt	Datei	Zeile	Unterdrückungszustand
Fehler		Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could not load assembly 'CustomRenderer, Version=, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?	CustomRenderer.Droid	C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets	974
Comment 1 Gerald Hoops 2016-08-15 13:04:33 UTC
Wrong Link. Here is the one that matches the error:

Sorry for the confusion but as all samples do not work I got it switched.
Comment 2 Paul DiPietro [MSFT] 2016-08-15 18:25:28 UTC
Setting the heap size to 1G should resolve this issue.
Comment 3 Gerald Hoops 2016-08-16 08:42:21 UTC
I confirm that it works with the 1G heap setting in the android advanced build options.