| Previous | Next |
| STATUS_SXS_IDENTITIES_DIFFERENT | STATUS_SXS_FILE_NOT_PART_OF_ASSEMBLY |
STATUS_SXS_ASSEMBLY_IS_NOT_A_DEPLOYMENT
An assembly is being used where a deployment-form assembly is required
STATUS_SXS_ASSEMBLY_IS_NOT_A_DEPLOYMENT distinguishes the role of an assembly from the validity of its XML. A manifest can describe an assembly and still not satisfy an operation that expects a deployment-form assembly and its required membership or deployment metadata.
Keep application manifests, assembly manifests and deployment inputs separate during diagnosis. Their schemas overlap around assemblyIdentity, but their locations, permitted elements and intended role differ. Treating one as a generic substitute for another can create a valid-looking document that still cannot be used by the requested operation.
What to inspect
- Identify the API or installer action that requested deployment semantics and record the input manifest type.
- Check whether the artifact is an application manifest, a private assembly manifest or a shared-store assembly manifest.
- Verify that all required members and identities were produced by the intended packaging/deployment step.
References
Looking for a different code? Search another status or error code.