[Installer] Start menu user bug; Inno switch; full user support about jumplist-extender HOT 9 OPEN

NSIS is best. Consider setting up a separate VS project for editing NSIS files, 
as
well as utilizing pre/post-build events to copy program files over.

Install script needs to copy over Defaults to AppData, and set up Start Menu 
library.

Requires an uninstall script that, 1. Removes all registrations from program
shortcuts and windows; 2. De-registers all applists from appids.

SEE:
IShellLibrary - http://msdn.microsoft.com/en-us/library/dd391719%28VS.85%29.aspx
Taskbar extensions, libraries -
http://www.codeproject.com/KB/winsdk/www7.aspx?msg=3285455#2
** VIP MOST USEFUL LINK ^^^

Got a pretty good one using NSIS.

BUG: Start Menu shortcuts are NOT ERASED when uninstalling as a regular user. 
Has to
do with UAC: UAC elevates the uninstaller so the "Administrator" user is 
running it.
Therefore, all of "Administrator's" profile paths are returned, NOT "User's". 
All of
JLE's shortcuts are stored under "User's" profile.

How do I get "User's" profile under an elevated process? Big question...

ADD: Windows 7 check.

The solution may be to, upon install:

1. Put JLE in Program Files
2. Put JLE in All Users\Programs
3. Put JLE startup in CURRENT user's registry only
4. Enumerate Users\AppData for each user's appdata, if existant
5. Enumerate user's environment to set jumplists

Upon uninstall:

1. Delete JLE in All Users\Programs
2. Enumerate HKEY_USERS for each user's JLE startup
3. Enumerate Users\AppData for each user's appdata, if needed
4. Enumerate user environment to remove jumplists

Everything pans out except the user environment and jumplists. I don't know how 
to do
that easily... Maybe put a /instFinal and /uninstFinal that, when each user 
starts up
on their own, the jumplist work will be done? If I go that route, the AppData 
won't
be deleted until the jumplist work is done...

Working on switching to InnoSetup, 'cause NSIS is the bane of my existence :(

I really want to get user support for the next release. The next version should 
be a
major feature release, mainly for user support and the website, as well as 
jumplist
pack integration.

The main blocker behind user support is applying jump list changes to other 
users upon install/uninstall.

Putting program icons in All Users/using users' own AppData is tame, but the 
installer runs an app that pins/unpins shortcuts and erases jump lists. What 
happens when an administrator is trying to uninstall, and the program needs to 
run under a certain user who's unable to provide a password?