Download to read offline
![How the DependencyService Works ? There are three parts to a DependencyService implementation: Interface - An Interface in the shared code that defines the functionality that requires platform-specific code. Registration - An implementation of the Interface in each platform- specific application project, along with an assembly attribute that 'registers' the class so that the DependencyService can create instances of it. [assembly:Dependency(typeof(‘className’))] Location - calling DependencyService.Get<>() in shared code to get a platform-specific instance of the Interface at run time, thereby allowing the shared code to access the underlying platform.](https://image.slidesharecdn.com/xamarinforms-150323075621-conversion-gate01/75/Your-first-application-with-Xamarin-Forms-8-2048.jpg)
Uploaded byДимитър Иванов
Your first application with Xamarin.Forms
The presentation provides an overview of Xamarin and Xamarin.Forms, including its history and a simple demo application. It covers the Model-View-ViewModel (MVVM) pattern and explains the implementation of the DependencyService with its components: interface, registration, and location. The speaker, Dimitar Ivanov, also shares personal links to connect and learn more.
Your first application with Xamarin.Forms
- 1.
- 2. Before we start Forgeteverything
- 3.
- 4. What’s included inthis presentation Short overview of Xamarin History / How they started Simple application with Xamarin.Forms 8 ball application Xamarin XAML and Intelisense Implement in our application the mvvm model (WPF) Using dependency services across Android/iOS
- 5.
- 6.
- 7.
- 8. How the DependencyServiceWorks ? There are three parts to a DependencyService implementation: Interface - An Interface in the shared code that defines the functionality that requires platform-specific code. Registration - An implementation of the Interface in each platform- specific application project, along with an assembly attribute that 'registers' the class so that the DependencyService can create instances of it. [assembly:Dependency(typeof(‘className’))] Location - calling DependencyService.Get<>() in shared code to get a platform-specific instance of the Interface at run time, thereby allowing the shared code to access the underlying platform.
- 9.
- 10. About me Facebook-> https://www.facebook.com/profile.php?id=100000558502123 LinkedIn -> https://www.linkedin.com/profile/view?id=331112897 Blog -> http://firmwareninja.blogspot.com/
Editor's Notes
- #10 responses[0] = "It is certain."; responses[1] = "It is decidedly so."; responses[2] = "Yes definitely."; responses[3] = "You may rely on it."; responses[4] = "As I see it yes."; responses[5] = "Most likely."; responses[6] = "Outlook good."; responses[7] = "Yes"; responses[8] = "Signs point to yes."; responses[9] = "Reply hazy try again."; responses[10] = "Ask again later."; responses[11] = "Better not tell you now."; responses[12] = "Cannot predict now."; responses[13] = "Concentrate and ask again."; responses[14] = "Don't count on it."; responses[15] = "My reply is no."; responses[16] = "My sources say no."; responses[17] = "Outlook not so good."; responses[18] = "Very doubtful."; responses[19] = "No.";