RE: Check out rights under Vista / Windows 7

> Hello BOb & Stephan,
>
> First thank you for your prompt answer.
>
> The context is: I'm providing an installation folder of my soft by
> the
> means of a SVN repository. When I upload updated installation files
> in
> the repository, the end-users just have to update their working
> copy
> in order to obtain the upgrade of the soft, as there is no need to
> go
> through a standard installation procedure alla Installshield. I
> found
> the location was proper, as it is an installation and the admin
> rights
> are respected for the update (the user must have them for
> updating).
> So it looked at another way of installing a software (It's not
> really
> a working copy from client side, in the sense that the end-user is
> not
> targetted to modify it, just a read-only access...).
>
> But I think I didn't explained properly last time: when I try to
> create an empty folder 'by hand' in the ProgramFiles folder (within
> Windows Explorer) and when I want to copy one file in this folder,
> it
> is possible as I've got the admin rights. It is just warned (pop up
> window under Vista/Win 7) that it requires admin rights, but when I
> click on 'Continue' the operation is successfully processed. This
> seems to be 'tunable' by Windows (several notification levels with
> 'user account control' - translated from French OS, not sure the
> english term is that). The same kind of warning pops up when I
> install
> new softs with standard installation procedures... But it seems
> that
> this notification, which does not appear when checking out a
> working
> copy with TSVN, locks the writing (because I suppose it is using
> standard I/O routines).
>
> I just wondered whether this lock behaviour can be managed by other
> softs (like TSVN), or if only Microsoft can handle it...
>
> Pierre

Certainly it is possible. But... TSVN is already running in process of the Explorer. So, you can't elevate an existing process. The only way to have processes within an application be able to do stuff is to separate out the code that needs to be elevated into a separate binary. IIRC this is all documented by microsoft. There are also UI guidelines like putting the shield on a button that runs a process that requires elevation.

Why don't you use click once or Installshield's update service to provide your users with updates. This would put a real install UI in front of them and Windows will request elevation if you set up your installer properly.

The other thing you could do is ship the svn.exe command line tool with your app... when you user wants to update you can run a shell command that requires elevation to run the update.

Bottom line... this is not something that needs to be changes in TSVN... it is your software that needs an updater than correctly requests elevated privileges.

Or, if you want to keep doing what your doing, DON'T install your app in program files. Install it in the user's home directory or in the root of c:\. You really should work with the Windows best practices, not against them.

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2671319

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-10-13 20:28:59 CEST