Best practice regarding update.txt files - Advanced Installer Community
flycast
Posts: 24
Joined: Thu Jul 25, 2019 10:31 pm

Best practice regarding update.txt files

Have a handfull of apps for internal use only. I am building installers for these apps using Advanced Installer. I am also wanting to move to updating the apps using the updating capability. My question is about best practice on folder layouts on the webserver that holds the app installers and update.txt files.

I could have a few different folder layouts:

1) Everything in the root folder and one installer.txt file in the root folder. The installer.txt would have sections for each app.

Code: Select all

/
    MyApp1.exe
    MyApp2.exe
    MyApp3.exe
    installer.txt
2) Each installer in it's own folder with a single installer.txt in the root:

Code: Select all

/
   installer.txt
   /MyApp1
       MyApp1.exe
   /MyApp2
      MyApp2.exe
   /MyApp3
      MyApp3.exe
   
3) Each installer in it's own folder with separate installer.txt files in the installer folder:

Code: Select all

/
   /MyApp1
       MyApp1.exe
       installer.txt
   /MyApp2
      MyApp2.exe
      installer.txt
   /MyApp3
      MyApp3.exe
      installer.txt
   
I see plus and minuses to all three strategies.

What is recommended best practice?
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Best practice regarding update.txt files

Hi,

If you want to update all the applications through the same Updater without needing to specify a different config file for each application, you can use the first two folder layouts (there is almost no difference between them).

However, in order to easily configure and maintain each application's update, I would recommend the third approach where each application has its own Updater and config file.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”