Dear all,
Now, I have deployed a window application with strong name provided.
After reading some references, I know that the binding policy and codebase
should be set in Global Assembly Cache Tool for the clients to update the
new version of dll. Now, I have some questions about that.
1. Since the binding policy and codebase should be filled in with specific
number of the new version, does it mean that I have to update for each
clients PC's binding policy and codebase once I have updated the dll in the
server.
2. Can I control the Global Assembly Cache of the clients in the server so
that I need not to update each client PC manually? (If there is 20 client
PC, should I update the dll of each PC manually?)
Actually, the main task of me is that while I have updated the window
application, the clients can update the version automatically.
Thanks a lot,
Ray

Hi,

http://msdn.microsoft.com/msdnmag/is...s/default.aspx

Ken
-------------
"Ray" <(E-Mail Removed)> wrote in message
news:O$$(E-Mail Removed)...
Dear all,
Now, I have deployed a window application with strong name provided.
After reading some references, I know that the binding policy and codebase
should be set in Global Assembly Cache Tool for the clients to update the
new version of dll. Now, I have some questions about that.
1. Since the binding policy and codebase should be filled in with specific
number of the new version, does it mean that I have to update for each
clients PC's binding policy and codebase once I have updated the dll in the
server.
2. Can I control the Global Assembly Cache of the clients in the server so
that I need not to update each client PC manually? (If there is 20 client
PC, should I update the dll of each PC manually?)
Actually, the main task of me is that while I have updated the window
application, the clients can update the version automatically.
Thanks a lot,
Ray