Open marranaga opened 3 years ago
When you say these names can change for each version, what Version do you mean? Builds like 20H1 20H2, or Version Patch 19042.xxxxx and 19042.yyyyyyy?
Apologies, should have been more clear. The individual application versions are built into the PackageName
. As that specific app updates overtime, the string will be slightly different. Alternatively, the DisplayName
property never changes.
I wasn't asking for clarification, just what your use case was, which you didn't answer. What I believe you are trying to do is take a JSON configuration for one OS Build and apply to a different OS Build. Is that accurate? The reason I ask is that I originally intended the JSON files to be unique for one OS Build, which does not change the Package Name, unless this is now changing because MS is releasing monthly updates on MVLS. I'm not certain on this though. So asking again for clarification on if you are using the JSON for different OS's or not so I can determine if this is a BUG or a Feature Request
Ohh, I'm sorry. Yes, I am using the same JSON for different OS versions that way we can have an automated process to update the OS each month. I've been using this practice for about a year now, and so far, everything has been working great. The only issue we've run into recently is that it's not removing the unique AppX PackageNames that aren't working.
The
PackageName
has additional information following the base name, which also includes version numbers, and can change for each version. When running these scripts via an automated method, it's difficult to remove AppX apps based off of thePackageName
.