Porting to LogicLab

WARNING: Those steps are strictly required because LogicLab5 has a different file and folder organization (the folder name inside the redist has changed from LogicLab4 to LogicLab5, and the executable name from LogicLab4.exe to LogicLab.exe)

Porting procedure from LogicLab4 to LogicLab5:

ISS changes

• modify the application name (da LogicLab4 a LogicLab5) in ISS (#define NameApp)
• modify the folder name (from LogicLab4 to LogicLab5) in the ISS file (#define LLSrcDir)
• modify the executable file name (from LogicLab4.exe to LogicLab.exe) in the ISS file (#define LLNameExe)
• Remove the old version (LogicLab4) in the ISS file with InstallDelete, if desired

[InstallDelete]
Name: {app}\LogicLab4; Type: filesandordirs

• Add in the ISS file the copy of the LogicLab\styles folder

Source: ..\{#LLSrcDir}\Styles\*.*; DestDir: {app}\{#LLDestDir}\Styles; Flags: ignoreversion

• Remove the AlUIExt.dll installation, not existing anymore

Source: ..\{#LLSrcDir}\AlUIExt.dll; DestDir: {app}\{#LLDestDir}; Flags: ignoreversion

LLMakeCustomVersion.bat changes

• modify the path (from LogicLab4 to LogicLab5) (set BUILDPATH)
• modify the executable file name (from LogicLab4.exe to LogicLab.exe) in the CustomVersions script (set SRC), in the :Init function

PCT catalog changes

• Modify the PCT file of every target of your catalog if they have any reference <loadExternalTemplate> that points to LogicLab4 in LogicLab5
• Modify the relative path of system libraries in the catalog, e.g. "<library>..\..\LogicLab5\Libraries\Standard.pll</library>"
• Modify the templates\LogicLab.pct file substituting <extension><dll> LogicLab4.exe in %APPEXENAME%

PageLab changes

• If you have Pagelab on your suite, modify the PLMakeCustomVersion.bat file and updating the NAMELLC and LOGICLAB_PATH variables