Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We’ve just added a dedicated test server for our Silverlight applications. We are deploying full copies of all our apps and services onto the test server. The issue we have is that we need to manually update ServiceReference.ClientConfig when we deploy, to point to the appropriate server (ie. test or live).
I’m sure this is a common issue. What is the “best practice” solution?
I usually create a Configuration folder in my SL web project, containing a ServiceReferences.ClientConfig for each location I intend to publish the application to (ServiceReferences.ClientConfig.dev, ServiceReferences.ClientConfig.test, ServiceReferences.ClientConfig.prod).
Then I create a solution configuration for each environment (dev, test, prod) and set the SL app build event to:
Before publishing, I just need to select the configuration, build and publish