use vbscript code in Autoit code

[Briandr]

Hi,

Can this small piece of vbscriot code be easily integrated into an existing AutoIT? Are there any examples of vbscript code converted into AutoIT code on the forum?

Const CSIDL_COMMON_PROGRAMS = &H17
Const CSIDL_PROGRAMS = &H2
Const CSIDL_STARTMENU = &HB
Set objShell = CreateObject("Shell.Application")
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objCurrentUserStartFolder = objShell.NameSpace (CSIDL_STARTMENU)
strCurrentUserStartFolderPath = objCurrentUserStartFolder.Self.Path
Set objAllUsersProgramsFolder = objShell.NameSpace(CSIDL_COMMON_PROGRAMS)
strAllUsersProgramsPath = objAllUsersProgramsFolder.Self.Path


If objFSO.FileExists(strCurrentUserStartFolderPath & "\Programs\Accessories\Windows Explorer.lnk") Then
Set objFolder = objShell.Namespace(strCurrentUserStartFolderPath & "\Programs\Accessories")
Set objFolderItem = objFolder.ParseName("Windows Explorer.lnk")
Set colVerbs = objFolderItem.Verbs
For Each objVerb in colVerbs
If Replace(objVerb.name, "&", "") = "Unpin from Taskbar" Then objVerb.DoIt
Next
End If

Thanks

Edited October 10, 2014 by Briandr

[Danyfirex]

ObjCreate()

Saludos

[JLogan3o13]

VBScript translates pretty easily, something like this:

Const $CSIDL_COMMON_PROGRAMS = "&H17"
Const $CSIDL_PROGRAMS = "&H2"
Const $CSIDL_STARTMENU = "&HB"

$oShell = ObjCreate("Shell.Application")
$oFSO = ObjCreate("Scripting.FileSystemObject")
$oCurrentUserStartFolder = $oShell.NameSpace($CSIDL_STARTMENU)
$sCurrentUserStartFolderPath = $oCurrentUserStartFolder.Self.Path
$oAllUsersProgramsFolder = $oShell.NameSpace($CSIDL_COMMON_PROGRAMS)
$sAllUsersProgramsPath = $oAllUsersProgramsFolder.Self.Path


    If $oFSO.FileExists($sCurrentUserStartFolderPath & "\Programs\Accessories\Windows Explorer.lnk") Then
        $oFolder = $oShell.Namespace($sCurrentUserStartFolderPath & "\Programs\Accessories")
        $oFolderItem = $oFolder.ParseName("Windows Explorer.lnk")

        $aVerbs = $oFolderItem.Verbs

            For $verb in $aVerbs
                $sVerb = StringReplace($verb.name, "&", "")
                    If $sVerb = "Unpin from Taskbar" Then $verb.DoIt
            Next
    EndIf

But is there a reason why you want to just unpin it instead of deleting it?

#include <Array.au3>
#include <File.au3>

$Folder = @AppDataDir & "\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar"
Local $aArray = _FileListToArray($Folder, "*.lnk", Default, True)

    For $sFile In $aArray
        If StringInStr($sFile, "Windows Explorer") Then
            FileDelete($sFile)
        EndIf
    Next

[MikahS]

converter: >link

[guinness]

converter: >link

This is 9 years old!

[MikahS]

This is 9 years old!

 

Time for me to get my eyes checked.

[guinness]

It might work, but considering the language has changed tenfold, I kind of highly doubt it.

[MikahS]

I kind of highly doubt it.

[Briandr]

Thanks to all have responded! No particular reason for unpinning vs deleting. I hope AutoIT overtakes VB in popularity, maybe it already has. That would be nice. Easier to work with or so it seems

[guinness]

Last time I heard VBScript was deprecated and PowerShell was its successor.

[BrewManNH]

There are 2 functions in that link that don't work, _ArrayCreate and _Iif, both having been removed/replaced, but easy enough to recreate. The convertor isn't 100% accurate anyways, for example it doesn't handle comments that aren't at the start of a line.

[JLogan3o13]

VBScript has been dead for a long time, though I admit I still look it up for reference sometimes. It is far easier to convert than PowerShell, what with all the embedded cmdlets

[TXTechie]

VBScript is still heavily used by Microsoft in MDT & WAIK solutions for Windows deployments, among others things.

[mLipok]

Thanks to VBScript, I'am able to qucik learn how to use new ActiveX object::
http://www.debenu.com/products/development/debenu-pdf-library/help/samples/
http://www.example-code.com/vbscript/default.asp

[Briandr]

Hi JLogan3o13,

When I ran the code you converted from vbscript to AutoIT, if did not work. When I ran it as a vbscript it did work. My next step would be to make this a total separate AutoIT script and not incorporate it as part of another AutoIT script, which I did.

Any ideas?

Thanks

[JLogan3o13]

The sample I provided was not meant to provide you with a fully functioning script, but an example of how vbscript converts to AutoIt.

As far as "it doesn't work", that doesn't help us much You need to add some error checking to your script so you can figure out at what point it is failing. Take a look at @error in the help file. The link to SetError shows a decent example

[Briandr]

I am still messing around with getting error checking working on this (new to Autoit), but I read your first reply and if it is easier I just assume delete the lnk. Only thing is I need to delete the lnk for all users, not just current users. When I get an error I'll paste it back.