Devart Forums

I'm using LLBLGenPro 2.5 and mySQLdirect 4.0.13 under VS2005. After building the project, version conflict with CoreLab.MySql are found, that can only be resumed by the following entry in app.config.






I'm not sure whether there is any negative impact with this. Anyway this behavior is new and did not exist in previous LLBLGenPro 2.0 and mySQLdirect 3.55.18.

Any idea?

There should be no negative impact in this case.

nb wrote:I'm using LLBLGenPro 2.5 and mySQLdirect 4.0.13 under VS2005. After building the project, version conflict with CoreLab.MySql are found, that can only be resumed by the following entry in app.config.






I'm not sure whether there is any negative impact with this. Anyway this behavior is new and did not exist in previous LLBLGenPro 2.0 and mySQLdirect 3.55.18.

Any idea?

You use the normal MySql driver ? (which is build against v4.x of core lab's provider) ?

@Core lab: didn't you include a policy file with the installer so all v4 references are redirected to the installed version? We build the mysql driver against v4.0.9.0

Also, with the new release of 4.20, will all reference hell and demo protection misery start all over again or is this covered and is transition smooth?

Frans Bouma, LLBLGen Pro lead developer

@Core lab: didn't you include a policy file with the installer so all v4 references are redirected to the installed version? We build the mysql driver against v4.0.9.0

Also, with the new release of 4.20, will all reference hell and demo protection misery start all over again or is this covered and is transition smooth?

We did include the policy files. And we haven't changed the license, so should be no licensing problem with the new version of MyDirect .NET and LLBLGenPro.