Xamarin.Forms：打造跨平台C#应用覆盖iOS、Android与Windows Phone

需积分: 9 123 浏览量更新于2024-07-21 收藏 15.1MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

Chapter 1 How does Xamarin.Forms fit in? 3

Problem 2: Different development environments

Programmers today are accustomed to working in a sophisticated integrated development environ-

ment (IDE). Such IDEs exist for all three platforms, but of course they are different:

 For iOS development, Xcode on the Mac.

 For Android development, Android Studio on a variety of platforms.

 For Windows Phone development, Visual Studio on the PC.

Problem 3: Different programming interfaces

All three of these platforms are based on different operating systems with different APIs. In many cases,

the three platforms all implement similar types of user-interface objects but with different names.

For example, all three platforms have something that lets the user toggle a Boolean value:

 On the iPhone, it’s a “view” called UISwitch.

 On Android devices, it’s a “widget” called Switch.

 On Windows Phone, one possibility is a “control” called ToggleSwitchButton from the

Windows Phone Toolkit NuGet package.

Of course, the differences go far beyond the names into the programming interfaces themselves.

Problem 4: Different programming languages

Developers have some flexibility in choosing a programming language for each of these three plat-

forms, but, in general, each platform is very closely associated with a particular programming lan-

guage:

 Objective-C for the iPhone

 Java for Android devices

 C# for Windows Phone

These three languages are cousins because they are all object-oriented descendants of C, but they

have become rather distant cousins.

For these reasons, a company that wants to target multiple platforms might very well employ three

different programmer teams, each team skilled and specialized in a particular language and API.

This language problem is particularly nasty, but it’s the problem that is the most tempting to solve:

If you could use the same programming language for these three platforms, you could at least share

some code between the platforms. This shared code likely wouldn’t be involved with the user interface

because each platform has different APIs, but there might well be application code that doesn’t touch

Chapter 1 How does Xamarin.Forms fit in? 4

the user interface at all.

A single language for these three platforms would certainly be convenient. But what language

would that be?

The C# and .NET solution

A roomful of programmers would come up with a variety of answers to the question just posed, but a

good argument can be made in favor of C#. Unveiled by Microsoft in the year 2000, C# is a fairly new

programming language, at least when compared with Objective-C and Java. At first, C# seemed to be a

rather straightforward, strongly typed, imperative object-oriented language, certainly influenced by

C++ (and Java as well), but with a much cleaner syntax than C++ and none of the historical baggage.

In addition, the first version of C# had language-level support for properties and events, which turn out

to be member types that are particularly suited for programming graphical user interfaces.

But C# has continued to grow and get better over the years. The support of generics, lambda func-

tions, LINQ, and asynchronous operations has successfully elevated C# to be classified as a multipara-

digm programming language. C# code can be traditionally imperative or flavored with declarative or

functional programming paradigms.

Also exciting is the future of C#: on April 3, 2014, C# creator Anders Hejlsberg stood on a stage at

the Microsoft Build 2014 conference and clicked a button that published an open-source version of the

C# compiler, called the .NET Compiler Platform (formerly known by its code name “Roslyn”).

Since its inception, C# has been closely associated with the Microsoft .NET Framework. At the lowest

level, .NET provides an infrastructure for the C# basic data types (int, double, string, and so forth).

But the extensive .NET Framework class library provides support for many common chores encoun-

tered in many different types of programming. These include:

 Math

 Debugging

 Reflection

 Collections

 Globalization

 File I/O

 Networking

 Security

 Threading

Chapter 1 How does Xamarin.Forms fit in? 5

 Web services

 Data handling

 XML and JSON reading and writing

Here’s another big reason for C# and .NET to be regarded as a compelling cross-platform solution:

It’s not just hypothetical. It’s a reality.

Soon after Microsoft’s announcement of .NET way back in June 2000, the company Ximian (founded

by Miguel de Icaza and Nat Friedman) initiated an open-source project called Mono to create an alter-

native implementation of the C# compiler and the .NET Framework that could run on Linux.

A decade later, in 2011, the founders of Ximian (which had been acquired by Novell) founded

Xamarin, which still contributes to the open-source version of Mono but which has also adapted Mono

