Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/fundamentals/single-project.md
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ Raw assets can then be consumed by controls, as required:
<WebView Source="index.html" />
```

At build time, raw assets are copied to your app package.
At build time, raw assets are copied to your app package. For information about disabling asset packaging, see [Disable asset file packaging](~/troubleshooting.md#disable-asset-file-packaging).

### CSS files

Expand Down
46 changes: 46 additions & 0 deletions docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,6 +183,8 @@ If you receive the error "Could not find a valid Xcode app bundle at '/Library/D
sudo xcode-select --reset
```

::: moniker range=">=net-maui-8.0"

## Diagnose issues in Blazor Hybrid apps

<xref:Microsoft.AspNetCore.Components.WebView.Maui.BlazorWebView> has built-in logging that can help you diagnose problems in your Blazor Hybrid app. There are two steps to enable this logging:
Expand All @@ -191,3 +193,47 @@ sudo xcode-select --reset
1. Configure a logger to write the log output to where you can view it.

For more information, see [Diagnosing issues in Blazor Hybrid apps](~/user-interface/controls/blazorwebview.md#diagnosing-issues).

## Disable image packaging

For troubleshooting purposes, image resource packaging can be disabled by setting the `$(EnableMauiImageProcessing)` build property to `false` in the first `<PropertyGroup>` node in your project file:

```xml
<EnableMauiImageProcessing>false</EnableMauiImageProcessing>
```

## Disable splash screen packaging

For troubleshooting purposes, splash screen resource generation can be disabled by setting the `$(EnableSplashScreenProcessing)` build property to `false` in the first `<PropertyGroup>` node in your project file:

```xml
<EnableSplashScreenProcessing>false</EnableSplashScreenProcessing>
```

## Disable font packaging

For troubleshooting purposes, font resource packaging can be disabled by setting the `$(EnableMauiFontProcessing)` build property to `false` in the first `<PropertyGroup>` node in your project file:

```xml
<EnableMauiFontProcessing>false</EnableMauiFontProcessing>
```

## Disable asset file packaging

For troubleshooting purposes, asset file resource packaging can be disabled by setting the `$(EnableMauiAssetProcessing)` build property to `false` in the first `<PropertyGroup>` node in your project file:

```xml
<EnableMauiAssetProcessing>false</EnableMauiAssetProcessing>
```

## Generate a blank splash screen

For troubleshooting purposes, a blank splash screen can be generated if you don't have a `<MauiSplashScreen>` item and you don't have a custom splash screen. This can be achieved by setting the `$(EnableBlankMauiSplashScreen)` build property to `true` in the first `<PropertyGroup>` node in your project file:

```xml
<EnableBlankMauiSplashScreen>true</EnableBlankMauiSplashScreen>
```

Generating a blank splash screen will override any custom splash screen and will cause app store rejection. However, it can be a useful approach in testing to ensure that your app UI is correct.

::: moniker-end
2 changes: 1 addition & 1 deletion docs/user-interface/fonts.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ A font can be added to your app project by dragging it into the *Resources\Fonts

Fonts can also be added to other folders of your app project. However, in this scenario their build action must be manually set to **MauiFont** in the **Properties** window.

At build time, fonts are copied to your app package.
At build time, fonts are copied to your app package. For information about disabling font packaging, see [Disable font packaging](~/troubleshooting.md#disable-font-packaging).

> [!NOTE]
> The `*` wildcard character indicates that all the files within the folder will be treated as being font files. In addition, if you want to include files from sub-folders too, then configure it using additional wildcard characters, for example, `Resources\Fonts\**\*`.
Expand Down
2 changes: 2 additions & 0 deletions docs/user-interface/images/images.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,8 @@ An image can be added to your app project by dragging it into the *Resources\Ima

To comply with Android resource naming rules, image filenames must be lowercase, start and end with a letter character, and contain only alphanumeric characters or underscores. For more information, see [App resources overview](https://developer.android.com/guide/topics/resources/providing-resources) on developer.android.com.

At build time, images can be resized to the correct resolutions for the target platform and device. The resulting images are then added to your app package. For information about disabling image packaging, see [Disable image packaging](~/troubleshooting.md#disable-image-packaging).

## Resize an image

Devices have a range of screen sizes and densities and each platform has functionality for displaying density-dependent images. The base size of an image represents the baseline density of the image, and is effectively the 1.0 scale factor for the image (the size you would typically use in your code to specify the image size) from which all other density sizes are derived. If you don't specify the base size for a bitmap image, the image isn't resized. If you don't specify a base size for a vector image, such as an SVG file, the dimensions specified in the image are used as the base size.
Expand Down
2 changes: 2 additions & 0 deletions docs/user-interface/images/splashscreen.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,8 @@ A splash screen can be added to your app project by dragging an image into the *

To comply with Android resource naming rules, splash screen files names must be lowercase, start and end with a letter character, and contain only alphanumeric characters or underscores. For more information, see [App resources overview](https://developer.android.com/guide/topics/resources/providing-resources) on developer.android.com.

At build time, the splash screen image is resized to the correct size for the target platform and device. The resized splash screen is then added to your app package. For information about disabling splash screen packaging, see [Disable splash screen packaging](~/troubleshooting.md#disable-splash-screen-packaging). For information about generating a blank splash screen, see [Generate a blank splash screen](~/troubleshooting.md#generate-a-blank-splash-screen).

## Set the base size

.NET MAUI uses your splash screen across multiple platforms and can resize it for each platform.
Expand Down
2 changes: 2 additions & 0 deletions docs/whats-new/dotnet-8.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ For information about what's new in .NET 8, see [What's new in .NET 8](/dotnet/c
- The <xref:Microsoft.Maui.Controls.TapGestureRecognizer> class gains the ability to handle secondary taps on Android. For more information, see [Recognize a tap gesture](~/fundamentals/gestures/tap.md).
- The <xref:Microsoft.Maui.Controls.PointerEventArgs> object that accompanies the pointer events raised by the <xref:Microsoft.Maui.Controls.PointerGestureRecognizer> class gains a `PlatformArgs` property of type `PlatformPointerEventArgs`. This property provides access to the platform-specific arguments for a pointer gesture event. For more information, see [Recognize a pointer gesture](~/fundamentals/gestures/pointer.md).
- The <xref:Microsoft.Maui.Controls.DragStartingEventArgs>, <xref:Microsoft.Maui.Controls.DragEventArgs>, <xref:Microsoft.Maui.Controls.DropEventArgs>, and <xref:Microsoft.Maui.Controls.DropCompletedEventArgs> objects that accompany drag and drop gesture events each gain a `PlatformArgs` property. This property provides access to the platform-specific arguments for a drag or drop event. For more information, see [Recognize a drag and drop gesture](~/fundamentals/gestures/drag-and-drop.md).
- For troubleshooting purposes, resource generation can be disabled. For more information, see [Disable image packaging](~/troubleshooting.md#disable-image-packaging), [Disable splash screen packaging](~/troubleshooting.md#disable-splash-screen-packaging), [Disable font packaging](~/troubleshooting.md#disable-font-packaging), and [Disable asset file packaging](~/troubleshooting.md#disable-asset-file-packaging).
- For troubleshooting purposes, a blank splash screen can be generated. For more information, see [Generate a blank splash screen](~/troubleshooting.md#generate-a-blank-splash-screen).

The following types or members have been deprecated:

Expand Down