nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Installer for FileSite Custom Command

dan9298

I am building a Windows Installer (.msi) that deploys a FileSite custom command, along with some other items. I want to create a launch condition that will check that FileSite is installed before beginning the install process. What is the correct way to do this (check for registry key, existing file, etc.)?

Find more posts tagged with

Comments

jny

I am building a Windows Installer (.msi) that deploys a FileSite custom command, along with some other items. I want to create a launch condition that will check that FileSite is installed before beginning the install process. What is the correct way to do this (check for registry key, existing file, etc.)?

I'm not sure how effective this is: You can read the install root from this regkey setting, then read the file system directory to validate the installed files are present:

[HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\WorkSite\8.0\Common\InstallRoot]

dan9298

Thanks, jny. This sounds reasonable, but my only concern is what happens when a new version is installed, and suddenly the version number isn't 8.0, which means my check is now invalid.

jny

Thanks, jny. This sounds reasonable, but my only concern is what happens when a new version is installed, and suddenly the version number isn't 8.0, which means my check is now invalid.

This key hasn't changed for 8.0 through 8.2. But to be on the safe side, you may check for [HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\WorkSite] then evaluate the subkeys.

Another approach would be to write up a script that invokes an instance of the AppModeCmd Object. This command class uses the IManExt.dll. So, if it fails at the attempt of creating this object, you'd know that IManExt.dll is most likely not registered - which means that WorkSite Desktop Clients are not installed as it's a core DLL to all of the WorkSite Desktop apps. The error typically reads: "Type Library not Registered." This implies that you should have error trap to evaluate the error message.

If the AppModeCmd is invoked successfully, then you may further check for the connection mode, the specific client, i.e., Integration app, DeskSite or FileSite. In which case, WorkSite Desktop Client is present.

[appmode.vbs]


Dim cmd
Dim context
Dim strAppName
Dim eAppMode

Set cmd = CreateObject("IMANEXT.AppModeCmd")
Set context = CreateObject("IMANEXT.ContextItems")

With cmd
.Initialize context
.Update
.Execute
End With

strAppName = context.Item("IManExt.AppMode.AppName")
' this returns the name of the WorkSite Client that is currently launched
eAppMode = context.Item("IManExt.AppMode")
' this returns the connection mode
' 0 = No connection established (IManExt.AppMode.AppName should respectively return empty string)
' 1 = On-line
' 2 = Off-line

MsgBox strAppName & ", " & eAppMode

dan9298

Thanks again. I think this will give me some ideas to work with.