Can’t see the doc, our company has things locked up tighter than the CIAs plans for the Kennedy assassination.
If memory is correct this example was a WinForms migration to WPF attempt that was being done for a more up to date project. In the end, this project elected to just import it directly as they were not interested in sharing a deployment.
The traditional WinForms version of this contained the ESRI nugget package content.
.\Esri.ArcGISRuntime.dll
.\Esri.ArcGISRuntime.xml
.\arcgisruntime100.X\client32 (and all files in subdirs)
.\arcgisruntime100.X\client64 (and all files in subdirs)
.\arcgisruntime100.X\resources (and all files in subdirs)
This ran for some time just without the client32 folder as we had a 64 bit, but it was added for the purpose of completeness. This is still in use today shared among a collection of WinForms applications.
I expect you are working a WPF solution and I believe the content is different but the idea is the same. I don’t know if you can trim it down the same way in that environment, but there’s no big loss just including everything. Though I do wish there was a way to safely ditch the language packs we know we won’t use (or maybe there is I never got around to trying it).