Hi, all. I’m currently creating an extension library which is dependent on SkiaSharp. SkiaSharp itself is a managed DLL, however it is dependent upon libSkiaSharp.dll which is unmanaged. Is there a way to include this file in the customization project which makes acumatica ignore the file while keeping it visible to the extension library’s DLL.
Any help and insight is deeply appreciated, thank you kindly.
Best answer by Dmitrii Naumov
As far as I understand, it will still put the dll in the bin folder, so the message is simply a warning and you can ignore that if it’s expected.
+7As far as I understand, it will still put the dll in the bin folder, so the message is simply a warning and you can ignore that if it’s expected.
Thank you for the reply, Dmitrii. I just did some testing to see what side effects it may have. I found one in the Translation Dictionaries which looks like the following:
I think this is caused by the unmanaged DLL because if I were to delete the unmanaged DLL from the Bin and refresh the website, this error does not appear. Also PX.Data has not been altered by my extension library as I have set “copy local” to False in Visual Studio.
+7It looks like it’s a bug. I’ll report to the engineering team
Alright, thank you very much for the help, Dmitrii. Just curious, would that mean that if the bug were to be fixed, my customization project will only function properly on 2022R2?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
