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

Ideas/best practices on how to AutoUpdate software?

P: n/a
Hello:
Always wanted to do this -- but never knew how...

The goal is to write software that goes out to clients -- but I want to be able to auto-update them
when there is a later release available at the website....
Any articles that would be a good place to start?

One of the things I don't understand is how a program can stop itself to replace itself...

I have seen several articles by now -- that I think are in the right direction -- but frankly, I'm
just getting myself confused as to which one is the right type of technology to look at.

* BITS seems to be a possible way to go investigate -- but not on all platforms (still have lots of
customers on win98 to my chagrin).

* Remote dll paths in the assembly sounds also interesting. But does that use the remote path to the
dll to cache a copy and use the cache copy, or does it actually update/replace the local one? And
doesn't that cause it to connect to the server every time the dll's are loaded? In other words, 1000
clients = 1000 * loadassembly = 1000 connections to my server. And what happens if the server is
down? Would it hang their application for 30 seconds?
As you can see, I don't know what I am talking about -- hence this post out for help :-)

Nov 16 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Google: "Background Intelligent Transfer Service API"

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hello:
Always wanted to do this -- but never knew how...

The goal is to write software that goes out to clients -- but I want to be able to auto-update them when there is a later release available at the website....
Any articles that would be a good place to start?

One of the things I don't understand is how a program can stop itself to replace itself...
I have seen several articles by now -- that I think are in the right direction -- but frankly, I'm just getting myself confused as to which one is the right type of technology to look at.
* BITS seems to be a possible way to go investigate -- but not on all platforms (still have lots of customers on win98 to my chagrin).

* Remote dll paths in the assembly sounds also interesting. But does that use the remote path to the dll to cache a copy and use the cache copy, or does it actually update/replace the local one? And doesn't that cause it to connect to the server every time the dll's are loaded? In other words, 1000 clients = 1000 * loadassembly = 1000 connections to my server. And what happens if the server is down? Would it hang their application for 30 seconds?
As you can see, I don't know what I am talking about -- hence this post out for help :-)

Nov 16 '05 #2

P: n/a
Thank you Clinton.
Did come across this and held back going this direction because it is only XP -- not win98.
How is Windows AutoUpdating Win98 clients? Not BITS, since XP only, right?


"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:ep**************@tk2msftngp13.phx.gbl...
Google: "Background Intelligent Transfer Service API"

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hello:
Always wanted to do this -- but never knew how...

The goal is to write software that goes out to clients -- but I want to be

able to auto-update them
when there is a later release available at the website....
Any articles that would be a good place to start?

One of the things I don't understand is how a program can stop itself to

replace itself...

I have seen several articles by now -- that I think are in the right

direction -- but frankly, I'm
just getting myself confused as to which one is the right type of

technology to look at.

* BITS seems to be a possible way to go investigate -- but not on all

platforms (still have lots of
customers on win98 to my chagrin).

* Remote dll paths in the assembly sounds also interesting. But does that

use the remote path to the
dll to cache a copy and use the cache copy, or does it actually

update/replace the local one? And
doesn't that cause it to connect to the server every time the dll's are

loaded? In other words, 1000
clients = 1000 * loadassembly = 1000 connections to my server. And what

happens if the server is
down? Would it hang their application for 30 seconds?
As you can see, I don't know what I am talking about -- hence this post

out for help :-)



Nov 16 '05 #3

P: n/a
I'd have to assume so as Microsoft has tried to orphan Win98.
--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:ef**************@TK2MSFTNGP10.phx.gbl...
Thank you Clinton.
Did come across this and held back going this direction because it is only XP -- not win98. How is Windows AutoUpdating Win98 clients? Not BITS, since XP only, right?


"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:ep**************@tk2msftngp13.phx.gbl...
Google: "Background Intelligent Transfer Service API"

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Hello:
Always wanted to do this -- but never knew how...

The goal is to write software that goes out to clients -- but I want
to be able to auto-update them
when there is a later release available at the website....
Any articles that would be a good place to start?

One of the things I don't understand is how a program can stop itself
to replace itself...

I have seen several articles by now -- that I think are in the right

direction -- but frankly, I'm
just getting myself confused as to which one is the right type of

technology to look at.

* BITS seems to be a possible way to go investigate -- but not on all

platforms (still have lots of
customers on win98 to my chagrin).

* Remote dll paths in the assembly sounds also interesting. But does
that use the remote path to the
dll to cache a copy and use the cache copy, or does it actually

update/replace the local one? And
doesn't that cause it to connect to the server every time the dll's
are loaded? In other words, 1000
clients = 1000 * loadassembly = 1000 connections to my server. And
what happens if the server is
down? Would it hang their application for 30 seconds?
As you can see, I don't know what I am talking about -- hence this
post out for help :-)




Nov 16 '05 #4

P: n/a
Ok. I'm going to have to mull over that article as it's just an itsy bitsy level out of my reach
coding wise...so it will take time to ponder/figure out.

Thanks for your help!

How did they do it before BITS came out? Any links to old methods? Socket? Batch file to shut down
exe/service, replace, restart?

Thanks!

"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:e%****************@TK2MSFTNGP10.phx.gbl...
I'd have to assume so as Microsoft has tried to orphan Win98.
--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:ef**************@TK2MSFTNGP10.phx.gbl...
Thank you Clinton.
Did come across this and held back going this direction because it is only

