We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

Yrlec
Posts: 30
Joined: Wed Jun 20, 2012 3:49 pm

Different build versions

Hi,
I am currently evaluating Advanced Installer for my company. We have a use case where want to be able to handle the following builds: development, pre-release and production. They will only differ in two ways:
  • One command-line argument specifying which build it is (this is used to determine which server environment to connect to etc.).
  • The release schedule.
For example: we want to be able to release a new version of our software to a small group of people with the pre-release version installed and once we feel that it is stable enough we want to create a production-release.
I have two questions about this:
  • Is this easy to achieve? Do we just create one setup-build for each type we want to create? I tried very quickly and I didn't see any way to change the update url between builds. Is that necessary or will the updater keep track of which build it is and ignore other releases?
  • What happens when we change a setting in one build? Does this propagate to other builds or do we have to change settings on each build? I guess what I am looking for is some type of inheritance among builds.
Thank you in advance!
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Different build versions

Hi and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer and for taking the time to evaluate it.
Is this easy to achieve? Do we just create one setup-build for each type we want to create? I tried very quickly and I didn't see any way to change the update url between builds. Is that necessary or will the updater keep track of which build it is and ignore other releases?
Here's a similar thread that discusses the implementation possibility of this scenario.
What happens when we change a setting in one build? Does this propagate to other builds or do we have to change settings on each build? I guess what I am looking for is some type of inheritance among builds.
Using multiple builds enables you to create several different packages starting from the same project. When creating a new build, by default it contains all project resources and has the default project settings. In order to customize it you have the option to exclude various resources:
- Prerequisites
- Features
- Launch Conditions
- Searches

Here are a couple of articles with more information:
Multiple Installer Builds
Multiple Build Configurations tutorial

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Yrlec
Posts: 30
Joined: Wed Jun 20, 2012 3:49 pm

Re: Different build versions

Thanks, I will try that!
Yrlec
Posts: 30
Joined: Wed Jun 20, 2012 3:49 pm

Re: Different build versions

I have now tried this and I ran into a problem. If I use the option /justcheck and supply a url (like this: updater.exe /justcheck -url=http://...) the process fails with the error message: "Invalid command-line".

I don't get that error message if I replace /justcheck with /checknow. However I need to use /justcheck because I want to find out if an update is available, so that I can shut down the app gracefully before starting the updater.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Different build versions

Hello,

This shouldn't happen. Can you please post the exact command lines you are using(altering any confidential information of course) so we can diff them and perhaps replicate the behavior? Maybe there's a typo or something else that's missing.

You could also try to set the URL location between quotes and see if the issue persists.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Different build versions

Reposting article for user Yrlec, lost due to hardware changes on our servers.

Here's the exact command lines used:
DegooUpdater /justcheck -url=http://downloads.degoo.com/Development/updates.txt

When quoting the url I get the same problem. Like this: DegooUpdater /justcheck -url="http://downloads.degoo.com/Development/updates.txt"

I get the same error message with both:
Image

I should add that the url specified doesn't exist yet. However, I don't think that's the problem because when I use the command line below it doesn't say "Invalid command line". In that case it actually complains about the response from the server.

DegooUpdater /checknow -url=http://downloads.degoo.com/Development/updates.txt

In this case I get the following error.
Image
This makes sense, since the url is invalid.
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Different build versions

Hello,

Actually after a closer look it seems you added an extra "=" sign. You can try as described in Auto Updater our user guide article and see if the error persists.

Change:

Code: Select all

... -url=http://...
to:

Code: Select all

... -url http://...
All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Yrlec
Posts: 30
Joined: Wed Jun 20, 2012 3:49 pm

Re: Different build versions

Thanks! I just did a quick test and it seems to be working now!
brad000123
Posts: 1
Joined: Mon Oct 22, 2012 5:47 am

Re: Different build versions

hello Yrlec . you try this? are you succeed ? plz tell me i want to do this also
B

Return to “Building Installers”