Review any build warnings and test your application thoroughly to catch potential issues after updating. This can affect custom P/Invoke invocations and native code linked in your application. Moving from 32-bit to 64-bit may uncover a number of issues in your application, as it changes the size and alignment of data structures. Select the x86_64 setting for 64-bit builds. To verify your project’s settings, open the Project > Options menu and navigate to the Mac Build > Supported architectures setting.
Xamarin.Mac Unified projects have support for building 64-bit binaries, but some existing and migrated projects may be building 32-bit instead. More information can be found in the migration documentation. There were a number of API corrections made in Unified, and changes to your code may be required. The menu will not be visible if your application has already been migrated to Xamarin.Mac Unified (references ).Īfter the automated migration wizard has finished, build your project to determine if additional changes are required. Next, start the Migration Wizard from the Project > Migrate to Xamarin.Mac Unified API menu. Existing warnings may be pointing towards future issues and should be fixed prior to migration. Visual Studio for Mac includes a migration wizard that will help automate many of the mechanical changes that are needed to update your Mac application.
Older projects that are still using Xamarin.Mac Classic or MonoMac will need to be migrated to Xamarin.Mac Unified to support 64-bit. The most noteworthy update includes migrating your project to 64-bit. If your Mac application is not 64-bit, we strongly recommend taking action to avoid compromises in the next version of macOS. Last June, Apple announced that upcoming macOS releases would only support 32-bit applications “with compromises”.
0 kommentar(er)
