Can't even compile the empty Cross Platform Program. RRS feed

  • Question

  • User98780 posted

    Trying to get started and I'm totally stymied. I can't even get the Hello World to compile and have no idea:

    Severity Code Description Project File Line Suppression State Error MSB4018 The "XamlCTask" task failed unexpectedly. System.IO.FileNotFoundException: Could not load file or assembly 'System.IO.FileSystem.Primitives, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'System.IO.FileSystem.Primitives, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

    Server stack trace: at Mono.Cecil.ModuleDefinition.ReadModule(String fileName, ReaderParameters parameters) at Mono.Cecil.AssemblyDefinition.ReadAssembly(String fileName, ReaderParameters parameters) at Xamarin.Forms.Build.Tasks.XamlCTask.Execute(IList`1& thrownExceptions) at Xamarin.Forms.Build.Tasks.XamlTask.Execute() at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.Build.Framework.ITask.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()

    WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

    Any help would be appreciated


    Tuesday, August 14, 2018 11:51 PM


  • User98780 posted

    Updated the .NET framework to 4.7.2 and the problem stopped occurring. It was 4.7.0.x before.

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Wednesday, August 15, 2018 10:05 PM