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; } } }

LAPI GetVersionInfo

James_Wilson

Been trying to figure out how to make c# call to lapi to invoke a call to LL_GetVersionInfo. That works but the integer that the DLL returns is now a mystery to me. How do we invoke code to get the string back from that Integer. LL_AssocGetString requires a "name-value pair". Is there doc on where this is located ?

Thanks

Jim Wilson.

Find more posts tagged with

Comments

eLink User

I am not sure if I understand you question correctly...LAPI functions return a status code. Outcome of a function is returned in one or more 'out' parameters.However: you can find the relevant documentation on GetVersionInfo online Regarding Assoc (and LLValue in general) usage please refer to "Value API: Java and .NET" in the LAPI documentation: The full documentation is online: or in your local installation in: ./builder/documentation

James_Wilson

Ok to say my question was cryptic after reading it would be an understatement. Thanks for the reply.

We created a c# class that is a C# clone of lapi.bas & lapi_documents.bas. We can call the LL_GetVersionInfo and get the VersionInfo integer back. I also can make a call to LL_AssocGetInteger and that works. We are blowing up trying to do a call to LL_AssocGetString. Any thoughts ?

// Declare Function LL_GetVersionInfo Lib "lapi_documents.dll" (ByVal session As Integer, ByVal VolumeID As Integer, ByVal NodeID As Integer, ByVal VersionID As Integer, ByVal VersionInfo As Integer) As Integer

DllImport ( "lapi_documents.dll" )] public static extern int LL_GetVersionInfo( int session, int VolumeID, int NodeID, int VersionID, int VersionInfo)

[ DllImport ("llkernel.dll")]

// Declare Function LL_AssocGetString Lib "llkernel.dll" (ByVal value As Integer, ByVal name As String, ByVal buf As String, ByVal bufLen As Integer, ByRef outSize As Integer) As Integer public static extern int LL_AssocGetString( int value, string name, string buf, int bufLen, ref int outSize);

Any thoughts as to what I am doing wrong ?

m_cLLAPI.LLMemAllocate(ref versionInfo);

int status = DMS_LAPI. cLAPI_documents .LL_GetVersionInfo(m_hSession, m_EnterpriseVolumeId, NodeID, VersionID, versionInfo); int fileSize = m_cLLAPI.LLAssocGetInteger(versionInfo, "FileDataSize" , m_hSession);

string fileName = m_cLLAPI.LLAssocGetString(versionInfo, "FileName" , m_hSession)

Kyle_Swidrovich

Is there a reason you are not using the native .NET LAPI libraries (e.g., LAPI_NETp.dll) instead of rewriting the VB versions?

James_Wilson

Because that DLL is dependent on Visual J version 1.0 and .NET 1.1

Running this with those versions in our environment is not an option. Any chance we could get a version of that DLL compiled under newer versions of Visual J and .NET ?

eLink User

Maybe it is just because I am not very familiar with this kind of re-usage but I do not see where/how you transform the result of LL_AssocGetString -- which is stored in a specified buffer -- to a return value: The documentation of LL_AssocGetString says"This function copies the string stored in the specified field of an Assoc value object to the specified character array."I think this happens in the implementation of your LLAssocGetString function -- how?What error exactly do you observe?

Ferdinand Prantl

This thread is taking the direction: How do I get LAPI libraries friendly to modern environment? Well, having LAPI officialy deprecated, you can't expect getting them from OT. You should consider APIs pushed by OT today - SOAP WS.

These are some threads I found in OTDN about LAPI & new platforms that may give you some options:

--- Ferda

James_Wilson

Sorry should have included that. Getting " Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

Code looks like this where versionInfo is the integer value returned from LL_GetVersionInfo.

int lStatus = 0; string outValue = null ; int lSize = 0; int bufferSize = 500; cLAPI .LL_AssocGetString(versionInfo, "FileName" , outValue, bufferSize, ref lSize);

James_Wilson

That is a valid point just we have too many .NET apps to scrap right now.

Ferdinand Prantl

I noticed that you are receiving the output parameter as string. If you were using P/Invoke it would be wrong; I haven't used RCW for a long time but I think that the marshalling rules are the same. You can try to change the type from string to StringBuilder. String is meant for input parameters, StringBuilder for input/ouptut parameters. You must set the capacity of the StringBuilder beforehand to get the memory allocated and prevent the callee from writing to void.

--- Ferda

James_Wilson

Great idea thanks.. I was thinking along that line but just wasn't sure.

Thanks... Jim

James_Wilson

StringBuilder instead of String was the answer. Thank you very much !