What if the URL for the production environment is different from the one for the development environment?
Do we have any best practices to handle the situation that the Web Adapter's URL for the production environment is different from the one for the development environment?
Replacing all the URLs in the Web Adapter's properties and all the match rules suffice? Or, do we have any simpler approach to achieve it such as parameterizing the URL?
The thing that comes to my mind is to weaken the URL match rules to meet both development and production environments, though we still need to replace Web Adapter's StartPage property manually. Any ideas?
When you deploy the solution it will create the DEFAULT .manifest and .openspan deployment files and will create additional .manifest and .openspan files for each configuration file (ex PROD and TEST) using the 'Name' of the configuration file.
So for the example it will automatically create.
DEFAULT: SOLUTION.manifest and SOLUTION.openspan
PROD Config: SOLUTION-PROD.manifest and SOLUTION-PROD.openspan
TEST Config: SOLUTION-TEST.manifest and SOLUTION-TEST.manifest