Titlebook: Cross-Platform .NET Development; Using Mono, Portable M. J. Easton,Jason King Book 2004 M.J. Easton and Jason King 2004 .NET..NET framework

originality

Developing Distributed Applications,puter without a care about the external world—a perfect example of digital agoraphobia. Nonetheless, .NET also contains a broad set of classes that makes it excellent for developing applications that have their logical intestines spread across a network, and it is this class of application that we d

Mendacious

Using Native Code,hat it investigates the converse issue of how .NET can be used to access platform-specific, native code. Although this chapter might grate against the honed sensi-bilities of this book’s more puritanical readership, the ability to call native code is an essential feature that allows .NET application

LUT

recession

Testing and Building Strategies, to dipping in and out—you should have enough knowledge to begin some serious projects. It’s now time to round it all off with a bit of best practice that can help in developing cross-platform software in a coherent and consistent manner.

coddle

Summary,t of .NET’s cross-platform aspirations is far too big to be fully covered within this tome. It’s certainly tempting to finish by mentioning the conspicuously absent material that we could’ve covered, the subsidiary topics that we might’ve mentioned, and numerous subjects that we should’ve espoused.

我不怕犧牲

Cross-Platform Pitfalls,2’s cross-platform programs is a bit of an illusion that’s generated by the simplicity of the programs themselves. After all, we don’t want you to run screaming into the sunset—perhaps by the next chapter or the end of the book, but definitely not just yet.

HAWK

Blanch

CEDE

https://doi.org/10.1007/978-90-368-1746-2Nonetheless, we’ll instead follow the wise, albeit misappropriated, words of Louis E. Boon and avoid reminiscing on the book’s shortcomings, instead opting to provide an opinionated glimpse into what the future holds for .NET as a cross-platform tool.

ANTI