Building Microsoft ASP.NET Applications for Mobile Devices, Second Edition [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Building Microsoft ASP.NET Applications for Mobile Devices, Second Edition [Electronic resources] - نسخه متنی

Andy Wigley; Peter Roxburgh

نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
تنظیمات قلم


اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
افزودن یادداشت
افزودن یادداشت جدید

Chapter 1, Chapter 2, and Chapter 3 primarily with you in mind; they introduce ASP.NET and Visual Studio .NET and walk you through the development of some mobile Web applications. Chapter 3 explains the essential information you'll need to understand to work with mobile Web Forms.

The second audience is those who already have experience working with the .NET Framework and Visual Studio .NET. If you've used ASP.NET before, you'll want to skim the first three chapters to get acquainted with the Mobile Internet Designer but then dive straight into Chapter 4 to begin working with the mobile controls.

Regardless of your background, you need to be familiar with object-oriented programming. The .NET Framework and everything built on it is completely object-oriented. ASP.NET Mobile Controls are classes, just like everything else in ASP.NET, and you need to understand about classes, methods, properties, and inheritance to make full use of the mobile controls and the .NET Framework.

Perhaps surprisingly, you don't need to be familiar with HyperText Markup Language (HTML) or Wireless Markup Language (WML). More important is familiarity with a programming language such as Microsoft Visual Basic or Microsoft Visual C#. We want to stress that you're writing object-oriented programs that just happen to output markup. It's quite possible to write very sophisticated ASP.NET Mobile Controls applications without ever having to dirty your hands with device-specific markup. Later on, some familiarity with HTML, WML, or XHTML can be useful if you want to customize your application for specific handheld devices. One of the things you can do with the Templates feature is send "raw" markup directly to the device. Advanced developers who want to develop their own controls must, of course, be completely familiar with the markup languages the devices use.

All the code examples in this book are written in C#, the programming language Microsoft developed concurrently with the .NET Framework. Our hope is that Visual Basic developers won't feel alienated by this focus on C#. In fact, C# code and Visual Basic code are structurally very similar, and apart from the obvious language syntax differences, the C# samples should be very readable to a Visual Basic .NET developer. On the Web site for this book, you'll find all the sample code from this book, with versions in C# and Visual Basic .NET. The only exceptions to this are the custom control examples in Chapter 21 and Chapter 22. These are only in C#, not because you can't use Visual Basic (or any other language the .NET Framework supports), but because we didn't have time to write the code!

/ 145