diff --git a/src/mono/nuget/Microsoft.NET.Runtime.WebAssembly.Sdk/Sdk/Sdk.targets.in b/src/mono/nuget/Microsoft.NET.Runtime.WebAssembly.Sdk/Sdk/Sdk.targets.in
index 9d3818cdbe0b5f..54b39b2384c41c 100644
--- a/src/mono/nuget/Microsoft.NET.Runtime.WebAssembly.Sdk/Sdk/Sdk.targets.in
+++ b/src/mono/nuget/Microsoft.NET.Runtime.WebAssembly.Sdk/Sdk/Sdk.targets.in
@@ -12,7 +12,13 @@
     <WasmEmitSymbolMap Condition="'$(UsingMicrosoftNETSdkBlazorWebAssembly)' != 'true' and '$(UsingMicrosoftNETSdkWebAssembly)' != 'true' and '$(WasmEmitSymbolMap)' == '' and '$(RunAOTCompilation)' != 'true'">true</WasmEmitSymbolMap>
   </PropertyGroup>
 
-  <Import Project="$(MSBuildThisFileDirectory)\BrowserWasmApp.props" />
+  <!-- Mono and CoreCLR each get their own set of targets. BrowserWasmApp.props (and the
+       WasmApp.Common.props it imports) is Mono-only: it seeds target lists such as
+       WasmNestedPublishAppDependsOn with targets defined in WasmApp.Common.targets, which the
+       CoreCLR path does not import. CoreCLR needs no props counterpart: RuntimeIdentifier comes
+       from the WebAssembly SDK, and TargetOS/TargetArchitecture are only consumed in-tree, where
+       eng/OSArch.props derives them from the RID. -->
+  <Import Project="$(MSBuildThisFileDirectory)\BrowserWasmApp.props" Condition="'$(UseMonoRuntime)' != 'false'" />
   <Import Project="$(MSBuildThisFileDirectory)\BrowserWasmApp.targets" Condition="'$(UseMonoRuntime)' != 'false'" />
   <Import Project="$(MSBuildThisFileDirectory)\BrowserWasmApp.CoreCLR.targets" Condition="'$(UseMonoRuntime)' == 'false'" />
 </Project>