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

Question

Question

Custom Code in WebLink 8/9

asked on November 7, 2023

Posting on behalf of client:

I’m reaching out to see if there was a developer or someone familiar with WebLink code who could assist me in figuring out how I can change the code as well as build and deploy it.

The main issue I am having is that I’m unable build the solution. There are several references to DLLs that are missing however I am using the most up to date code base and the same code files work in production so I’m not sure what’s going on.

As you can see in the above screenshot, it is complaining about an assembly “Interop.LFSO92Lib” and I’m not sure how to proceed.

----

The original problem I had is that there is seemingly multiple solutions with *almost* identical code in them, and they all are called WebLink. I wasn’t sure which one it was, so I decided to bring in the code that was already in prod and start from scratch with a new repo.

The DLL I found in production is titled “WebLink 8” however one of those solutions I was mentioning before that we have are titled “WebLink 9.0 code”, and whoever was maintaining this code before me left no documentation on what is and isn’t the correct solution. So, based on the DLL that is in production I believe it is Weblink 8, however there’s a solution for Weblink 9.0 code in our repository for this project and I’m not sure if it is related or not.

There are multiple solutions with seemingly slightly different versions and It’s left me confused.

----

[We'd] like to add to the query parameters of a document link a timestamp that the DocView page will check. If the timestamp has expired then the document will no longer be viewable to the user. This was a layer of security we wanted to add so that these URLs that our document service api generates are not viewable forever.

0 0

Replies

replied on November 7, 2023

Not sure if you've talked to them about this, but I would try and talk them into upgrading. Laserfiche 8 products hit end of support December 31, 2019 and Laserfiche 9 products December 31, 2021.

1 0
replied on November 7, 2023

Hi Blake,

 

Thank you for your response. The client is open to upgrading if the link expiration is available in a newer version. From my understanding, the concern is that there's less room for customization in the later versions, so unless that functionality has since been introduced, they'd have more luck writing it themselves in the more "open" version they currently have.

0 0
replied on November 7, 2023

The link expiration isn't available in newer versions, but what makes them think that the newer versions are less customizable? You are able to use Visual Studio to alter the code just like previous versions. See the help files.

0 0
replied on November 17, 2023

Interop.LFSO92Lib is a component that allows .Net code to call into the COM LFSO library. It's installed as part of the WebLink installation, but if you just copied the code off to a dev machine you might not have it. I think the interop goes in the GAC, and I recall Visual Studio being reluctant to look in there for it. You might have to manually copy it out and add a reference to the project.

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

Sign in to reply to this post.