License only activated on connection.Open()

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
yaz_ozzie
Posts: 4
Joined: Wed 24 Apr 2019 08:38

License only activated on connection.Open()

Post by yaz_ozzie » Wed 08 May 2019 09:16

We have found that we are unable to use parts of OracleScript without having already activated the Devart license via connection.Open(). Whilst we are generally likely to be in a position where we can open an unneeded connection early in our scripts simply for the purpose of activating the license key, this seems like a bit of a hack.

Is there any functionality in Devart to activate the license (e.g. in as a standalone method call) without first opening a database connection so that we can access the functionality we need? In our case, we are looking to use the parser on some SQL code and don't require a database connection to do so.

Pinturiccio
Devart Team
Posts: 2390
Joined: Wed 02 Nov 2011 09:44

Re: License only activated on connection.Open()

Post by Pinturiccio » Tue 14 May 2019 17:20

The OracleScript class is not present in the Free edition of dotConnect for Oracle. Thus, you need to activate the license first when you use assemblies from NuGet packages. And activating can be done only when opening a connection.

As a workaround you can open a connection only with the one parameter "License Key". Opens will fail, thus you need to run it in the try block. License check is performed before a connection opening. Thus you can use OracleScript right after the catch block.

yaz_ozzie
Posts: 4
Joined: Wed 24 Apr 2019 08:38

Re: License only activated on connection.Open()

Post by yaz_ozzie » Thu 16 May 2019 10:51

Thanks for your reply - we will work with that solution.

Post Reply