Forum Discussion
when command set Extension is deployed --ship then it doesn't work? Help:)
Hi have created a small extension that contains an ApplicationCustomizer for the topheader and one ListViewCommandSet. They work together beautifully when doing debug, but when properly deployed it doesn't show at all?
Any pointers?
They are not deployed tenant wide, but is manually installed.
"includeClientSideAssets": true,
"skipFeatureDeployment": true,
"isDomainIsolated": false,
"features": [
{
"title": "Application Extension - Deployment of custom action.",
"description": "Deploys a custom action with ClientSideComponentId association",
"id": "wwwwww",
"version": "1.0.1.0",
"assets": {
"elementManifests": [
"elements.xml",
"ClientSideInstance.xml"
]
}
}
]
trillian74 You may want to explain what you mean by "It doesn't work"
- trillian74Copper Contributor
Beau CameronFair Well it's kinda strange because when i debug the extension
gulp serve --config=quickProjectDetail
it works as i want, but when i deploy it to apps it does not surface on the site after i installed it as an app on the site. I do have an extension and a commandset in the same project, but i don't think that should mean anything.
It does not show anything in the app monitor nor the installation of the package.
Ole
- trillian74Copper Contributor
Beau Cameronfor test sake i divided them up into two separate Projects... deployed Perfect. didn't know that was a restriction.