This project is read-only.

Standalone installer

Jul 10, 2011 at 8:31 PM

I don't like ClickOnce. Can you please provide a standalone MSI installer?

Jul 12, 2011 at 12:02 AM

I'm curious what your concern with ClickOnce is.

The application is prettymuch x-copy deployable but it keeps settings and cached files in your appdata directory.  I'm not sure of anything significant that using MSI would benefit over ClickOnce.

The main reason for using ClickOnce is it provides a solution for application updates, which is especially important since Facebook tends to unexpectedly change their API behaviors.  When Fishbowl is run and not deployed through ClickOnce the user won't get automatic updates and the app may run with limited functionality as parts of the Facebook integration begin to fail.  I'd rather not make it so people who don't care about whether it's installed through ClickOnce accidentally opt-out of the app updating itself by installing it a different way.

Jul 12, 2011 at 7:02 AM

Thanks for replying. My concerns with ClickOnce are:
1.  One cannot deploy it to multiple computers. Plus it installs on per-user basis instead of per-machine basis.
2.  I have outgoing firewalls on most PCs and it blocks the installation. The firewall needs to be turned off on all of them.
3.  The user cannot download/own the installer with ClickOnce as he can with MSI. Say, tommorrow for example, you drop Windows XP support and I don't have an earlier version installed, I won't be able to obtain Fishbowl for new XP installations any more.
4.  ClickOnce hides where the application gets installed in some obscure directory in %appdata% instead of Program Files.
5.  Somewhat forced updates. You are constantly nagged to update even if you don't want to.
You can write a standalone tiny standalone updater and it will become better than ClickOnce.

May 6, 2012 at 8:58 AM

Yes. Need a FishBowl Offline Installer file. Online Installer file not good a solution.