Enforcing Dependencies in WinBuilder Scripts External links Options

[WetHat]

WinBuilder allows the specification of dependent files and scripts under the script options tab (see screenshot):



However, WinBuilder does not seem to enforce these dependencies. If dependent files are missing the script continues without any warning. If script dependenies need to be enforced a bit of custom code can be used.

Just add the following code sections to your WinBuilder script:

CODE

[process]
Run,%ScriptFile%,CheckDependencies
. . . . .

[CheckDependencies]
Echo,"Checking dependencies ..."
IniRead,%ScriptFile%,main,Depend,%Depend%
StrFormat,SPLIT,"%Depend%",#$c,0,%DependencyCount%
Loop,%ScriptFile%,CheckDependency,1,%DependencyCount%

[CheckDependency]
StrFormat,SPLIT,"%Depend%",#$c,#c,%Dependency%
If,NOTEXISTFILE,"%Dependency%",Begin
  Set,%msg%,"%ScriptTitle% requires %Dependency%"
  Message,"%msg%",Error
  Exit,"%msg%"
End
## ____/If dependency is a script assert that it is selected\____ ##
StrFormat,EXT,"%Dependency%",%DependencyExtension%
If,%DependencyExtension%,EQUAL,".script",Begin
  IniRead,"%Dependency%","Main","Selected",%DependentScriptSelected%
  If,"%DependentScriptSelected%",Equal,False,begin
    IniRead,"%Dependency%","Main","Title",%DependentScriptTitle%
    Set,%msg%,"Script #$q%DependentScriptTitle%#$q must be selected to use %ScriptTitle%"
    Message,"%msg%",Error
    Exit,"%msg%"
  end
End

WetHat

[Lancelot]

However, WinBuilder does not seem to enforce these dependencies. If dependent files are missing the script continues without any warning. If script dependenies need to be enforced a bit of custom code can be used.

Hi WetHat,

WinBuilder does something to enforce,
*
if the dependency script not available and when you try to enable the script, wb warns you that you do not have the dependent script and does not enable the script.
*
if the dependency script available and when you enable the script than you get depedency script enabled too.
*
However,
user can make a mistake and disable dependency script after enableing OR user may have already enabled script which depends on another script OR maybe an advanced user making a test

====>
We have a verrry good tool to prevent end users from these kind of mistakes, wbverify.exe (Verify Project , !WBVerify.Script ). (check here )

!WBVerify.Script executed at the very begining of the project to check many things including dependencies

If there is a dependency error you would get
"blablabla requires dabalabula"



Getting error/warning at the very early step of the build is better than getting the error/warning after many process, I hope you like wbverify

[WetHat]

a verrry good tool to prevent end users from these kind of mistakes, wbverify.exe (Verify Project , !WBVerify.Script ). (check here )

!WBVerify.Script executed at the very begining of the project to check many things including dependencies

If there is a dependency error you would get
"blablabla requires dabalabula"

Getting error/warning at the very early step of the build is better than getting the error/warning after many process, I hope you like wbverify

Hi Lancelot,

I agree that an early check is much better. I'll give wbverify a try!

Thanks for pointing this out.

WetHat