Auto update of programs.

  • Thread starter Thread starter UJ
  • Start date Start date
U

UJ

Has anybody had any experience writing an auto update program that will
check the internet to see if there is a newer version of the code out there
and download it?

It doesn't seem that complicated but I just wanted to hear from people who
have done it if there are any gotchas I should watch out for.

TIA - Jeffrey.
 
I can assure you that this code is tested and that it will be in the
release.
http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx

Apps in production within MS already use this technology. I speak from
experience, it works just fine.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
 
Nick said:
I can assure you that this code is tested and that it will be in the
release.
http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx

Apps in production within MS already use this technology. I speak from
experience, it works just fine.
Click to expand...

It's no longer a safe be to /trust/ Microsoft on this stuff.

I say, stick with the tried and true.

For example, I've looked at many of the "Application Blocks" and found
installation and requirements to be restrictive and cumbersome (
requiring XP Pro in some instances ).

Even if it 'works' and is 'almost ready' I'd stay away from it because
Microsoft constantly twists and changes things before release. At that
point he would be stuck with a lot of code dependent on something that
doesn't exist.

You can write an auto updater quite easily with a little bit of code
that can call a web service and get version number. I'm writing just
such code right now. There are built in methods to get version numbers
from assemblies and calling assemblies -- just match those to an update
version on the server to see if they need to be downloaded.

Simple.
 
John Bailo said:
It's no longer a safe be to /trust/ Microsoft on this stuff.

I say, stick with the tried and true.

For example, I've looked at many of the "Application Blocks" and found
installation and requirements to be restrictive and cumbersome ( requiring
XP Pro in some instances ).

Even if it 'works' and is 'almost ready' I'd stay away from it because
Microsoft constantly twists and changes things before release. At that
point he would be stuck with a lot of code dependent on something that
doesn't exist.

You can write an auto updater quite easily with a little bit of code that
can call a web service and get version number. I'm writing just such
code right now. There are built in methods to get version numbers from
assemblies and calling assemblies -- just match those to an update version
on the server to see if they need to be downloaded.

Simple.
Click to expand...

If you weren't such a notorious member of this forum, John, I'd engage in an
actual lucid conversation about the pros and cons of "buy" vs. "build".
Unfortunately, your reputation for attempting to start fruitless arguments
rather than discussing actual points of concern precedes you by leaps and
bounds.

If you are worried about being tied to a particular interface in .Net 2.0,
then encapsulate it with a facade pattern. That way, if it changes, only
your facade changes. (Personally, I wouldn't be worrying, but worrying is
such a personal thing... feel free to spend your time on this and any of a
dozen other concerns, like how you are going to get your simple app to make
sure that the file you are updating isn't being used by another user when
you are updating it).

--- N



--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
 
Nick said:
If you weren't such a notorious member of this forum, John, I'd engage in an
actual lucid conversation about the pros and cons of "buy" vs. "build".
Unfortunately, your reputation for attempting to start fruitless arguments
rather than discussing actual points of concern precedes you by leaps and
bounds.
Click to expand...

Nice FUD Nick.

As soon as my arguments best yours, you resort to name calling.

I offered very valid technical reaons -- you hid behind some vague
'technology' that is in beta, buggy and might not meet the persons needs.

Scrape the MVP off your badge, dude...it's back to MSCE training for you.
 
Nick,

I don't see what is wrong that John, gives his opinion. He tells it directly
how he thinks it is. You can read it as; it is just rude arguing without
sense. You can read it as a warning to others and Microsoft that *he* wants
more consistency.

I keep it that he means the last.

(While I don't agree with him, VS 2005 is a product still in its developing
phase. That means for me every time evaluations of what you did and because
you do that be open to renew it until the last moment of release)

Just my thought,

Cor
 
Nick,
Unfortunately this won't work because our product runs unattended so it
needs to check the server every once in a while (much like Norton Antivirus
goes out and gets new definitions.) So I need to make this happen
automatically.

I will probably go with either a Window's Web Service to check against the
server or do something so stupid as download a 'version' file that tells me
the current version of the software and if they are different I'll download
the file.

Thanks anyway.
 
Hi Cor,

I would gladly engage with a conversation with you on this or any other
issue. It is true that beta software has risks, and that using it comes
with some concern. I suggested that the OP take a look at the beta software
to see if it would fit. I didn't suggest that it was the only possible
answer, or even that it applied to their problem... simply to take a look.

Mr. Bailo has made some good contributions with some technical merit. For
that, I credit him. In this thread, he's been OK. On other threads,
including some recent ones, he has intentionally posted 'troll threads'
where he will make an intentionally opinionated non-technical statement that
he cross-posts to the linux advocacy group. As a result, I have no desire
to engage Mr. Bailo in any kind of direct conversation, regardless of the
merit of his statements. A person that I do not know gets a basic level of
respect, that is theirs to lose. He has lost that respect.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
 
I have. It is based on MS Application Updater Block, and works with the
current version of the framework. It recommended itself as a very useful
application and is used by hundreds of users in different parts of the world.
 
Back
Top