- System Requirements
- Property Pages and Manifest redesign
- New Entitlements Editor
- Several improvements and bug fixes.
- Bug Fixes.
- Known Issues.
Included in this release:
In Xamarin 4.6 we are continuing working on the redesign of our Property Pages and Manifest editors adding a new editor: the Entitlements Editor.
The new editor is now a stand-alone editor. It was designed in a way it's simpler and effective and can be launched by double clicking your entitlements.plist file. It provides a user-friendly UI which can be easily browsed, keeping a familiar look and feel for editting manifests.
This release includes the following fixes:
- iOS device list simulator list does not get updated when changing iOS version to lower.(188.8.131.529)
- Fixed VS hang on Zeroconf during build host discovery.(184.108.40.2069)
- The SayGoodbye target fails when building an iOS Library.(220.127.116.119)
- MSBuild process produces high CPU usage due to XMA monitoring.(18.104.22.1689)
- Mac Agent icon doesn't update after reconnection in some scenarios.(22.214.171.1249)
- Cannot manually select the Xcode path in settings.(126.96.36.1999)
- Android Archive - Warn the user about keystore backup needed and facilitates copying it to a different location.(188.8.131.529)
- Cannot open Assets Catalogs named "Assets" in Visual Studio 2017.(184.108.40.2069)
- VS doesn't set the MinimumOSVersion key in the .plist file for a new iOS project.(220.127.116.119)
- "Linker Behavior" drop-down shows inaccurate default value of "Don't Lin" for MtouchLink property.(18.104.22.1689)
- Show Xamarin.iOS compatibility errors on the Mac Server connection dialog.(22.214.171.1249)
- User is able to drag .png files to Vector section of image assets.(126.96.36.1999)
- Supported Families and Complication Group is not disabled when Data Source Class is not selected.(188.8.131.529)
- Change connection flow to not show any dialog when auto connecting like when openning a solution.(184.108.40.2069)
- Set the correct configuration platform when a UWP project is set as startup project.(220.127.116.119)
- tvOS binding project build fails with multiple errors.(18.104.22.1689)
- Visual Studio hangs on ZeroConf in some scenarios(22.214.171.1249)
- MSBuild process produces high CPU usage due to incorrect parent process monitor on XMA.(126.96.36.199)
- The SayGoobye target fails when building an iOS library.(188.8.131.52)
- Unhandled exception on Debugging File Provider Extension app.(184.108.40.206)
- VS crashes clicking on "Add to app" while adding free app component twice.(220.127.116.11)
- Typos on iOS Icons Visual Assets editor.(18.104.22.168)
- Native Static Reference (.a) source file ends up with 0 Kb after build.(22.214.171.124)
- Typos on Android Property pages.(126.96.36.199)
- F# Android project fails to build with multiple errors.(188.8.131.52)
- System.IO.FileNotFoundException on deploying WatchOS application.(184.108.40.206)
- tvOS C# of SpriteKit Game template fails in building application..(220.127.116.11)
- Several connection reliability Mac agent fixes.(18.104.22.168)
- Android Library template includes Resource files.(22.214.171.124)
- Android project template doesn't generate mipmap icons.(126.96.36.199)
- Unable to depoly tvOS extension app[TV Services Extension] in debug mode. No tvOS simulators in device dropdown.(188.8.131.52)
- "Xamarin for Visual Studio Updates" dialog does not give the user a way to get past "This installation package could not be opened" if one of the .msi files has an incorrect MD5 checksum after it finishes downloading.(184.108.40.206)
- Visual Studio Crash trying to start an Android app without activities.(220.127.116.11)
- Sets watchOS on Default mode as default simulator.(18.104.22.168)
- Native breakpoint does not hit, with Microsoft debugger.(22.214.171.124)
Build canceled with error: Project 'project_name' requires the following components installed on your machine: ...
Building Android applications can require installing additional components. This can be needed in several cases, like if you're using a new component, NuGet Package, or if it's the first Xamarin.Forms solution you're building on a given machine.
Xamarin for Visual Studio detects the lack of those missing resources, and shows an error informing it requires to download and install them:
Double click on that error in the list to start downloading and installing the missing components.
Please keep in mind that you need to have Intellisense errors visible in the list, otherwise you won't be able to see that error.
If you try to build any project in the solution without installing the missing components, the build will be canceled. You cannot build without installing those components. Please ensure Intellisense errors are visible to be able to start installing them.
An optional way to install missing components is to build from the command-line.
Other Known issues
If you downgrade to Xamarin 4.2 or older versions after using this release, you will need to re-register your known Mac servers in the Mac Server dialog. Please use the Forget Mac option, and configure your server connection again.