Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows installer #55

Open
GlassBil opened this issue Nov 11, 2013 · 15 comments
Open

Windows installer #55

GlassBil opened this issue Nov 11, 2013 · 15 comments

Comments

@GlassBil
Copy link

Thanks for forking Console2. Its resizing issues in Windows 7 was driving me mad. :)

The current build on the wiki requires you to unzip and place it where you like it on your system. It'd be really nice if there was an installer (other than chocolatey). I can write a simple Windows installer in NSIS (http://nsis.sourceforge.net) if there's interest for it.

Just let me know if anyone is interested in this and I'll get on to it.

@tborychowski
Copy link

-1

Apps like this should be portable!
If you end up creating an installable version, please leave in the portable option too.

@brsanthu
Copy link

-1

I always look for portable apps to the extent that, sometimes I don't use an app because it doesn't provide portable option. Please support portable mode even if you add installation option.

@tomByrer
Copy link

tomByrer commented Dec 1, 2013

-1

Plus, we hacker types tend to have our own folder locations, configs, etc. It would just eat up HD space & bandwidth IMHO.

@benh57
Copy link

benh57 commented Jan 30, 2014

One can always use the non-installer version. Personally i'd prefer an installer, but would like to have both options.

@sschuberth
Copy link

FYI, for example Inno Setup supports to create "installers" that basically are nothing more than self-extracting archives (via the Uninstallable option). This option could be set to "no" at install time if the uses chooses a "Portable" installation mode. If files are installed like this e.g. to an USB stick, there goes your portable version, and would also have a "real" installer.

@iljau
Copy link

iljau commented Feb 18, 2014

Nice self-extractable archive (looks like real "installer") can be easily created with NSIS using method described in: cmderdev/cmder#142

@cbucher
Copy link
Owner

cbucher commented Apr 10, 2014

Produce an installer package, doesn't mean that portable archives disappear!

@contributors The packaging must be automatic and integrated to the build process.

Personally, I prefer a "real" installer -> MSI.

@Maximus5
Copy link

Maximus5 commented May 1, 2014

May be interesting, that even my app provides both "installer" and "7z package", more than 65% of users prefer to download the installer. Even if 7z packager is on first place in downloads list...

@vicentedealencar
Copy link

+1 for chocolatey

EDIT: there already, great! but i can`t find the manual :(

@cbucher
Copy link
Owner

cbucher commented Sep 1, 2014

@vicentedealencar ConsoleZ manual? just show help (or press F1)

@jondo
Copy link

jondo commented Sep 2, 2014

+1. An installer could also ask whether the user wants shell integration (via these reg files).

@ezk84
Copy link

ezk84 commented May 30, 2015

+1

@Centril
Copy link

Centril commented Oct 6, 2015

+1, Cortana Search on Windows 10 is having issues with finding portable applications it seems.

@theyapps theyapps mentioned this issue Jul 17, 2016
@theyapps
Copy link

I have given an attempt at creating an installer project. This creates an msi and an exe, the files are still built portable and the installer is just a generated package of those same portable files.

@Adambean
Copy link

So many downvotes, not enough reasoning. The creation of an MSI package doesn't mean a portable package has to disappear.
Although 5 years old I'd like to nip in my interest for an MSI package.

The positive of an MSI installer becomes apparent in a business environment where Active Directory is prevalent. This would allow domain administrators to deploy ConsoleZ throughout all/particular workstations and keep them up to date. Whilst this is "possible" without an MSI package it becomes a bit more difficult to keep consistency.

Personally I'd also like this application to be available via the Windows Store if suitable. That'd help with keeping it up to date (without manual notifications/reminders to do so) for personal/non-domain users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests