soliarchitect.blogg.se

#XAMARIN STUDIO LATEST VERSION INSTALL#
#XAMARIN STUDIO LATEST VERSION UPDATE#
#XAMARIN STUDIO LATEST VERSION MANUAL#

If it is older, click on the Updates list to download the latest version. and click on the Installed list to check that the NuGet Package Manager for Visual Studio is at least version 2.8.5.

#XAMARIN STUDIO LATEST VERSION INSTALL#

Older versions of NuGet in Visual Studio will not correctly install the Unified version of Xamarin.Forms 1.3.1. If you are using Visual Studio, ensure the latest version of the NuGet Package Manager is installed.

#XAMARIN STUDIO LATEST VERSION UPDATE#

It is recommended that you delete and re-add the Xamarin.Forms NuGet package to update to version 1.3. Update Xamarin.Forms to 1.3.1 pre-release using the NuGet Package Manager for all projects in the solution: PCL (if present), iOS, Android, and Windows Phone. These steps are explained below: 2.1 Update NuGet in all Projects

Changing the code to use the new Xamarin.Forms Application, FormsApplicationDelegate (iOS), FormsApplicationActivity (Android), and FormsApplicationPage (Windows Phone) classes.

Updating the Xamarin.Forms NuGet package in each project.

Once the iOS app has been updated to the Unified API, the rest of the solution needs to be updated to Xamarin.Forms version 1.3.1. These tips will also help identify changes that are required. Re-compile your app and refer to the Updating Existing iOS Apps instructions for additional information on changes that may be required.

#XAMARIN STUDIO LATEST VERSION MANUAL#

If you have added additional iOS native code (such as custom renderers or dependency services) you may need to perform additional manual code fixes. These steps are explained in more detail in the Unified API docs.

Update the csproj file to use the correct build targets for the Unified API.Ĭlean and Build the project to ensure there are no other errors to fix.

Change the namespace references in the code to remove the MonoTouch prefix.

Change the framework reference to Xamarin.iOS (replacing the old monotouch reference).

Change the project type to support the Unified 64-bit API.

and agree to the warning message that appears. Migration ToolĬlick on the iOS project so that it's selected, then choose Project > Migrate to Xamarin.iOS Unified API. In order for the correct assembly references to be created, we first need to update the iOS project to use the Unified API. Part of the migration requires upgrading Xamarin.Forms to version 1.3, which supports the Unified API. Update the MainPage in the Windows Phone project. Update the MainActivity in the Android project. Update the AppDelegate in the iOS project.

Install the Xamarin.Forms 1.3.1 NuGet package. Update the entire solution to Xamarin.Forms version 1.3. Update iOS native APIs as outlined in the instructions to update iOS apps (specifically in custom renderer or dependency service code). Use the migration tool to automatically update the project.

Migrate the iOS app to the Unified API using Visual Studio for Mac's build in migration tool. This means that in addition to updating the iOS project for Unified support, you'll also need to edit code in all the projects in the solution. Because Xamarin.Forms 1.3.1 is the first release that supports the Unified API, the entire solution should be updated to use the latest version at the same time as migrating the iOS app to Unified.