By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,467 Members | 1,594 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,467 IT Pros & Developers. It's quick & easy.

what is the best priactise for updating client

P: n/a
Hi,

I have an Client-Server based C# application to run in an intranet. Since
there are hundred of clients, what is best way to update clients?

Should client use TCP/IP socket to poll new dll files from the server? What
about the dll already loaded by client application? Should I write another
client solely for checking and updating?

Now I manully copy all files, when I did few times, it really takes time and
effort.

Thanks,
Ryan
May 17 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Wed, 17 May 2006 17:41:14 +0800, Ryan Liu wrote:
Hi,

I have an Client-Server based C# application to run in an intranet. Since
there are hundred of clients, what is best way to update clients?

Should client use TCP/IP socket to poll new dll files from the server? What
about the dll already loaded by client application? Should I write another
client solely for checking and updating?

Now I manully copy all files, when I did few times, it really takes time and
effort.


You might want to consider, or at least look at, the updater application
block from Microsoft. More info can be found at
http://msdn.microsoft.com/library/en.../updaterv2.asp
--
Tom Porterfield
May 17 '06 #2

P: n/a
you might also want to take a look at click-once deployment

May 17 '06 #3

P: n/a

If you're using VS2005, there is click-once deployment, where your
application is 'Published' to a web server, and the clients check if
they are the latest version at startup, and download the new copy if
they need to.
You will need to make sure you increment version numbers appropriately.
Paul

Ryan Liu wrote:
Hi,

I have an Client-Server based C# application to run in an intranet. Since
there are hundred of clients, what is best way to update clients?

Should client use TCP/IP socket to poll new dll files from the server? What
about the dll already loaded by client application? Should I write another
client solely for checking and updating?

Now I manully copy all files, when I did few times, it really takes time and
effort.

Thanks,
Ryan

May 17 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.