search

emuikernel / wittytwitter

Automatically exported from code.google.com/p/wittytwitter
1 stars 0 forks source link

Make a proper Installer #62

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It would be nice for it to follow in the standard install scenario.  This 
would also ask to create a desktop icon or quick launch icon and insert an 
entry into Add/Remove Programs.

New versions would prompt to uninstall the old version and install the new 
one.

Original issue reported on code.google.com by kurtbroc...@gmail.com on 8 Dec 2007 at 5:34

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
As a comment to this.  I like that there's not an installer: opting for x-copy 
deployment.  This allows for portability - haven't tried it but I'd bet Witty 
could 
run from a thumb drive, for instance.  Unless there's reason beyond icons and 
prompt 
for uninstall, though clean - I'd admit, like click-once and auto-updates I'd 
consider staying on this.  

On the other hand, and to play devil's advocate to my "vote" above: for 
developers, 
logging/instrumentation would be a cool feature.  An installer could handle 
setting 
up an eventlog source: hm...  I'm working on an extensibility feature that I'll 
present to the Witty folks, in the next few days, with a request to contribute, 
where I write to a custom eventlog source.  To this point: it's required a 
small 
utility run as Admin (on vista) to create the log source.  This, however, could 
be 
dealt with in other ways...

Portability is a big win - still like x-copy deploy!!!  

My two-cents, 

Matt

Matt Ortiz | email: matt[at]footheory[dot]com | twitter: @mortiz

Original comment by ma77or...@gmail.com on 4 Jan 2008 at 7:54

GoogleCodeExporter commented 8 years ago 
I agree with Matt, I really like the x-copy install personally. 

However, since I know a lot of people expect an installer, I'm submitting a 
simple 
install created with Inno Setup. I really like Inno Setup over MSI because it 
creates nice, lightweight installs and doesn't require uninstalling old 
versions 
when installing an upgrade. The install script paths expect it to be placed in 
the 
source root folder (\WittyTwitter\).

I'm happy to build the install for releases, it takes about 30 seconds.

Original comment by jongallo...@gmail.com on 1 Feb 2008 at 7:20

Attachments:

GoogleCodeExporter commented 8 years ago 
Added a check for .NET 3.0 to the installer.

Original comment by jongallo...@gmail.com on 1 Feb 2008 at 8:46

Attachments:

GoogleCodeExporter commented 8 years ago 
Some thoughts:

Is it possible to add an installer project to the main solution file?
What about auto-update feature?
What about a ClickOnce installation like Family.Show?

Original comment by alan...@gmail.com on 1 Feb 2008 at 11:06

GoogleCodeExporter commented 8 years ago 
I agree, ClickOnce would be best. That would require hosting the install on 
another
server, right?

The Visual Studio Installer projects have always bugged me because MSI installs 
have
some annoying problems, like requiring uninstall in order to update. There's a
workaround for it, but that's an example. So if ClickOnce isn't an option, I'd
recommend just adding the Inno Setup script to the project. The Inno Setup 
builder is
free, and it's a tiny install - about 1MB. http://www.jrsoftware.org/isdl.php

Original comment by jongallo...@gmail.com on 3 Feb 2008 at 1:41

GoogleCodeExporter commented 8 years ago 
Saw jon's update last night.  I'm release the installer into the wild as v0.1.6 
Beta 2.

Setup-Witty-0.1.6-Beta2.exe

I think the installer needs a better naming convention. Is it possible to 
change the
extention from .exe to .msi?

Original comment by alan...@gmail.com on 7 Feb 2008 at 2:23

GoogleCodeExporter commented 8 years ago 
I noticed that the installer will over-write older versions which is cool. No 
need to
uninstall older versions.

I think Witty is still lacking an auto-update feature. WIll continue looking if
ClickOnce is the answer.

Original comment by alan...@gmail.com on 7 Feb 2008 at 2:27

GoogleCodeExporter commented 8 years ago

Original comment by alan...@gmail.com on 7 Feb 2008 at 2:31

GoogleCodeExporter commented 8 years ago 
It's not possible to rename the existing installer to .msi, since it's not an 
.msi 
intaller.

Original comment by jongallo...@gmail.com on 7 Feb 2008 at 9:38

GoogleCodeExporter commented 8 years ago 
Had an idea for auto-update which doesn't require hosting outside of Google 
Code. 
The latest release is listed on 
http://code.google.com/p/wittytwitter/downloads/list, for instance the current 
release is http://wittytwitter.googlecode.com/files/Setup-Witty-0.1.6-Beta2.exe

That means that if Witty was notified of a new release, it (after confirmation 
from 
the user) download and execute the latest installer. The installer would kill 
Witty, 
install, and run the new version.

That just leaves the notification part. There are two ways that Witty could be 
notified of a new release:
1) Could check the releases available on 
http://code.google.com/p/wittytwitter/downloads/list once a day and determine 
if a 
new release is available. That could be done by naming convention, so if it's 
running 0.1.6 it wouldn't download until a newer release (major.minor.release) 
was 
available. The naming convention could also include Alpha / Beta / Release, so 
users 
could select what type of releases they wanted.
2) This solution is more "Twitter-ish" but could be error-prone - new release 
announcements could be posted via a new Twitter account, say "WittyReleases". 
Users 
wouldn't have to follow that account, Witty could just automatically check it 
at an 
interval. I think that could get into some weird issues, though.

Thoughts? There's a bit of custom code going on there, but the tradeoff is that 
it 
leverages the Google Code hosting and doesn't require an external service or 
website.

Original comment by jongallo...@gmail.com on 7 Feb 2008 at 9:53

GoogleCodeExporter commented 8 years ago 
Why not use twitter itself to announce a twitter client release? I think your
solution #2 is genius!

Original comment by alan...@gmail.com on 7 Feb 2008 at 5:54

GoogleCodeExporter commented 8 years ago 
Based on the move to ClickOnce, I'm marking this fixed. The current installer 
works 
for nightlies.

Original comment by jongallo...@gmail.com on 4 May 2008 at 5:02