Closed dazinator closed 9 years ago
This looks like it is because the build process is updating the version number in the vsix manifest with the semver spec build number which then causes the vsix not to install.
Example:
<PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011">
<Metadata>
<Identity Id="CrmAdo..844f4586-0bfb-44a2-874f-f464eb4f2ea1" Version="1.2.7+0" Language="en-US" Publisher="Darrell Tunnell" />
I will change this to use a VSIX compatible build number.
The installer does not appear to install the VSIX package for "CrmAdo". This causes issues for other VSIX packages that may require that as a dependency - like CrmAdo.DDEX