Pass parameters to detection method script
Creating a functional detection method is by far the most important, and potentially challenging thing people have to do when they start out with the application model, when the app is not an msi.
Most of our customers do use a consistent way of registering their sccm-based installations, whether that be in registry, wmi or just in the file system.
Passing parameters like the app name, dt name, and their respective guids to the script based option in a dection method would allow one to create a uniform detection method that just "always works".
IDK how it is implemented. Environment variables are the most universal but a custom COM object would do too.
Sem Craeghs commented
For example: I'm missing now access to the version of the application in the Powershell detection rule...