[wpkg-users] [Bug 171] User notification does not work on Vista

[Rainer Meier]

Hi Robin,

Robin Roevens wrote:
> Maybe it is a good idea to supply a small executable in the tools
> directory that will be used for notifying the user?
> That way you are not dependent on a Microsoft ways of notifying users,
> thus not windows-version dependent. (except for binary incompatible
> windows versions :-))
> Something in style of the current WPKGclient notification, or like
> WPKGmessage
> (http://www.gig-mbh.de/edv/software/wpkgtools/wpkg-message-english.htm)
> 
> This tool can then give current state information about the wpkg
> process, and disappear when the process is done..
> And you can then also put an option in that tool so that the user can
> press a button to let it dissapear into the systray or so, so it is not
> in the way of the working user, but the user is still aware that the
> process is still running..until that tray icon disappears. (maybe it is
> best to have an animated tray icon then). And the user can check on the
> current state by clicking on that tray icon which then displays the tool
> again..

Currently WPKG client is using this approach. In general I don't think that it
would be a good idea having wpkg.js (which is invoked by different user
credentials in different environments) invoking such a binary. WPKG is designed
to run using only built-in Windows facilities. No additional binaries or
libraries needed. The notification using "net send" was introduced years ago in
WPKG 0.x and was just kept there. It has many limitations but provides basic
notification which can be useful in some situations. It at no means useful to
block the user to do actions or to log in while WPKG is running.

I think it's the right way that WPKG client as a service tries to reach these goals:
- Implement logon delay
- Notify user while preventing user actions

We already know that especially on Windows Vista and newer we have troubles with
the logon delay feature. Including such actions into wpkg.js seems not to be a
good idea; I prefer wpkg.js to be as stable and reliable as possible and leaving
such "fancy" stuff up to tools invoking wpkg.js. In case of failure or changes
on OS/System level there is much less impact and lots of possibilities for
work-around to get the core working.

br,
Rainer