Skip to content

[coreclr] appsettings.json is Not Bundled in CoreCLR WASM #124895

@ilonatommy

Description

@ilonatommy

Reproduction:
Run Wasm.Build.Tests.AppSettingsTests (currently disabled in eng/testing/scenarios/BuildWasmAppsJobsListCLR.txt)

Error:

Collection: ["'/appsettings.json' exists 'False'", "'/appsettings.Development.json' exists 'False'", "'/appsettings.Production.json' exists 'False'"] Stack Trace: C:\Users\itomkowicz\repros\runtime2\src\mono\wasm\Wasm.Build.Tests\AppSettingsTests.cs(74,0): at Wasm.Build.Tests.AppSettingsTests.LoadAppSettingsBasedOnApplicationEnvironment(Boolean publish, String msBuildApplicationEnvironment, String queryApplicationEnvironment, String expectedApplicationEnvironment) at System.Runtime.CompilerServices.AsyncHelpers.RuntimeAsyncTask`1.DispatchContinuations()

Fix Suggestions:

CoreCLR WASM does not currently bundle appsettings.json or other configuration files by default, unlike Mono WASM. To fix, update the SDK/runtime pack or build logic to include appsettings.json in the published/bundled output for CoreCLR WASM apps.
Reference: See Mono WASM behavior for expected bundling logic.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions