Can someone explain to me how to use custom installers in Software Deployment? It is especially about the fact that we want to roll out e.g. Affinity Designer. That works so far. But what happens when a new version is released? This will also change the path in the registry where we check which version is installed. If we simply create a new version in the catalog, we get a message that a package with the same name already exists. Why do I have a version field if it does not work like this.If i delete the old package from the catalog and create a new package with the new registry paths i wonder how he should remove the old version. Can someone give me some ideas on this please?