Cross-Platform Development

6.

.NET MAUI Deep Dive

6.1.

Core Architecture

6.1.1.

.NET Runtime Integration

6.1.1.1.

Cross-Platform .NET

6.1.1.2.

Native AOT Compilation

6.1.1.3.

Garbage Collection

6.1.2.

Single Project Structure

6.1.2.1.

Multi-Targeting Framework

6.1.2.2.

Platform-Specific Resources

6.1.2.3.

Conditional Compilation

6.1.3.

Handler Architecture

6.1.3.1.

Native Control Mapping

6.1.3.2.

Custom Handler Creation

6.1.3.3.

Platform Abstraction

6.2.

Development Environment

6.2.1.

Visual Studio Setup

6.2.1.1.

Workload Installation

6.2.1.2.

Project Templates

6.2.1.3.

Debugging Configuration

6.2.2.

.NET CLI Integration

6.2.2.1.

Command-Line Tools

6.2.2.2.

Build and Deploy Commands

6.2.2.3.

Package Management

6.3.

6.3.1.

XAML Markup Language

6.3.1.1.

Declarative UI Definition

6.3.1.2.

Data Binding Syntax

6.3.1.3.

Resource Management

6.3.2.

Code-Behind Integration

6.3.2.1.

6.3.2.2.

UI Logic Implementation

6.3.2.3.

Lifecycle Management

6.3.3.

Control Library

6.3.3.1.

Layout Controls

6.3.3.2.

6.3.3.3.

Display Controls

6.3.3.4.

Navigation Controls

6.4.

Data Binding and MVVM

6.4.1.

Model-View-ViewModel Pattern

6.4.1.1.

Separation of Concerns

6.4.1.2.

Testability Benefits

6.4.1.3.

Data Flow Architecture

6.4.2.

Binding Expressions

6.4.2.1.

Property Binding

6.4.2.2.

Command Binding

6.4.2.3.

Converter Usage

6.4.3.

Observable Collections

6.4.3.1.

INotifyPropertyChanged Interface

6.4.3.2.

ObservableCollection Class

6.4.3.3.

Change Notification

6.5.

Platform Services

6.5.1.

Dependency Injection

6.5.1.1.

Service Registration

6.5.1.2.

Constructor Injection

6.5.1.3.

Service Lifetime Management

6.5.2.

Platform-Specific APIs

6.5.2.1.

Conditional Platform Code

6.5.2.2.

Platform Abstractions

6.5.2.3.

Native API Access

Previous

5. Flutter Deep Dive

Go to top

Next

7. Development Lifecycle and Best Practices