Hello all,
I'm looking for ideas on how to handle the following situation in a more automated fashion.
We have a production and dev/qa shipping service that is accessed by AX using a visual studio project. The visual studio project currently has an app.config that points to production (so that when deployments take place, we won't forget to change this setting). So the problem is that when we sync source to dev environments from TFS, we get the production settings. We have to remember to replace the app.config file with a version that points to a dev/qa instance of the shipping service. Another issue is that each time the aos is restarted, the app.config file gets rebuilt and therefore points to production once again.
You can reverse the roles of the previous scenario and the problem still exists.
I've toyed with the idea of having all service reference situations like this placed in a model and deployed to the usr layer via deployment scripts. I don't have this all thought out yet.
What are some things that other organizations have done to manage this issue?
*This post is locked for comments
I have the same question (0)
