This question is locked. New answers and comments are not allowed.
Greetings guys,
We have OpenAccess/Data Access installed and are using it for our main product. We do have a small side project that uses BLToolkit for the purposes of creating a DAL.
Now the problem, if we build the solution on a PC with OpenAccess installed somehow it gets "injected" as a reference or embedded type or something like that and if you run the assembly on a test pc WITHOUT OA installed it will start throwing errors. If we build the exact same solution - no changes no nothing - on a pc WITHOUT OpenAccess installed it will then run fine on the test pc.
I'd like to point out that will did used to have a reference to OpenAccess in this project at the very beginning, but had to remove it a bit later on (due to the way bltoolkit builds business objects), however we've checked and triple checked every reference and made sure the libs we use are not shared between telerik (namely the mysql connector) and still nothing.
We have OpenAccess/Data Access installed and are using it for our main product. We do have a small side project that uses BLToolkit for the purposes of creating a DAL.
Now the problem, if we build the solution on a PC with OpenAccess installed somehow it gets "injected" as a reference or embedded type or something like that and if you run the assembly on a test pc WITHOUT OA installed it will start throwing errors. If we build the exact same solution - no changes no nothing - on a pc WITHOUT OpenAccess installed it will then run fine on the test pc.
I'd like to point out that will did used to have a reference to OpenAccess in this project at the very beginning, but had to remove it a bit later on (due to the way bltoolkit builds business objects), however we've checked and triple checked every reference and made sure the libs we use are not shared between telerik (namely the mysql connector) and still nothing.