enough API making the port of existing .NET Framework application code to .NET Core almost impossible • Issue with third-party library if it doesn’t implement .NET Standard 1.x
with 1.x • 70% of NuGet packages are compatible • Support for referencing .NET framework libraries and projects • .NET Core 2.0 treats all linux distros as a single OS • Removing OpenSSL on Mac and using Apple’s crypto librairies • Live testing support for .NET Core projects within Visual Studio 2017 • Visual Studio support for side-by-side .NET Core SDKs
runtime (LLVM optimization) • Hybrid mode possible • Pre-compile, optimize, obfuscate • Dynamic code generation is still here • Dynamically loading assemblies works
Mono 5.0 Support • Concurrent SGen garbage collection • Roslyn C# compiler • Ongoing convergence with .NET Class Library • .NET Core Support • Web Tooling • Publish ASP.NET Core Web Apps to Azure • Multi-Process Debugging
Player app on the phone • Pair Visual Studio and the phone via QRCode • Two mode for using it • Debug the app remotely • Live edit a screen • Streams the source code to the mobile and runs it locally
supported • “ Some” iOS storyboards features not supported • iOS XIB not supported • Limited reflection support (troubles with SQLite or JSON.NET nugets) • Some system classes cannot be overriden • Some features that require provisioning might not work (ex: HealthKit) • Problems with big projects • Problems with firewalls
signing identities and install them to the local Keychain • Create new Provisioning Profiles • Add a new signing identity to an existing profile • Provision new devices
a native library for each platform • Android => jar • Swift => framework • ObjectiveC => framework • C/C++ => native library(.a, .so ....) • Also works with UI code • Idiomatic bindings • Thoughts about embedding Xamarin Forms into native apps
Graph • Interaction through Microsoft or Azure AD account • Remote systems and remote sessions API • Discover, launch, and message to your apps on other devices
Distribute • Tables • Identity • Crashes • Analytics • Push • API first • Everything on the portal is usable through an API • A Swagger is available • No need for a Mac to build iOS • Use what you want • Integration with other tools • VSTS, Github, BitBucket • HockeyApp • Mobile Center Test Cloud • ...
known • No known release date • No possibility to add custom build tasks (annoying for resigning apps) • A lot of components that sometimes feels not correctly joined together Pros • No need for a Mac as a Build Machine • Fast build • Uses VSTS under the hood • Analytics feels promising • Team listening to feedbacks
color and HDR for Image • SVG support for Image • Context menu support everywhere • Keytips support for XAML • UI creation optimization (x:Load) • Embed UWP API within Win32 apps • and more!