Category Archives: Mono Framework

Stable Release: Cycle 7

We are publishing the final builds for our next major feature release, called Cycle 7, to the Stable channel.

Please check out the product release notes to see all the fixes and known issues for this release, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. The functionality for this is supported in this release.

NOTE: Visual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE: The Cycle 7 version of Xamarin.VS requires Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed. These tools can be downloaded from the Download tab of My.VisualStudio.com with a Visual Studio subscription or a Dev Essentials account.

NOTE: The Cycle 7 version of Xamarin Studio on Windows requires both Microsoft Build Tools 2013 (or Visual Studio 2013) and Microsoft Build Tools 2015 (or Visual Studio 2015) to be installed. These tools can be downloaded from the Download tab of My.VisualStudio.com with a Visual Studio subscription or a Dev Essentials account.


Known Issues

  • [Xamarin.VS]41836 – For iOS apps, breakpoints within async methods in PCL projects are not hit if the linker is enabled.
  • [Xamarin.VS/Xamarin.iOS] – Under certain conditions, downgrading from our Xamarin products in the Alpha channel to the Beta or Stable channel versions may result in the Xamarin.iOS plugin failing to load correctly.
    • Workaround – Delete the component cache  (steps here).
  • [Xamarin.VS & Xamarin.iOS] – When deploying WatchKit applications in Visual studio, the error “The file ‘bin\iPhoneSimulator\Debug\WatchKitApp1WatchKitApp.app\WatchKitApp1WatchKitApp’ does not exist” may appear.
  • [Xamarin.VS] – tvOS Applications built with the “Build ad-hoc IPA” checkbox enabled in “Debug/Release + Device” configuration will fail with the error “The ‘CopyFileToWindows’ task failed unexpectedly.”
  • [Xamarin Studio] –  41565 – “Could not load solution:” and “Load operation failed.” when attempting to open certain projects in Xamarin Studio 6.0.
    • Recommended fix – Open the problematic .csproj file in a text editor and remove the conflicting item from the <ProjectTypeGuids> element. For iOS extension projects, the most common fix is to remove the {FEACFBD2-3405-455C-9665-78FE426C6842}; item from the list.
  • [Xamarin.Android] – AOT+LLVM compiling is disabled in this release due to a crash discovered while trying to fix a compiler issue. It will be re-enabled in a future release.

Products Released 

  • GTK# 2.12.38

Previous Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – May 18th, 2016

Beta RC3 – May 24th, 2016

Stable – This Release!

Beta Release: Cycle 7 Release Candidate 3

Update (6/6) – Slightly newer builds have been pushed to the Beta channel in anticipation of our upcoming Stable release. Please see the newer version numbers noted below. 

We are publishing a new release candidate of our next major feature release, called Cycle 7. As this is a Beta build, there may be some known issues and the possibility of new issues being found during testing.

Please check out the product release notes to see all the fixes and known issues for this preview, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. The functionality to support this is supported in this release.

NOTE: Visual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE – You will need to have MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Beta channel.


Known Issues

  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Xamarin Studio] – You may be unable to run watchkit applications after selecting Appicon on the Apple Watch Notification Center.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [Xamarin.VS & Xamarin.iOS] – When deploying WatchKit applications in Visual studio, the error “The file ‘bin\iPhoneSimulator\Debug\WatchKitApp1WatchKitApp.app\WatchKitApp1WatchKitApp’ does not exist” may appear.
  • [Xamarin.VS] – tvOS Applications built with the “Build ad-hoc IPA” checkbox enabled in “Debug/Release + Device” configuration will fail with the error “The ‘CopyFileToWindows’ task failed unexpectedly.”

Products Released 


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – Mar 15th, 2016

Beta RC1 – Apr 27th, 2016

Beta RC2 – May 18th, 2016

Beta RC3 – This Release!

Stable – April/May 2016

Preview: Android N Support Preview 2

We are releasing our second preview with support and bindings for Google’s Android N SDK. Be sure to visit the Android N page and read about all the new features N support provides. If you are looking to get started right away, make sure to check out the new Android N samples and join in on the forum discussions.

Please note that depending on which platform you are targeting, you will need to download certain products for this preview to work:

  • If you are using Visual Studio, you will only need to download the Xamarin.VS linked below.
  • If you are using Xamarin Studio on a Mac machine, you will need to download the Xamarin Studio, Xamarin Android, and Mono Framework linked below.
  • If you are using Xamarin Studio on a Windows machine, you will to download the Xamarin Studio, Xamarin.VS, and GTK Installer linked below.

