Please implement support for PSADT in Custom apps where you do not need to shim the files in at the publisher level. This is so important to us to really take off with Custom apps.
As an extension, Master Wrapper (part of the Master Packager bundle) is basically PSADT GUI, but adds custom detection registry keys to make detection more reliable. This (or a similar methodology) might make a consistent set of detection rules trivial, and allow custom detection to be implemented more rapidly. We have more than a few packages that don't show up in A/R Programs, which makes custom detection mandatory.
You can now upload files and folders within the portal.
PSADT packages can be leveraged within custom apps by uploading Deploy-Application.exe (v3) or Invoe-AppDeployToolkit.exe (v4) as the main 'app', with the additional content on top.
Duplicate file names within a package can cause problems with the on-prem Publisher (fixed in preview release 2.1.33.44 or above, to be released shortly). It is recommended to wait for this fix, but for the time being you can identify duplicate file names with this command, and delete them prior to upload:
Get-ChildItem <Path> -File -Recurse | Group-Object Name | Where-Object Count -gt 1
Custom detection for custom apps is now in preview: https://docs.patchmypc.com/installation-guides/patch-my-pc-cloud/administration/manage-your-company/enable-preview-features
This is the biggest roadblock to us being able to fully leverage the custom apps portal. We standardize all our app packaging with PSADT and need to be able to upload folders to use it with the Custom Apps Portal. This is doubly important because we currently cannot allow other teams access to the PMPC console installed on our ConfigMgr SUP.
+1