XP -- not win98.
How is Windows AutoUpdating Win98 clients? Not BITS, since XP only, right?


"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:ep**************@tk2msftngp13.phx.gbl...
Google: "Background Intelligent Transfer Service API"

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
> Hello:
> Always wanted to do this -- but never knew how...
>
> The goal is to write software that goes out to clients -- but I want to be able to auto-update them
> when there is a later release available at the website....
> Any articles that would be a good place to start?
>
> One of the things I don't understand is how a program can stop itself to replace itself...
>
>
>
> I have seen several articles by now -- that I think are in the right
direction -- but frankly, I'm
> just getting myself confused as to which one is the right type of
technology to look at.
>
> * BITS seems to be a possible way to go investigate -- but not on all
platforms (still have lots of
> customers on win98 to my chagrin).
>
> * Remote dll paths in the assembly sounds also interesting. But does that use the remote path to the
> dll to cache a copy and use the cache copy, or does it actually
update/replace the local one? And
> doesn't that cause it to connect to the server every time the dll's are loaded? In other words, 1000
> clients = 1000 * loadassembly = 1000 connections to my server. And what happens if the server is
> down? Would it hang their application for 30 seconds?
>
>
> As you can see, I don't know what I am talking about -- hence this post out for help :-)
>
>
>



Nov 16 '05 #5

P: n/a
I have no idea how it was done before BITS. You should also
Google: "Wise Installer" as I recall the vendor may have some
features that help update installed applications.
--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:ez*************@TK2MSFTNGP10.phx.gbl...
Ok. I'm going to have to mull over that article as it's just an itsy bitsy level out of my reach coding wise...so it will take time to ponder/figure out.

Thanks for your help!

How did they do it before BITS came out? Any links to old methods? Socket? Batch file to shut down exe/service, replace, restart?

Thanks!

"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:e%****************@TK2MSFTNGP10.phx.gbl...
I'd have to assume so as Microsoft has tried to orphan Win98.
--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REMOVETHISTEXTmetromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
news:ef**************@TK2MSFTNGP10.phx.gbl...
Thank you Clinton.
Did come across this and held back going this direction because it is only
XP -- not win98.
How is Windows AutoUpdating Win98 clients? Not BITS, since XP only,
right?

"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message news:ep**************@tk2msftngp13.phx.gbl...
> Google: "Background Intelligent Transfer Service API"
>
> --
> <%= Clinton Gallagher, "Twice the Results -- Half the Cost"
> Architectural & e-Business Consulting -- Software Development > NET cs*********@REMOVETHISTEXTmetromilwaukee.com
> URL http://www.metromilwaukee.com/clintongallagher/
>
>
>
> "S.Sigal" <as*******@xact-solutions.removethis.com> wrote in message
> news:%2****************@TK2MSFTNGP09.phx.gbl...
> > Hello:
> > Always wanted to do this -- but never knew how...
> >
> > The goal is to write software that goes out to clients -- but I want to be
> able to auto-update them
> > when there is a later release available at the website....
> > Any articles that would be a good place to start?
> >
> > One of the things I don't understand is how a program can stop
itself to
> replace itself...
> >
> >
> >
> > I have seen several articles by now -- that I think are in the
right > direction -- but frankly, I'm
> > just getting myself confused as to which one is the right type of
> technology to look at.
> >
> > * BITS seems to be a possible way to go investigate -- but not on all > platforms (still have lots of
> > customers on win98 to my chagrin).
> >
> > * Remote dll paths in the assembly sounds also interesting. But

does that
> use the remote path to the
> > dll to cache a copy and use the cache copy, or does it actually
> update/replace the local one? And
> > doesn't that cause it to connect to the server every time the
dll's are
> loaded? In other words, 1000
> > clients = 1000 * loadassembly = 1000 connections to my server. And

what
> happens if the server is
> > down? Would it hang their application for 30 seconds?
> >
> >
> > As you can see, I don't know what I am talking about -- hence this

post
> out for help :-)
> >
> >
> >
>
>



Nov 16 '05 #6

P: n/a
You might want to have a look at the updater application block. It's flexible
and could save you lots of coding time.
<a
href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/updater.asp"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/updater.asp</a>

"S.Sigal" wrote:
Hello:
Always wanted to do this -- but never knew how...

The goal is to write software that goes out to clients -- but I want to be able to auto-update them
when there is a later release available at the website....
Any articles that would be a good place to start?

One of the things I don't understand is how a program can stop itself to replace itself...

I have seen several articles by now -- that I think are in the right direction -- but frankly, I'm
just getting myself confused as to which one is the right type of technology to look at.

* BITS seems to be a possible way to go investigate -- but not on all platforms (still have lots of
customers on win98 to my chagrin).

* Remote dll paths in the assembly sounds also interesting. But does that use the remote path to the
dll to cache a copy and use the cache copy, or does it actually update/replace the local one? And
doesn't that cause it to connect to the server every time the dll's are loaded? In other words, 1000
clients = 1000 * loadassembly = 1000 connections to my server. And what happens if the server is
down? Would it hang their application for 30 seconds?
As you can see, I don't know what I am talking about -- hence this post out for help :-)

Nov 16 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.