There is no target stable date for N support at this time, as we have to wait until Google finalizes and publishes their support before we can release ours. That being said, we will do additional N preview releases between now and the final Google release, so be sure to check back and see if newer versions become available in the coming months.

As with all our preview releases, this is not a product we officially support. If you encounter any issues, we recommend filing a bug in Bugzilla. You can also jump into the discussions on the forum thread posted below.


Known Issues 

  • [Xamarin.Studio / Xamarin.VS] – The Xamarin.Android Designer does not support rendering of the new API level (N).
  • 31002 – [Xamarin.Studio / Xamarin.VS] – Users will have to manually make sure their minimum SDK version is set to v6.0 (23) or lower, instead of v6.0.99 (24), in order to deploy to N devices and emulators.
  • 40156 – [Xamarin Android] Projects which utilize Support.v7.AppCompat may no longer compile on Windows when using the preview build tools (24 rc2). This can be worked around by using the latest stable version of build tools instead (23.0.3).

Products Released

  • Xamarin for Visual Studio 4.1.0.509 [Download]

Evolve Keynote Releases!

UPDATE – We’ve added a new build of the Xamarin Profiler that is compatible with the Cycle 7 builds noted below. 

 

As you may have heard from Miguel during the Evolve 2016 Keynote session, we’re releasing a number of new builds to our Alpha and Beta channels, with many new features available to sample right now.

 

 


WEB PREVIEW – XAMARIN WORKBOOKS / INSPECTOR


We are releasing an updated preview of the Xamarin Inspector for iOS, Android, Mac, and WPF applications. Xamarin Inspector is an interactive tool that you can use to diagnose and prototype changes in your application. The inspector can attach to a live application on any of the supported platforms.


Products Released

 

 


WEB PREVIEW – iOS SIMULATOR (FOR WINDOWS)


We are releasing our first preview of the iOS Simulator for Xamarin.VS. The remoted iOS Simulator provides you with a way to test and debug iOS apps on the simulator entirely from Visual Studio on Windows.

 

 


WEB PREVIEW – XAMARIN PROFILER


Xamarin Profiler preview 0.33 is now available for download! There have been a number of fixes since our previous preview, which have been noted below.

Please note that the Mac app bundle has been renamed (from XamarinProfiler.Mac.app to “Xamarin Profiler.app”), so the old version needs to be removed before installing this new update, so that Xamarin Studio prompts the user for the new location.


Products Released

 

 


ALPHA RELEASE – CYCLE 8  FIRST PREVIEW


Our first preview of our newest upcoming feature release (called Cycle 8) can be downloaded from the Alpha channel.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. The functionality to support this is not in this release, however it will be included in a future release of Cycle 8, and will also be published to our Stable Channel via a Service release shortly after Evolve 2016.

NOTE: Visual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 8 Xamarin Studio build noted below.

NOTE – You will need to have MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Alpha channel.


Cycle 8 Alpha Known Issues

  • [Xamarin Studio / Xamarin.VS] – Updating your Xamarin.iOS, Xamarin.Android, or Xamarin.Mac to the builds noted below without also updating your IDE will prevent the IDE from properly running license checks, which can cause adverse functionality.
  • [Xamarin Studio – Windows Only] – You must have both MS Build Tools 2013 and MS Build Tools 2015 installed on your machine for Xamarin Studio to work properly on Windows.
  • [Xamarin.iOS] – Breakpoints may not hit for WatchKit applications when the Link All option is selected.
    • Workaround – Perform a “Clean” (or Rebuild) after switching the Link all option on.
  • [Xamarin.Android] – Android.App.Instrumentation subclasses used for app launching or headless execution may not behave as expected when running on API 15 devices or lower.
    • Workaround – Change the target framework for any such project to v2.3.
  • [Xamarin.Android] – Fast deployment is not working correctly for satellite assemblies.
    • Workaround – Disable fastdev/shared runtime to ensure the local assemblies are just bundled into the APK. This does not result in these assemblies also being written into MonoAndroidIntermediateAssetsDir.
  • [Xamarin.Android] – Command line project installation via msbuild/xbuild  (as well as other targets which require a device) will now fail when multiple devices are attached.
    • Workaround – The suggested workflow is to use the ‘serial’ argument: “-s $(serial)”.

Cycle 8 Alpha Products Released 

  • GTK# 2.12.38

