Doug Holland | Akateeminen Kirjakauppa

The book explores several strategies for sharing code with both a detailed explanation of the ‘why’ accompanied with end-to-end examples that demonstrate the ‘how.’ Where there is more than one way to approach a given problem, the trade-offs between various approaches will be discussed and illustrated in samples.

Developers are increasingly being tasked with developing apps for multiple platforms while technology books typically address each platform in isolation. This book will be the first of its kind to illustrate how code can be shared between Windows 10, Windows Phone 10, and Xbox One.[1] 

With Windows 10 developers write apps for one product family against one developer platform accessible from one store. Windows 10 represents huge opportunities for developers and using shared code reduces both the investment required to adopt the platform as well as the time to market.

The book will explore several strategies for sharing code with both a detailed explanation of the ‘why’ accompanied with end-to-end examples that demonstrate the ‘how.’ Where there is more than one way to approach a given problem, the trade-offs between various approaches will be discussed and illustrated in samples.

Key topics include:

• Application Architecture: An application exhibits an architecture whether planned or unplanned. If an application is architected well, it will lend itself naturally to code sharing. If not, architectural refactorings may be necessary and such refactorings will also be discussed within the book.
• Strategies for Code Sharing: While other strategies for code sharing may be discussed in the book, the book will largely focus on Visual Studio 2015 UAP and Universal projects, Portable Class Libraries, Windows Runtime Components, and 3) Visual Studio’s Add as Link capability.
• Portable Code: Portable Code is .NET based code that is portable across one or more target frameworks. Windows Store and Windows Phone apps are two such target frameworks.
• Shared Code: Windows and Windows Phone Runtime components are not binary-compatible, but rather are different projects built using shared code. At the time of writing Windows Phone Runtime components can only be written in C++ while Windows Runtime Components can be written in C++, C#, and VB.
• Dependency Injection: Dependency Injection or Inversion of Control (IOC) techniques are extremely useful when writing applications across Windows and Windows Phone (and likely Xbox One too). These techniques allow abstractions of platform specific capabilities to be implemented in portable or shared code. Concrete implementations of these abstractions are then implemented for each specific platform. The author used this technique in the MSDN Magazine article on shared code: http://msdn.microsoft.com/en-us/magazine/dn201744.aspx