Dealing with DLLs - best practices
Posted: Mon Jan 24, 2022 9:25 pm
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
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