This document discusses structuring a Universal Windows Platform (UWP) application. It outlines where to place different types of code components like views, view models, models, and repositories. It also discusses using complementary technologies like WebAPI, Entity Framework, and T4 templates. It covers consuming WebAPIs in UWP apps and validation requirements. Finally, it discusses authentication using Azure Active Directory and securing apps and services.

1. UniversalApps Development
Part 2/3
Jiri Danihelka

2. Structuring the solution
• Where did we put Views?
• Where did we put View Models?
• Where did we put Models?
• Where did we put Repositories?
• Where did we put Resources?
• Where did we put View Services?
• Where did we put Behaviors?

3. Complimentary technologies
• WebAPI
– Popular, standards-oriented service
– Built on top of ASP.Net MVC
– Lightweight transmission
• The Entity Framework
– Provider-based abstraction
• T4 templates
– Code generation templates
– Ideal for boilerpate code

4. Consuming WebAPI in Windows Runtime
• JSON.Net by NewtonSoft
• Common.Models
• The new Windows.Net.Http.HttpClient
– Fully asynchronous

5. Validation requirements
• Determine when an object is dirty
• Provide a way to revert to original
• Provide a way to mark as clean
• Allow for complex, custom validation
• Perform validation on a model & property-level
• Expose errors on a model & property-level

6. Introducing IProperty

7. Implementing Property<T> : IProperty
1
2
3
4
5

8. Introducing IModel

9. Implementing ModelBase: IModel
1
2
3
4

10. Azure active directory
• Cloud-version of the most popular enterprise authentication
directory
– Subset, fixed schema
– On-premise integration with ADFS
• Single-sign-on with third-party apps
– Salesforce.com, etc.
• Multi-factor authentication
• Application access management
• Service level agreement
• Graph query

11. Securing your application
• Not all applications have a service
• Users can authenticate against the directory
by requesting access to the graph
– https://graph.windows.net

12. Your login implementation
• Using the silent login
• Using continuation on the Phone
• Take care of the navigation backstack
• Enabling logout

13. Securing services
• Services can share a single client token
• Services can be uniquely secured

14. Module Agenda
• Storage Landscape
• SQLite
• Settings
• Blob storage
• Provisioning Strategies

15. • What is not included
– System.Data
– SQL CE
• What is included
– System.Web
– Microsoft.Web
– File System
• What is available
– SQLite
• Web Services
– WCF Services
– REST Services
– OData Services
• OneDrive
– Other providers
• Windows Azure
– SQL Database
– Table Storage
– Blob storage
Storage Landscape

16. Settings Charm
• Windows Store Apps Only
– Phone implements Settings as a Page
– Windows uses Settings Flyout
• Settings, Options, Preferences, Personalization
• Charm not required
• Use a light dismiss

17. Settings
• Adjusted Occasionally
– Not part of your applications workflow
• Depend on user preferences
– Think through defaults to minimize configuration
• Save immediately – do not use a “Save” or “Apply” button

18. Adding Settings Commands
• Prism and MvvmAppBase gives us
a convenient extension point:

19. Using the SettingsFlyout Control