xsharp.eu • Dealing with DLLs - best practices
Page 1 of 1

Dealing with DLLs - best practices

Posted: Mon Jan 24, 2022 9:25 pm
by alex_schmitt
Dear all,

my project uses the following 3rd party projects:

- BBrowser
- Xs2Ado
- SEUIXP
- Fabtools

When I use the respectively compiled DLLs of these projects and place them into one folder for referencing them out of my own projects I am ending up in compiler errors as to my understanding these binaries require different versions of native XS-Dlls.
E.g.:

error XS1705: Assembly 'SEUIXPXS' with identity 'SEUIXPXS, Version=1.7.0.0, Culture=neutral, PublicKeyToken=null' uses 'VOGUIClasses, Version=2.6.0.0, Culture=neutral, PublicKeyToken=a967d8055360a7b9' which has a higher version than referenced assembly 'VOGUIClasses' with identity 'VOGUIClasses, Version=2.0.0.8, Culture=neutral, PublicKeyToken=a967d8055360a7b9' 31,1 _winShellAbstract.prg winShellAbstract:winShellAbstract

How can I get out of this? Do I need to compile all the projects from scratch to make sure all of them are referencing the same native XS DLLs?

Best,
Alex

Dealing with DLLs - best practices

Posted: Tue Jan 25, 2022 12:33 am
by Chris
Hi Alex,

This GUI dll version 2.0.0.8 is very very old, how come you are using this? Which X# version do you have installed? You will just need to replace the references to those old dlls to more recent ones and the problem should go away.

Dealing with DLLs - best practices

Posted: Tue Jan 25, 2022 10:08 am
by robert
Alex,
The VERY old version of X# also explains the warnings you got when opening the source code to FabTools.
Please use the last available public version: 2.9.

Robert

Dealing with DLLs - best practices

Posted: Tue Jan 25, 2022 9:19 pm
by alex_schmitt
Hi Chris, Robert,

I copied now all of these DLLs into one folder and made sure that no legacy DLLs are in there. Not sure where they came from but that actually did the trick.

Thanks!

Alex