Upcoming Release Dates

Cycle 8 Alpha – This Release!

Cycle 8 Beta – Fall 2016

Cycle 8 Stable – Fall 2016

 

 


BETA RELEASE – CYCLE 7 RELEASE CANDIDATE


Our next major feature release, called Cycle 7, has had some Alpha and Beta previews out for awhile, but now we’re putting our first Release Candidate to the Beta Channel. We’re really close to finalizing this release, but need your help to hammer on these RCs and shake out any last issues that are hidden away.

NOTE: Since Google’s newest Android N previews now only allow linking to NDK-provided native libraries, existing apps using e.g. Mono.Data.Sqlite.dll will crash when running on Android N. The functionality to support this is not in this release, however it will be included in a future release of Cycle 7, and will also be published to our Stable Channel via a Service release shortly after Evolve 2016.

NOTE: Visual F# Tools 4.0 RTM must be installed in order for F# console project builds to work with Cycle 7 Xamarin Studio build noted below.

NOTE – You will need to have MS Build Tools 2015 installed in order to use the iOS Designer with the Xamarin.VS build published to the Beta channel.


Cycle 7 Release Candidate Known Issues

  • [Xamarin Studio / Xamarin.VS] – Updating your Xamarin.iOS, Xamarin.Android, or Xamarin.Mac to the builds noted below without also updating your IDE will prevent the IDE from properly running license checks, which can cause adverse functionality.
  • [Xamarin Studio – Windows Only] – You must have both MS Build Tools 2013 and MS Build Tools 2015 installed on your machine for Xamarin Studio to work properly on Windows.
  • [Xamarin.iOS] – Breakpoints may not hit for WatchKit applications when the Link All option is selected.
    • Workaround – Perform a “Clean” (or Rebuild) after switching the Link all option on.
  • [Xamarin.Android] – Android.App.Instrumentation subclasses used for app launching or headless execution may not behave as expected when running on API 15 devices or lower.
    • Workaround – Change the target framework for any such project to v2.3.
  • [Xamarin.Android] – Fast deployment is not working correctly for satellite assemblies.
    • Workaround – Disable fastdev/shared runtime to ensure the local assemblies are just bundled into the APK. This does not result in these assemblies also being written into MonoAndroidIntermediateAssetsDir.
  • [Xamarin.Android] – Command line project installation via msbuild/xbuild  (as well as other targets which require a device) will now fail when multiple devices are attached.
    • Workaround – The suggested workflow is to use the ‘serial’ argument: “-s $(serial)”.

 

Cycle 7 Release Candidate Products Released 

  • GTK# 2.12.38

Upcoming Release Dates

Cycle 7 Alpha – March 10th, 2016

Cycle 7 Alpha 2 – March 15th, 2016

Cycle 7 Beta – April 11th, 2106

Cycle 7 Release Candidate – This Release!

Cycle 7 – May 2016

 

Preview: Android N Support

We are releasing our first preview with support and bindings for Google’s Android N SDK. Be sure to visit the Android N page and read about all the new features N support provides. If you are looking to get started right away, make sure to check out the new Android N samples and join in on the forum discussions.

Please note that depending on which platform you are targeting, you will need to download certain products for this preview to work:

  • If you are using Visual Studio, you will only need to download the Xamarin.VS linked below.
  • If you are using Xamarin Studio on a Mac machine, you will need to download the Xamarin Studio, Xamarin Android, and Mono Framework linked below.
  • If you are using Xamarin Studio on a Windows machine, you will to download the Xamarin Studio, Xamarin.VS, and GTK Installer linked below.

There is no target stable date for N support at this time, as we have to wait until Google finalizes and publishes their support before we can release ours. That being said, we will do additional N preview releases between now and the final Google release, so be sure to check back and see if newer versions become available in the coming months.

As with all our preview releases, this is not a product we officially support. If you encounter any issues, we recommend filing a bug in Bugzilla. You can also jump into the discussions on the forum thread posted below.


Known Issues 

  • [Xamarin.Studio / Xamarin.VS] – The Xamarin.Android Designer does not support rendering of the new API level (N).
  • 31002 – [Xamarin.Studio / Xamarin.VS] – Users will have to manually make sure their minimum SDK version is set to v6.0 (23) or lower, instead of v6.0.99 (24), in order to deploy to N devices and emulators.
  • 40156 – [Xamarin Android] Projects which utilize Support.v7.AppCompat may no longer compile on Windows when using the preview build tools (24 rc2). This can be worked around by using the latest stable version of build tools instead (23.0.3).
  • 40193 – [Xamarin Android] Certain binding projects may no longer compile on Windows due to generator changes.

