[PaulOBrien]

So you've implemented AppToDate in your application, you've seen the cool stats and all the cool benefits that come from having users on the latest version of your app, but you're not sure how to try and get as many people using it as possible?

Introducing the 'AppToDate Stub'.

The AppToDate Stub is a tiny EXE (<20k) that you can include in your CAB files to encourage people to use AppToDate. The EXE has the same icon as the full AppToDate exe, and should be installed as a shortcut with the same 'AppToDate' name, but when the user clicks it, they will be prompted 'Do you wish to download and install AppToDate?', where they can of course click yes or no. If they click yes, the application CAB downloads and installs, if they click no, the application just exits. Simple as that!

Directions for use are as follows...

• Download attached ZIP file
  
• Extract AppToDate.Stub.exe
  
• Add this EXE to your CAB file to install to \Windows\AppToDate.exe. ENSURE THE FILE IS SET TO NOT OVERWRITE EXISTING FILES!
  
• Add a shortcut to this EXE in the programs menu. ENSURE THE SHORTCUT IS SET TO NOT OVERWRITE EXISTING SHORTCUTS!
  
• You're done!

It is vitally important that you ensure the EXE and shortcut do not overwrite existing files, or you run the danger of overwriting a full version of AppToDate with the stub, which is not good!

Hope this is useful, as always, feedback welcome!

P

Attached File(s)

•  AppToDate.Stub.zip (64K)
  Number of downloads: 275

[Sponsored Links]

[chucky.egg]

I was wondering about bundling ATD with my app just last night

This might be a great solution, but how do we set the .exe and .lnk not to overwrite existing files? Is there a switch in the .inf file?

[PaulOBrien]

Hmmm, not sure, I use WinCE CAB Manager to build my CABs.

Anyone?

P

[PaulOBrien]

COPYFLG_NO_OVERWRITE looks like the answer?

References:

http://www.sundialso....uk/cabinfo.htm

Let us know if you figure it out!

P

[simonster]

Paul,

Top news, I'll include this in HelloTwitFace when I update it on Saturday night (no I don't have anything better to do - is there anything better than code?)

Si

[PaulOBrien]

Hell no!

P

[supbro]

Anyone figure out how to not overwrite when using the Visual Studio .cab creator?

[PaulOBrien]

I don't think it's exposed in VS.

An alternative i'm thinking is that you can install the stub as 'AppToDate Install' rather than 'AppToDate', then the first time ATD runs it looks for a shortcut called 'AppToDate Install' and deletes it... will work particularly well if I can get the setup dll working to launch ATD on install completion.

P

[supbro]

Paul (MVP), on Apr 21 2008, 01:47, said:

I don't think it's exposed in VS.

An alternative i'm thinking is that you can install the stub as 'AppToDate Install' rather than 'AppToDate', then the first time ATD runs it looks for a shortcut called 'AppToDate Install' and deletes it... will work particularly well if I can get the setup dll working to launch ATD on install completion.

Hmm, but then when you update my program, it will re-install "AppToDate Install"...

[PaulOBrien]

True, hadn't considered that!

Of course, it'd be deleted next time you ran ATD, but still.

I think the non-overwrite is the best way... if we can figure it out via VS!

P

[chucky.egg]

I do my INF files by hand

[simonster]

chucky.egg, on Apr 21 2008, 22:22, said:

I do my INF files by hand

Any chance you could post a working INF file, or at least the copy file section - I just can't get it to work and it's almost 2am

Ta

Si

[PaulOBrien]

I think this should work as the file description in the INF?

apptodate.lnk,,,0x00000010

I believe '0x00000010' is 'don't overwrite'?

P

[simonster]

Quote

apptodate.lnk,,,0x00000010

I believe '0x00000010' is 'don't overwrite'?

I think I missed out one "," then. I'm finding the easist way to do this is to create the cab in VS (am using 2008), then edit the INF and CabWiz it.

[chucky.egg]

That's the right flag for No Overwrite.

