You are viewing limited content. For full access, please sign in.

Question

Question

Launch Laserfiche Client and search - Version 8.3 and 10.3

asked on July 10, 2018 Show version history

Hello all,

I have a pretty simple question. Users will possibly have one of two different versions of the Laserfiche Client. They might have the Laserfiche Client 8.3 or they might be upgraded to version 10.3. 

The tricky part is, I am trying to write code that will work on both versions of the clients in which I can launch the client and perform a search. So I have code like this:

try
{
    SearchOptions serO = new SearchOptions();

    /*...Assign search options here...*/

    LaunchOptions launO = new LaunchOptions();
  
    /*...Assign launch options here...*/

    ClientInstance cliIn;
    ClientManager cliMan = new ClientManager();

    //On Laserfiche Client 10.3 this works and searches fine, on Laserfiche Client 8.3 it throws and error "Timeout waiting for client startup"
    cliIn = cliMan.LaunchClient(launO);

    /* Additional code here to search, never gets here on Laserfiche Client 8.3. */
}
catch
{
    //Comes here after erroring: "Timeout waiting for client startup"
}

Is there any way around this? Somehow read the version of the client installed on the machine and launch the Laserfiche 8.3 Client a different way? It's probably recommended to upgrade all users to the most current version obviously, but I was just wondering if this is something that can be done.

 

Thanks in advance for any help/suggestions.

0 0

Replies

replied on July 10, 2018

It sounds like reading the client version is the way to go, it is stored in the registry: HKLM\SOFTWARE\WOW6432Node\Laserfiche\Client\CurrentVersion

1 0
replied on July 11, 2018 Show version history

Thanks Robert,

Does this restrict me to using LFSO and ImageEnabled? Or is there an easier way to accomplish this?

I don't know how well RepositoryAccess works on older Laserfiche clients 8.3 and under.

Also I don't think there would be an issue reading the registry on standard user accounts, but I'd have to check the policies as that could have an effect if they aren't able to.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.