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.
I’m working on application that does some tests on Windows Servers. Front end of application connects to small application installed on each server via WCF.
Problem with this flow is that when i make slight update to small application on server or even change WCF server signature i should re-install this application again on numerous servers.
How did you tackled such problem or would advice to ?
WCF handles most compatibility issues without complaining such as adding new parameters to a method (old clients still work, new parameters are initialized as default). Removing params also does not affect the client (extra params ignored). Other changes and how to deal with them can be found here: http://msdn.microsoft.com/en-us/library/ff384251.aspx.
For deployment, as stated in another answer click-once is a quick way to have client machines auto-update, if you prefer more of a push model, you may be able to setup msdeploy to push a build out to the other machines (provided you have access to them).
Hope this helps.