Publish/Deploy self-contained win-x64 not working for .NET7 in 200.0.0

[SokoFromNZ]

Hi,

I've found a bug in the current version (I reckon).

I'm using Esri.ArcGISRuntime.WPF v200.0.0 in a WPF + NET7 application.

I am publishing it as self-contained win-x64.

Accoring to https://developers.arcgis.com/net/license-and-deployment/deployment/#wpf-or-winui-targeting-net-6-or... your DLLs should be copied to the <Output>\publish folder... which they are not.

In fact all the files in <BuildOut>\runtimes\win10-x64\native\ are not copied (i.e. RuntimeCoreNet200_0.dll).

Here's my csproj:

<Project Sdk="Microsoft.NET.Sdk">

	<PropertyGroup>
		<OutputType>WinExe</OutputType>
		<TargetFramework>net7.0-windows10.0.19041.0</TargetFramework>
		<Nullable>enable</Nullable>
		<ImplicitUsings>disable</ImplicitUsings>
		<UseWPF>true</UseWPF>
	</PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Esri.ArcGISRuntime.WPF" Version="200.0.0" />
  </ItemGroup>

</Project>

Please let me know if you know about this already and when it will be fixed.

I can copy those DLLs afterwards myself. But if I want to deploy/publish it as single-file I'm out of luck 😞

thx

PS: I've also attached my full Solution for reproduction purposes

[dotMorten_esri]

Make sure when you publish to set your runtime identifier to “win10-x64”.

This is a change from 100.x where the RID was “win-x64”.

Side note: v200.1 will generate a helpful build error if you use an unsupported RID so that you’ll realize this a little easier.

[SokoFromNZ]

Hi,

I would... if I could... see screenshot

[dotMorten_esri · Accepted solution]

Yeah that’s a VS bug. In your project settings add this and it should show:

<RuntimeIdentifiers>win10-x86;win10-x64;win10-arm64</RuntimeIdentifiers>

Or you can manually change it in the publish settings file.