| View previous topic :: View next topic |
| Author |
Message |
bhpianist Cheater
Reputation: 1
Joined: 17 Apr 2010 Posts: 38
|
Posted: Wed Jun 23, 2010 9:26 pm Post subject: When is a program big enough for an installer package? |
|
|
| How do you determine whether a program is big enough to use an installer package? (eg. InstallShield, etc.)
|
|
| Back to top |
|
 |
Deltron Z Expert Cheater
Reputation: 1
Joined: 14 Jun 2009 Posts: 164
|
Posted: Thu Jun 24, 2010 5:20 am Post subject: |
|
|
| Even if it's less than a mega byte you could use an installer, the question is what are the benefits? if you'd like to set up registry values and let the user change directory and some options you would probably want an installer instead of coding everything in your program and checking if this is the first time run.
|
|
| Back to top |
|
 |
atom0s Moderator
Reputation: 205
Joined: 25 Jan 2006 Posts: 8587 Location: 127.0.0.1
|
Posted: Wed Jun 30, 2010 4:40 pm Post subject: |
|
|
Typically when your project contains various extra files, folders, and such. Or if you wish to include the framework (.NET if required) with your program if a user might need it, it's nice to have built into the installer for automatically detect and install it for them.
If your project is a single file thing, it's better to just zip it up with a readme/license/etc. and just release that way.
Unless you are an actual business or company, it's not really worth building installers for very small ideas and projects.
_________________
- Retired. |
|
| Back to top |
|
 |
|