to form the basis of cross-platform mobile solutions.

Shortly after the open-source version of C# was published, Scott Guthrie of Microsoft announced

the formation of the .NET Foundation, which serves as a steward for open-source .NET technologies, in

which Xamarin plays a major part.

A single language for all platforms

For the first three years of its existence, Xamarin focused mainly on compiler technologies and three

basic sets of .NET libraries:

 Xamarin.Mac, which has evolved from the MonoMac project.

 Xamarin.iOS, which evolved from MonoTouch.

 Xamarin.Android, which evolved from Mono for Android or (more informally) MonoDroid.

Collectively, these libraries are known as the Xamarin platform. The libraries consist of .NET versions

of the native Mac, IOS, and Android APIs. Programmers using these libraries can write applications in

C# to target the native APIs of these three platforms, but also (as a bonus) with access to the .NET

Framework class library.

Xamarin also makes available Xamarin Studio, an integrated development environment that runs on

both the Mac and PC and lets you develop iPhone and Android applications on the Mac and Android

applications on the PC.

It is also possible to use Visual Studio with the Xamarin libraries to develop Mac, iPhone, and An-

droid applications. (However, Mac and iPhone development also requires a Mac with Xcode and

Xamarin Studio installed and connected through a local network with the PC.)

Of course, if you’re using Visual Studio, you can also target Windows Phone and other Microsoft

platforms.

Chapter 1 How does Xamarin.Forms fit in? 6

Sharing code

The advantage of targeting multiple platforms with a single programming language comes from the

ability to share code among the applications.

Before code can be shared, an application must be structured for that purpose. Particularly since the

widespread use of graphical user interfaces, programmers have understood the importance of separat-

ing application code into functional layers. Perhaps the most useful division is between user-interface

code and the underlying data models and algorithms. The popular MVC (Model-View-Controller) ap-

plication architecture formalizes this code separation into a Model (the underlying data), the View (the

visual representation of the data), and the Controller (which handles input from the user).

MVC originated in the 1980s. More recently, the MVVM (Model-View-ViewModel) architecture has

effectively modernized MVC based on modern GUIs. MVVM separates code into the Model (the under-

lying data), the View (the user interface, including visuals and input), and the ViewModel (which man-

ages data passing between the Model and the View).

When a programmer develops an application that targets multiple mobile platforms, the MVVM

architecture helps guide the developer into separating code into the platform-specific View—the code

that requires interacting with the platform APIs—and the platform-independent Model and View-

Model.

Often this platform-independent code needs to access files or the network or use collections or

threading. Normally these jobs would be considered part of an operating system API, but they are also

jobs that can make use of the .NET Framework class library, and if the class library is available on each

platform, it is effectively platform independent.

The part of the application that is platform independent can then be isolated and—in the context of

Visual Studio or Xamarin Studio—put into a separate project. This can be either a Shared Asset Project

(SAP)—which simply consists of code and other asset files accessible from other projects—or a Portable

Class Library (PCL), which encloses all the common code in a dynamic-link library (DLL) that can then

be referenced from other projects.

Whichever method is used, this common code has access to the .NET Framework class library, so it

can perform file I/O, handle globalization, access web services, decompose XML, and so forth.

This means that you can create a single Visual Studio solution that contains four C# projects to tar-

get the three major mobile platforms (all with access to a common SAP or PCL project), or you can use

Xamarin Studio to target iPhone and Android devices.

The following diagram illustrates the interrelationships between the Visual Studio or Xamarin Studio

projects, the Xamarin libraries, and the platform APIs:

剩余452页未读，继续阅读

robertyuzj

粉丝: 23
资源: 75

Xamarin.Forms：打造跨平台C#应用覆盖iOS、Android与Windows Phone

用C#进行智能手机编程开发

手机开发程序 C#

visual studio 2015

ros2 for Android

ios android

flutter required

qt for android

Visual Studio 2019

cross platform native plugins 下载

visual Studio2019

cross platform replay kit

cross-platform screen recorder kit下载

android flutter

wxWidgets 书籍

c#从入门到精通第九版

python wxpython

C# Web Services

cocos creator vue

qt android excel

s = The python language is a cross platform language." printis.findflanguage',s.index("a'")

最新资源