Desarrollo multiplataforma con el framework .net
•Download as PPTX, PDF•
0 likes•99 views
iOS, Android, Windows, Linux, Mac, Smart TV, Web utilizando C# y el framework .Net podemos cubrir todas estas áreas de desarrollo. Vamos ha hablar de Xamarin, .Net Core, .Net Standard y como todas estas tecnologías nos habilitan el desarrollo a 360 grados compartiendo código entre los varios proyectos (modelos, business logic, data layer, communication layer, ...)
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Desarrollo multiplataforma con el framework .net
Similar to Desarrollo multiplataforma con el framework .net (20)
More from Dan Ardelean
More from Dan Ardelean (20)
Desarrollo multiplataforma con el framework .net
- 1. #GDGCochabamba Desarollo multiplataforma con el framework .NET Dan Ardelean | Microsoft MVP & Xamarin Certified Mobile Dev @danardelean | dan@mahiz.it
- 3. .NET today—reusing code Difficult to reuse skills • Need to master 3+1 base class libraries Difficult to reuse code • Need to target a fairly small common denominator Difficult to innovate • Need implementations on each platform
- 5. .NET tomorrow .NET Standard Reuse skills • Master one BCL, not a Venn diagram Reuse code • Common denominator is much bigger Faster innovation • Target .NET Standard & run anywhere
- 6. What is .NET Standard? • .NET Standard is a specification • A set of APIs that all .NET platforms have to implement .NET Standard .NET Framework .NET Core Xamarin ~ ~ HTML specification Browsers
- 7. 2.0 1.6 1.3 Versioning in .NET Standard • Higher versions incorporate all APIs from previous versions. • Projects targeting version X.Y can reference libraries & projects targeting any version between 1.0 and X.Y • Concrete .NET platforms implement a specific version of .NET Standard • From that platform you can reference libraries up to that version 1.0
- 8. .NET Standard 2.0 Has much bigger API surface • Extended to cover intersection between .NET Framework and Xamarin • Makes .NET Core 2.0 bigger as it implements .NET Standard 2.0 ~70% +20K Can reference .NET Framework libraries • Compat shim allows referencing existing .NET Framework code – without recompilation • Limited to libs that use APIs that are available for .NET Standard
- 10. What version should you target? • The higher the version, the more APIs you have • The lower the version, the more platforms support it Lower Version More Reach Higher Version More APIs
- 11. Difference to Portable Class Libraries (PCL) • PCLs were an after thought, i.e. each platform could decide which APIs to includes • No systematic approach to versioning • Computed intersection profiles • Each PCLs is targeting a specific set of platforms • Not compatible with newer platforms • Hard to understand compatibility relationships Platform 3Platform 1 Platform 2 Intersection Profiles
- 12. #GDGCochabamba
Editor's Notes
- Notes: Even if we are reusing a lot across components (especially with the open sourcing last year), the reality is that each platform has its own implementation of the base libraries. Note: .NET Framework BCL and Mono BCL are the same APIs, different implementation. .NET Core “Core Library” is a similar set of APIs, but different.
- Notes: Even if we are reusing a lot across components (especially with the open sourcing last year), the reality is that each platform has its own implementation of the base libraries. Note: .NET Framework BCL and Mono BCL are the same APIs, different implementation. .NET Core “Core Library” is a similar set of APIs, but different.
- Notes: Even if we are reusing a lot across components (especially with the open sourcing last year), the reality is that each platform has its own implementation of the base libraries. Note: .NET Framework BCL and Mono BCL are the same APIs, different implementation. .NET Core “Core Library” is a similar set of APIs, but different.
- Notes: Even if we are reusing a lot across components (especially with the open sourcing last year), the reality is that each platform has its own implementation of the base libraries. Note: .NET Framework BCL and Mono BCL are the same APIs, different implementation. .NET Core “Core Library” is a similar set of APIs, but different.