Share
Report
265We've been working with the software developer toolkit for a while now, and have developed a fully automated VSTS deployment pipeline working for unmanaged solutions which are kept in the customisations project in the Visual studio solution.
The process goes like this:
- Import customisations from CRM
- Check customisations into VSTS
- Check in triggers an automated build of the project, which creates a solution file using the solution packager
- Solution then deployed as part of the next release
However, we've not been able to come across a way to do the same for any of our managed solutions.
I think the problem comes down to the fact that when you import customisations from CRM, you have no option to select a managed solution for export.
You can amend the build script so that it builds a managed solution, but the customisations project solution is always imported as unmanaged, so even if you hack the solution file to make it managed, it will get overwritten the next time you import customisations from CRM. So the built solution file always ends up as unmanaged.
Any ideas how to resolve this?
*This post is locked for comments
All responses (
Answers (
