When you try and install Mono.Android in Visual Studio for the first time you may find that you're presented with an error similar to the one below: System.UnauthorizedAccessException: Access to the path 'C:\ProgramData\Mono for Android\License' is denied. at Xamarin.Components.Ide.Activation.ActivationService.GetErrorWorkflow(LicenseSyncResult[] results, Boolean ignoreSyncErrors) at Xamarin.Components.Ide.Activation.ActivationService.<GenerateFullWorkflowSequence>d__88.MoveNext() at Xamarin.Components.Ide.Activation.ActivationDialog.DisplayWorkflowStep(ActivationWorkflowStep step) at Xamarin.Components.Ide.Activation.ActivationDialog.<>c__DisplayClass13.<StartSpinnerTaskAndScheduleContinuation>b__12(Task t) If you close down VS and run it again as an Administrator it should sort the issue out. Remember activation of your Xamarin licenses doesn't actually kick off until you run the project for the first time. If you're still having activat
I was presented with this error whilst developing with Xamarin Forms For me it was simply down to copy and paste :-O. I'd created a new Xaml Page, which fully qualified was MyNameSpace.MyPage. I then copied in some Xaml which had a different name in the Xaml x:Class attribute (x:Class="NotMyNameSpace.OrPage"). I then tried to compile with our fixing the x:Class attribute and got the 'InitializeComponent does not exist' error. Once I changed the Xaml to match my actual classname (x:Class="MyNameSpace.MyPage") I was back on track and the error went away. Hope this helps. For more information have a look at forums.xamarin.com The other reason is that you may have created a Shared Xamarin Forms Project rather than a Xamarin Forms Portable project. From Craig Dunn at Xamarin (taken from Xamarin Forms Forum ) You cannot use Xaml with the Shared Project template with iOS apps (in Xamarin Studio). It's a weird combination to rem
When developing with Xamarin Forms you may get the exception below when using Xaml XamlParseException: No embeddedresources found This is a known bug and for now a work around is to save the Xaml file before running/building. Have a look at this for more info: https://bugzilla.xamarin.com/show_bug.cgi?id=22019
Comments
Post a comment