Re: WebUpdate

• Previous message: Steven Burn: "Re: WebUpdate"
• In reply to: Steven Burn: "Re: WebUpdate"
• Next in thread: Steven Burn: "Re: WebUpdate"
• Reply: Steven Burn: "Re: WebUpdate"
• Messages sorted by: [ date ] [ thread ]

Date: Mon, 3 Jan 2005 15:28:40 -0600

Is this how most update programs handle these sorts of things? I mean, if I
include a new OCX within my SETUP, does that mean I need to write another
EXE just so it can be called from my UPDATE program to register the required
files?

I suppose I'm just looking at this from the perspective of:

User1 installs version 1.01 of program.
User2 installs version 1.02 of program. New OCX #1 in this version.
User3 installs version 1.03 of program. Only EXE changed.
User4 installs version 1.04 of program. New DLL #1 and OCX #2 in this
version.
User5 installs version 1.05 of program. Only EXE changed.
User6 installs version 1.06 of program. Only EXE changed.

Now User1 does a webupdate and we download version 1.05 to his PC. Well, he
needs to have OCX #1 and OCX #2 installed, in addition to DLL #1 and new
EXE.

How do I keep all this straight?

User5 later checks for updates and finds there is version 1.06... which
means he only needs to download the EXE.

Seems to me I should just repackage my entire setup and publish that to a
webserver.

Every time there is an update, the application redownloads the entire SETUP
and reruns. This way all users have everything and all dependencies are
met?

I guess the only downside to this approach is download time and size of
update. If I'm including MDAC in SETUP, it could take a while each time.

Does this make sense?

"Steven Burn" <somewhere@in-time.invalid> wrote in message
news:%23HZA2fd8EHA.3840@tk2msftngp13.phx.gbl...
> Air code........
>
> Public Function RegisterFile(sFile As String, valOpt As Long)
> Select Case valOpt
> Case 1 '// Register
> Shell "regsvr32 " & Chr$(34) & sFile & Chr$(34)
> Case 2 '// Register silently
> Shell "regsvr32 /s " & Chr$(34) & sFile & Chr$(34)
> Case 3 '// Un-Register
> Shell "regsvr32 /u " & Chr$(34) & sFile & Chr$(34)
> Case 3 '// Un-Register silently
> Shell "regsvr32 /u /s " & Chr$(34) & sFile & Chr$(34)
> End Select
> End Function
>
> Tested on my 98SE/2K Pro/XP Pro machines and works perfectly (for me
> atleast).
>
> --
>
> Regards
>
> Steven Burn
> Ur I.T. Mate Group
> www.it-mate.co.uk
>
> Keeping it FREE!
> "DavidM" <spam@spam.net> wrote in message
> news:#bZrRLd8EHA.3840@tk2msftngp13.phx.gbl...
>> Yes, but then what? How would I register?
>>
>>
>>
>> "Steven Burn" <somewhere@in-time.invalid> wrote in message
>> news:%23Gwseeb8EHA.2568@TK2MSFTNGP10.phx.gbl...
>> > In the case of new components/dependancies, you could simply do a
>> > fileexists
>> > on them (and if exists = true, check their version against the new
> version
>> > (if applicable).
>> >
>> > --
>> >
>> > Regards
>> >
>> > Steven Burn
>> > Ur I.T. Mate Group
>> > www.it-mate.co.uk
>> >
>> > Keeping it FREE!
>> >
>> > "DavidM" <spam@spam.net> wrote in message
>> > news:u$bpSWb8EHA.2572@tk2msftngp13.phx.gbl...
>> >> All this sounds great.
>> >>
>> >> I guess my only big concern with any of these methods or trying to
>> >> rollout
>> >> my own solution would be how to handle other dependency objects. For
>> >> example, what if on my next release of the update, I include a new
>> >> control
>> >> or third party control. Sure, I can download the OCX or DLL. But how
>> > would
>> >> the update know that he needed to register?
>> >>
>> >> It almost sounds like my best option is to simply redownload any
> updated
>> >> SETUP.EXE that may be on the website and re-run SETUP each time there
> is
>> > an
>> >> update. At least this would install everything that is required for
> the
>> >> application.
>> >>
>> >> Opinions?
>> >>
>> >>
>> >> "Gaurav - http://www.gauravcreations.com"
>> >> <gauravcreations@hotmail.com>
>> >> wrote in message
>> > news:25483870-5FA0-4AEF-8FA7-0E34DDC0EC61@microsoft.com...
>> >> >u can try the following
>> >> >
>> >> > create a text file say version.txt on the server and make your
>> > application
>> >> > read tht file
>> >> > Set httpreqversion = New WinHttpRequest
>> >> > httpreqversion.Open "GET", "htt://yourpage/version.txt", True
>> >> > httpreqversion.Send
>> >> > httpreqversion.WaitForResponse (20)
>> >> > source = httpreqversion.ResponseText 'string which will store teh
>> >> > response
>> >> >
>> >> > compare the response i.e version number with the one stored on the
>> >> > local
>> >> > PC
>> >> > and prompt for an update or auto update if the versions do not
>> >> > match.
>> >> >
>> >> > --
>> >> > Gaurav Creations
>> >> > "DavidM" wrote:
>> >> >
>> >> >> Are there any other VB coders that have coded for checking the web
> and
>> >> >> doing
>> >> >> a webupdate if there is a newer version?
>> >> >>
>> >> >> Do you have any pointers?
>> >> >>
>> >> >> Best Practices to use?
>> >> >>
>> >> >> Should the update program be separate program or part of my main
>> >> >> application?
>> >> >>
>> >> >> Should I rely on IE for HTTP/FTP functionality or should I use a
> third
>> >> >> party
>> >> >> control like Mabry's FTP (which I have)?
>> >> >>
>> >> >> If I use Inno as my installer, should I have the webupdate
> re-download
>> >> >> the
>> >> >> installer for the version of my application or simply redownload
>> >> >> the
>> >> >> files
>> >> >> that changed?
>> >> >>
>> >> >> If I do use Inno, how do I check to see if application is currently
>> >> >> running
>> >> >> before continuing?
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >
>> >
>>
>>
>
>

• Previous message: Steven Burn: "Re: WebUpdate"
• In reply to: Steven Burn: "Re: WebUpdate"
• Next in thread: Steven Burn: "Re: WebUpdate"
• Reply: Steven Burn: "Re: WebUpdate"
• Messages sorted by: [ date ] [ thread ]