Manifest identities are unique per machine, and compromise the identity name, version and culture. Moreover, a given application manifest cannot be referenced by more than one deployment manifest. If this rule is violated, only the first deployment to be installed will succeed. This can cause problems in multi-environment settings, where the same entry point assembly may be deployed into several environments (e.g. moving a deployment version from Test to QA to Production).
The application manifest name is arbitrary (it need not equal the entry point assembly name), therefore to resolve this, the inferred application manifest identity should include, at a minimum, in priority order:
Identity name (advanced setting, infrequently set)
Product name (likely to include environment in multi-environment settings)
(to be incorporated into existing inference strategy)
Manifest identities are unique per machine, and compromise the identity name, version and culture. Moreover, a given application manifest cannot be referenced by more than one deployment manifest. If this rule is violated, only the first deployment to be installed will succeed. This can cause problems in multi-environment settings, where the same entry point assembly may be deployed into several environments (e.g. moving a deployment version from Test to QA to Production).
The application manifest name is arbitrary (it need not equal the entry point assembly name), therefore to resolve this, the inferred application manifest identity should include, at a minimum, in priority order:
(to be incorporated into existing inference strategy)