gvSIG bugs #4122: Shortcut can't be run as administrator - Application: gvSIG desktop - gvSIG

gvSIG bugs #4122

Shortcut can't be run as administrator

Added by Antonio Falciano about 8 years ago. Updated almost 7 years ago.

Status:

Closed

% Done:

Priority:

Normal

Spent time:

Assignee:

Francisco Díaz Carsí

Category:

Application

Target version:

2.4.0-2821 (rev. org.gvsig.desktop-2.0.187)

Severity:

Minor

Add-on version:

gvSIG version:

2.3.0

Add-on build:

gvSIG build:

2424

Add-on resolve version:

Operative System:

Windows

Add-on resolve build:

Keywords:

Proyecto:

Has patch:

Hito:

Add-on name:

Unknown

Description

The shortcut can't be run as administrator right clicking on it, because it's actually linked to a VBScript.

gvSIG-desktop-2.3.0-launcher_AutoIt.zip (850 KB) Antonio Falciano, 08/04/2016 08:15 PM

Associated revisions

Revision 42933
Added by Joaquín del Cerro Murciano over 7 years ago

refs #4122, añadido fichero reg para windows que tras rodarlo permite ejecutar gvsig-desktop.vbs como administrador

Revision 43294
Added by Francisco Díaz Carsí almost 7 years ago

refs #4122 Fixed Shortcut can't be run as administrator

History

#1 Updated by Antonio Falciano about 8 years ago

A workaround for RC1 windows users: right-click on the gvsig-desktop.cmd file contained in the gvSIG install folder and execute it as administrator. So it will be possible to install new plugins from the Addons manager.

#2 Updated by Antonio Falciano almost 8 years ago

The gvsig-desktop.vbs can be forced to run always as administrator, but it could be very annoying for the user:

If WScript.Arguments.length=0 Then
Set objShell = CreateObject("Shell.Application")
objShell.ShellExecute "wscript.exe", Chr(34) & _
WScript.ScriptFullName & Chr(34) & " uac", "", "runas", 1
Else
Set shell = CreateObject("Wscript.Shell")
shell.CurrentDirectory = CreateObject("Scripting.FileSystemObject").GetParentFolderName(Wscript.ScriptFullName)
shell.Run "busybox sh gvSIG.sh", 0, True
End If

Instead, the best alternative I know is to compile an exe file from a simple AutoIt script (in place of the vbs script):

Run(@ComSpec & " /c busybox sh gvSIG.sh", @WorkingDir, @SW_hide)

This one lets the user decide to run gvSIG as administrator or not, just like in gvSIG 2.2-

#3 Updated by Joaquín del Cerro Murciano over 7 years ago

Estoy teniendo en cuenta varias opciones...
Una de ellas seria habilitar la ejecución de vbs como administrador desde el menú contextual.
Para ello habría que añadir al registro una clave en el momento de la instalación, lo que llevaría tocar el izpack.
No termina de convencerme, pero dejo aquí la nota por si acaso vuelvo sobre esta opción.

Adding the Run as Administrator option for .VBS and .JS files
http://www.winhelponline.com/blog/adding-the-run-as-administrator-option-for-vbs-and-js-files/

IzPack, RegistryInstallerListener / RegistryUninstallerListener
https://izpack.atlassian.net/wiki/pages/viewpage.action?pageId=491676

#4 Updated by Joaquín del Cerro Murciano over 7 years ago

Mientras decido que opción tomar... un usuario que precisase arrancar como administrador la aplicación, podría hacerlo yendo a la carpeta donde ha instalado gvSIG y ejecutando allí el "gvsig-desktop.cmd" usando el menú contextual para ejecutarlo como administrador.

#5 Updated by Joaquín del Cerro Murciano over 7 years ago

Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220)

#6 Updated by Antonio Falciano over 7 years ago

File gvSIG-desktop-2.3.0-launcher_AutoIt.zip added

Hi Joaquín,
I attach two compiled versions (x86 and x64) and the source itself of the above AutoIt script for evaluation purpose.

Minimal instructions for watchers/testers:

copy only one executable file in the gvSIG install folder in reference to the installation type (x86 or x64, i.e. 32 or 64 bits);
rename it simply as "gvsig-desktop.exe";
create a desktop shortcut of gvsig-desktop.exe;
verify that the desktop shortcut can be executed as administrator by the contextual menu correctly.

Feedbacks are very appreciated, especially those of Windows 10 users! ;-)