Products Released

  • Xamarin for Visual Studio 4.1.0.298 [Download]

Alpha Preview 2: Cycle 7

Update 1 – Bumped Xamarin.iOS from 9.8.0.58 to 9.8.0.156. This adds support for Apple iOS 9.3 / Xcode 7.3. 


We are releasing a new Alpha preview of our next major feature release, called Cycle 7. As this is an Alpha build, there are some known issues and the possibility of new issues being found during testing.

Please check out the product release notes to see all the fixes and known issues for this preview, and use the below forum threads to report and monitor issues that may occur, as well as find any potential workarounds that may exist.


Known Issues

  • [Xamarin Studio w/ F# Add-in] – Error when creating an F# Android template on Windows. This should still function correctly on Mac.
  • [Xamarin Studio] – Dragging and dropping a folder from one project to another moves the files, but does not add them to the destination project.
  • [Xamarin Studio] – Breakpoints are not hitting in Xamarin.Mac C#/F# Unified Applications.
  • [Mono Framework] – Mono 4.3 Cryptography.ProtectedData fails to decrypt data from Mono 4.2. As a result, NuGet packages will fail to restore with the error “Data unprotection failed” when a protected NuGet source is configured.
    • Workaround – In Xamarin Studio you will need to add back any NuGet package sources that use password authentication before re-attempting to restore the packages.
  • [Xamarin.VS & Xamarin.iOS] – When deploying WatchKit applications in Visual studio, the error “The file ‘bin\iPhoneSimulator\Debug\WatchKitApp1WatchKitApp.app\WatchKitApp1WatchKitApp’ does not exist” may appear.

Products Released


Upcoming Release Dates

Alpha – March 10th, 2016.

Alpha 2 – This Release!

Beta – March 2016

Stable – Late March / Early April 2016

Stable Release: Cycle 6 Service Release 2

We are releasing the Stable builds of Service Release 2 on top of  Cycle 6. Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.


Products Released


Upcoming Release Dates

Beta – March 3rd, 2016.

Stable – This Release!

Stable Release: Cycle 6 Service Release 1

We are releasing our next Service Release to Cycle 6 to the Stable channel. This is a much bigger service release, and should address a vast majority of the issues we’ve seen reported by the community after the release of Cycle 6. The issues noted below as addressed are not the only ones fixed with this release, so make sure to check out the product release notes to see all the fixes provided with this preview.

Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.


Known Issues

  • [Xamarin.VS] – Renaming UI for Asset Catalogs (AppIcon, LaunchImages, Images, Data, SpriteAlias) is not appearing correctly.
    • Workaround: You can still rename these items using the “Name” entry in the Properties window (“View -> Properties Windows”).
  • [Xamarin.iOS]38206 – Certain iOS app projects fail to copy resources to the application bundle, resulting in errors similar to “Could not find a storyboard named ‘Main’ in bundle NSBundle”. Now hotfixed in Xamarin.iOS 9.4.1.25.
  • [Xamarin.VS] – 38240 – Breakpoints in library projects fail to pause the debugger if the Visual Studio UI is set to a language other than English. Now hotfixed in Xamarin.VS 4.0.1.93.
  • [Xamarin.VS] – 38401 – “The “PackLibraryResources” task failed unexpectedly.” when an iOS library project contains any bundle resources in the root folder other than images. Now hotfixed in Xamarin.VS 4.0.1.96.
  • [Xamarin.VS]38433 – The Info.plist editor does not display any of its tabs (“iPhone Icons”, “Entitlements”, etc.) if it is opened in window that is too narrow. Now hotfixed in Xamarin.VS 4.0.1.96.

Products Released

  • Xamarin Studio 5.10.2.56
    • Release Notes
    • Forum Thread – Stable Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • 32494 – Fixed an issue where Xamarin Studio would always compile using C# 5, leading to various errors (often syntax errors) if the project included C# 6 features.
      • 35977 – Fixed an issue where Japanese characters could not be typed into the text editor.
      • 34250 – Fixed an issue where all of the menu items would become disabled after certain project operations.
  • Xamarin for Visual Studio 4.0.1.87
    • Release Notes
    • Forum Thread – Stable Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • Fixed the “iOS IPA -> Include Artwork in IPA” checkbox in the project properties so that it correctly saves changes to the value.
      • Added a candidate fix for an issue where breakpoints in class libraries were not being resolved (non-public Bug 35691).
      • 36117 – Fixed an issue where certain distribution identities and provisioning profiles did not appear in the iOS project settings.
      • Fixed an issue with WatchKit applications in Notification mode failing with “System.ArguementOutOfRangeException”.
  • Xamarin.iOS 9.4.1.24
    • Release Notes
    • Forum Thread – Stable Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • 35786 – Fixed an issue where the iOS build process could run out of file descriptors when building large projects, leading to errors such as “error : Could not strip assembly”.
      • 30698 – Fixed an issue with certain 32-bit floating point operations causing crashes on 32-bit devices.
      • 36238 – Fixed an issue with True/False status of the “iOS IPA -> Include Artwork in IPA” not showing the correct value unless the text of the .csproj file explicitly included the “IpaIncludeArtwork” property.

Upcoming Release Dates

Alpha – December 8th, 2015

Alpha (w/ iOS 9.2 & Xcode 7.2 support) – December 10th, 2015

Alpha 2 – December 18th, 2015

Alpha 3 – January 18th, 2016

Beta – January 21st, 2016

Stable – This release!

4th Preview: Xamarin Studio with Roslyn Support

We are releasing an updated preview version of Xamarin Studio with Roslyn support, which now also supports Xamarin Studio for Windows. Please make sure to check out the associated documentation and release notes.

As with all our preview releases, this is not a product we officially support. If you encounter any issues, we recommend filing a bug in Bugzilla, and also jumping into the forum thread below to learn more and share your experience with us.


Products Released

Beta Preview: Cycle 6 Service Release 1

We are releasing an updated Beta preview of our next Service Release to Cycle 6. This is a much bigger service release, and should address a vast majority of the issues we’ve seen reported by the community after the release of Cycle 6. The issues noted below as addressed are not the only ones fixed with this release, so make sure to check out the product release notes to see all the fixes provided with this preview.

Please use the below forum threads to report and monitor issues that may occur, and find any potential workarounds that may exist.


Known Issues

  • [Xamarin Studio] – Using IComponent will wipe the designer.cs file.
  • [Xamarin.VS] – Renaming UI for Asset Catalogs (AppIcon, LaunchImages, Images, Data, SpriteAlias) is not appearing correctly.
    • Workaround: You can still rename these items using the “Name” entry in the Properties window (“View -> Properties Windows”).

Products Released

  • Xamarin Studio 5.10.2.55
    • Release Notes
    • Forum Thread – Beta Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • 32494 – Fixed an issue where Xamarin Studio would always compile using C# 5, leading to various errors (often syntax errors) if the project included C# 6 features.
      • 35977 – Fixed an issue where Japanese characters could not be typed into the text editor.
      • 34250 – Fixed an issue where all of the menu items would become disabled after certain project operations.
  • Xamarin for Visual Studio 4.0.1.81
    • Release Notes
    • Forum Thread –Beta Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • Fixed the “iOS IPA -> Include Artwork in IPA” checkbox in the project properties so that it correctly saves changes to the value.
      • Added a candidate fix for an issue where breakpoints in class libraries were not being resolved (non-public Bug 35691).
      • 36117 – Fixed an issue where certain distribution identities and provisioning profiles did not appear in the iOS project settings.
      • Fixed an issue with WatchKit applications in Notification mode failing with “System.ArguementOutOfRangeException”.
  • Xamarin.iOS 9.4.1.24
    • Release Notes
    • Forum Thread –Beta Release: Xamarin 4, Cycle 6 – Service Release 1
    • Key Issues Addressed:
      • 35786 – Fixed an issue where the iOS build process could run out of file descriptors when building large projects, leading to errors such as “error : Could not strip assembly”.
      • 30698 – Fixed an issue with certain 32-bit floating point operations causing crashes on 32-bit devices.
      • 36238 – Fixed an issue with True/False status of the “iOS IPA -> Include Artwork in IPA” not showing the correct value unless the text of the .csproj file explicitly included the “IpaIncludeArtwork” property.

Upcoming Release Dates

Alpha – December 8th, 2015

Alpha (w/ iOS 9.2 & Xcode 7.2 support) – December 10th, 2015

Alpha 2 – December 18th, 2015

Alpha 3 – January 18th, 2016

Beta – This release!

Stable – Late January 2016