You’re offline. This is a read only version of the page.
Hello,
I have developed a custom Dynamics CRM solution which extensively use Service Endpoints (Azure Service Bus Queues) to communicate with external services.
I would like to know the best practices to deploy that Service Endpoint on production given the Endpoint which I use for development is not the same (obviously).
The GUID should be preserved amoung different enviroments, since it is referenced by custom actions.
My question is: If I deploy the Endpoint on my managed solution and then, on Prod enviroment, re-configure it to use the Production Queue, subsequent deploys would override the configuration, right? What is the recommended way of doing it?
I tried to let the ServiceEndpoint resource on an unmanaged solution but removing it from the managed solution prevented it from being deployed cause of the lack of required components (even if the resource is already previously deployed).
Thank you!
Lucas
*This post is locked for comments
I have the same question (0)
Exactly !! try deploying the Service Endpoint in a different solution. That way, you will not have to override/change it every time you deploy your main solution. Even if you include it in your main solution, you can modify it in your production (unmanaged) and then in your subsequent managed solution deployments to Production always select "Main Customization" to not overwrite the Service Endpoint however you have to be careful what unmanaged customization you are doing on Prod in order to avoid inconsistencies.
Share
Report
All responses (
Answers (
4