This is my INF, which points to a .lnk file for AppToDate.Stub.exe (because I couldn't see a way to set the No Overwrite flag on an automatically created shortcut).
Seems to work

[Version]
Signature = "$Windows NT$"
Provider = "Chucky.Egg"
CESignature = "$Windows CE$"

[CEStrings]
AppName = "Nested Tasks"
InstallDir = %CE1%\%AppName%

[Shortcuts]
%AppName%,0,"Nested Tasks.exe"

[SourceDisksNames]
1 = , "Files",,.

[SourceDisksFiles]
"Nested Tasks.exe" = 1
"Nested Tasks Settings.exe" = 1
"Nested Tasks.xml" = 1
"Nested Tasks.ico" = 1
"AppToDate.Stub.exe" = 1
"AppToDate.lnk" = 1

[Files.NestedTasks]
"Nested Tasks.exe","Nested Tasks.exe",,
"Nested Tasks Settings.exe","Nested Tasks Settings.exe",,

[Files.AppToDate]
"Nested Tasks.xml","Nested Tasks.xml",,
"Nested Tasks.ico","Nested Tasks.ico",,

[Files.Windows]
"AppToDate.Stub.exe","AppToDate.Stub.exe",,0x00000010

[Files.StartMenu]
"AppToDate.lnk","AppToDate.lnk",,0x00000010

[DestinationDirs]
Files.NestedTasks=,%InstallDir%
Files.AppToDate=,"\Application Data\AppToDate"
Files.Windows=,%CE2%
Files.StartMenu=,%CE2%"\Start Menu\Programs"
Shortcuts=,%CE2%"\Start Menu\Programs"

[DefaultInstall]
Copyfiles=Files.NestedTasks,Files.AppToDate,Files.Windows,Files.StartMenu
CEShortcuts=Shortcuts

[PaulOBrien]

Cool.

I did have one issue pointed out, and that is that if your app is installed, then apptodate is installed, then your app is uninstalled, it's going to uninstall the apptodate shortcut

Gonna see if I can set up the shortcut as 'readonly' to fix that tho!

P

[chucky.egg]

Just a thought but...

From my point of view I want more people on ATD, so that I only have to post updates to one location. Call me lazy.
Do I specifically want/need the ATD shortcut? No.

What about including the Stub in my CAB, but linking to it from my apps menu system?
That removes the issue of different apps adding/deleting the icon, still gives my users a quick way to install it, and still helps (to a lesser extent, admittedly) publicise ATD. It may actually be more popular with some users, those who dont like their devices being "hijacked" by apps they didn't specifically choose to install.

The other thing I was just thinking was why don't I just include the current ATD CAB in mine?
There is a way to trigger a CAB that is inside another CAB (I think it requires a setup.dll, not read up on it yet) so my users could be given the option during installation. ATD self-updates anyway, so even if the version changes it'll just prompt them to download the latest.


The shortcut idea is nice in some ways, and I have no issues with it, but its starting to feel like a bodge.
I don't want to be causing problems for people (all 20 of them worldwide!) who install my apps.

Just thunking out loud... Flame me if you dare!

[PaulOBrien]

You can do whatever you like!

You're under no obligation to include anything at all, and you can include as much or as little as you like. I generally would advise against packaging ATD in it's entirety tho?

P

[chucky.egg]

Oh, dont get me wrong.
I like it, and I want to use it myself. I cant see why anyone would NOT want to use it (Sorry Mark!)
And I want my apps to support it.

I just dont know what the "best" way to deliver it is.

One question:
ATM it installs to \Windows, where I expected it to go to \Program Files\ATD or something.
If I point a menu link to "\Windows\AppToDate.exe" will it always be there? - are you planning to change the install location?

And finally, how about putting logic in the Stub to check for a local copy of the full app, and then close the Stub and open the full version if it's there? (if not there prompt to download)

[chucky.egg]

Have I missed the point with the Stub?
My CAB installs it as "AppToDate.Stub.exe". Should I be installing it as "AppToDate.exe" instead?

That would make sense with the No Overwrite flag, and would mean that I can point my app to "AppToDate.exe" and expect it to be there.

[Sponsored Links]