J
John Yung
All,
Here is my situation?
I have an application that communicates with the middle tier via the .NET
remoting. The middle tier connectivity information is store in the
application configuration file. Depending on the environment (QA, UAT, and
Production), the configuration file will be different.
Since the setting will be set by non-developers, I could not publish a
different release for each environment (nor do I want to takeup that
responsibility). Due to the fact that ClickOnce checks the hash code for
each file, ClickOnce deployment will fail because the configuation file had
changed since it is published.
One work around is to replace the hashcode each time the configuration file
is modified. How can I do that (to generate the hashcode)? Is there another
work around (like not checking the hash code for a specific file)?
Please advice!
Thanks,
John Yung
Here is my situation?
I have an application that communicates with the middle tier via the .NET
remoting. The middle tier connectivity information is store in the
application configuration file. Depending on the environment (QA, UAT, and
Production), the configuration file will be different.
Since the setting will be set by non-developers, I could not publish a
different release for each environment (nor do I want to takeup that
responsibility). Due to the fact that ClickOnce checks the hash code for
each file, ClickOnce deployment will fail because the configuation file had
changed since it is published.
One work around is to replace the hashcode each time the configuration file
is modified. How can I do that (to generate the hashcode)? Is there another
work around (like not checking the hash code for a specific file)?
Please advice!
Thanks,
John Yung