In dire need of more intermediate features that requires UAC intervention

[peters]

Is this something that is planned for 1.0? Having used Shimmer only for a day two, you guys have convinced me that this is the way to go. It's incredibly simple to use, but it's lacking intermediate features such as service install/uninstall (correct me if i'm mistaken).

Though a UAC free experience is great (as a baseline) but would you consider other features that require UAC intervention as "opt-in" features?

I'd be willing to contribute the features i'm going to implement back to the project ofcourse. Otherwise i'll just fork Shimmer and stay up to date with upstream :)

[shiftkey]

but it's lacking intermediate features such as service install/uninstall (correct me if i'm mistaken).

This isn't something I've had in mind for v1 (although this discussion from someone on Twitter today is in the back of my mind).

would you consider other features that require UAC intervention as "opt-in" features?

What sort of things (aside from service install/uninstall) do you see as essential to your use cases?

[peters]

The most important ones:

• Registry changes
• Filesystem modifications (e.g writing to a protected ACL folder)

A quick fix where you could specify either in the nuspec manifest the desired elevation level required during install/uninstall or by using an attribute in IAppSetup would be awesome! ;)

[peters]

Also, is it possible to specify a custom path to the 'Releases' directory? I would like to use an UNC path where are releases are stored (per application) so i do not have to worry about keeping a backup on my local developer machine.

[shiftkey]

Boom #106

[peters]

:+1:

[anaisbetts]

A quick fix where you could specify either in the nuspec manifest the desired elevation level required during install/uninstall or by using an attribute in IAppSetup would be awesome!

Sorry, UAC is not in the cards for Shimmer 1.0. You can certainly do it yourself in your IAppSetup (and it probably wouldn't be too overly difficult to do so), but Shimmer was explicitly designed for per-user installs.

You could also consider instead of using a service (which seems easy to write, but is actually pretty hard to write correctly since you will have to IPC securely with your app), just install an app that runs at startup in the context of the user. That's way easier because your app and background app are running at the same privilege levels, you don't have to pop any UAC dialogs, and Shimmer will do most of the work for you (your IAppSetup just needs to suppress making a normal shortcut, and put it in the Startup folder instead)