How to Upload Status Message to Devart

This topic provides technical details on embedding license information into your applications. This is a special resources that must exist nowadays in every application that uses dotConnect for Oracle.

Note:
License data discussed in this topic is non same thing as license for using dotConnect for Oracle. License purchased on our site allows you, your team, or your visitor to utilise dotConnect for Oracle. For information on how to purchase license for using dotConnect for Oracle please refer to topic Ordering.

The article consists of following sections:

• General Information
• Licensing .NET Standard (.Cyberspace Core) Projects
• Adding License Automatically
• Adding License Manually
• Grade Libraries Back up
• Licensing ASP.NET Applications
• Licensing Meaty Framework Projects
• DbProviderFactory Notes
• Compiling License Manually
• Licensing Mono Projects
• Troubleshooting

General Data

dotConnect for Oracle uses .Cyberspace component licensing. To build an application dotConnect for Oracle requires valid license. If no license is available, dotConnect for Oracle does not work.

License information is a especially formed embedded resources. Unremarkably you do non have to care about embedding license in your application. When you install dotConnect for Oracle, the system is configured so that licensing is done transparently. Terminate-users of your software do not require any additional license.

dotConnect for Oracle includes License Wizard that helps y'all configure license information. The wizard analyzes the current projection, informs you about bug found, and performs some actions needed to fix the problems.

To invoke the wizard cull Oracle | License Information from the Visual Studio Tools bill of fare. Then click the Set up buttons in the dialog and follow the wizard's instructions. In about cases this is enough to configure .Net component licensing.

The following tabular array helps get started quickly with dotConnect for Oracle licensing. Find your blazon of application and follow links to corresponding sections of the commodity.

Diagram	Explanation
	This is general case of licensed .NET Framework application. Whatever the blazon of awarding you lot develop, read carefully sections Adding License Automatically and Adding License Manually.
	These two diagrams show how you can apply dotConnect for Oracle through a class library. In add-on to Adding License Automatically and Calculation License Manually delight read department Grade Libraries Support.
	These are two modes of accessing dotConnect for Oracle within ASP.Cyberspace awarding. In addition to Adding License Automatically and Calculation License Manually delight read department Licensing ASP.NET Applications.
	Some applications that have no licensing information embedded, and use DbProviderFactory to operate dotConnect for Oracle, crave the product installed on the computer. Refer to section DbProviderFactory Notes for more information.

Licensing .Cyberspace Standard (.Cyberspace Cadre) Projects

.NET Standard compatible assemblies of the dotConnect for Oracle utilize a unlike licensing mechanism. For .NET Standard (.Net Core) projects you lot must add together the license key either as a connexion cord parameter or as a file to the C:\ProgramData\Devart\dotConnect\License\ folder. For more information read the Licensing .NET Standard (.Cyberspace Core) Projects topic.

Calculation License Automatically

License is automatically added to project when you drop a OracleConnection component from Toolbox onto a class designer.

Under .Cyberspace Meaty Framework, in the moment of compilation license information is automatically added if the dotConnect for Oracle addin for Visual Studio is running.

Adding License Manually

In some cases you have to manually add license. Information technology is necessary for panel applications, class libraries, and existing projects initially congenital with dotConnect for Oracle version that did not use component licensing, that is, iii.00 and older. In this instance perform the post-obit steps:

• Create a file named licenses.licx, if this file does not be yet.
• Open up the file with a text editor and place this line inside:
  Devart.Information.Oracle.OracleConnection, Devart.Information.Oracle
• Salve the file and add it to your project.
• Make sure information technology is embedded as a resources.

If IDE fails to compile the license automatically, y'all can practice it yourself as described in department Compiling License Manually.

Course Libraries Back up

In case where it is impossible to put the license data direct to executable file, dotConnect for Oracle allows you lot to create grade libraries that can be used with certain executable files. To exercise this perform the following steps:

1. Create and setup file named licenses.licx as described above.
2. Create a text file named licenses.config and identify it next to licenses.licx.
3. In this file enumerate names of executable files that will work with the library, every file proper name on dissever line, for example:

   MyApplication.exe
   MyAnotherApp.exe
   ExtraTool.exe

Yous do non have to add together the file licenses.config to project.

Licensing a library without specifying the executables that will use it is possible by agreement with Devart. For details on this, delight mail to support@devart.com or sales@devart.com.

Licensing Spider web Projects

In that location are 2 types of web projects depending on the type of licensing.

1. Starting time, Web Application Project (Web Forms, MVC, Spider web API, etc.) are compiled entirely, so that web server does not perform any compilation on need. In this example licensing spider web applications is aforementioned equally licensing mutual Course Library applications.
2. Second, there are Spider web Site Projects, when source files are uploaded to server, where they are compiled on user request. In this instance you should deploy a special associates App_Licenses.dll to the Bin directory of your site for the Web Site projects. To create this assembly, right-click the licenses.licx file in the Solution Explorer view and and then click Build Runtime Licenses. The required assembly will be created automatically. Note that the corresponding shortcut menu command is available when the licenses.licx file is located in the root folder of the site.

Licensing Compact Framework Projects

For .NET Compact Framework the Visual Studio add-in automatically embeds all required information into every assembly that uses Devart.Data.Oracle.dll library. Form libraries are supported automatically.

If the license fails to be added to a projection, you can add together and compile information technology manually. Notation that at that place is no license compiler from Microsoft for .Net Compact Framework. You tin can request the compiler from Devart support team.

There is a known problem with the .Net Compact Framework. A "License non institute" exception can be thrown by OracleDataAdapter.Make full method in case when OracleConnection had never been opened. To avert the trouble just open (or open up and close) whatever connection before calling the OracleDataAdapter.Fill up method.

DbProviderFactory Notes

Applications that phone call dotConnect for Oracle through DbProviderFactory require registration in DbProviderFactory. This registration can be performed either by launching installer of dotConnect for Oracle with the Minimal install type (the licenses.licx file is not required in this case), or manually every bit it is described in the Deployment topic. DbProviderFactory support allows using dotConnect for Oracle in SQL Server 2008/2012 Business Intelligence Solutions.

Compiling License Manually

The license resource cannot exist compiled automatically when your project does not take reference to Devart.Data.Oracle.dll or dotConnect for Oracle is not installed on your build server. This section describes how to compile the required resource manually.

Generate licensing resources file using following command line:
"%Compiler Path%\lc.exe" /target:MyApplication.exe /complist:licenses.licx /i:"%Assembly Path%\Devart.Data.Oracle.dll"
Where

• %Compiler Path% is a path to advisable lc.exe file (for case, C:\Plan Files\Microsoft.NET\SDK\v2.0\Bin);
• MyApplication.exe is name of your target executable file;
• licenses.licx is a text file described earlier in this topic;
• %Assembly Path% is location of Devart.Information.Oracle.dll assembly

Substitute these arguments with actual values. If the license compiler fails with an error, try calculation full assembly specification to licenses.licx file, for example:
Devart.Information.Oracle.OracleConnection, Devart.Data.Oracle, Version=viii.4.215.0 , Culture=neutral, PublicKeyToken=09af7300eec23701

License compiler will generate 'MyApplication.exe.licenses' resources file. You should add this file to your project as an embedded resource. Note that you should not add licenses.licx to the project because the *.licenses file already includes all the necessary license information.

If the default namespace of your project is non an empty cord, it must be the same as the target assembly name (in this example - 'MyApplication'). IDE adds the default namespace to the resource name when building application, then you lot have to rename 'MyApplication.exe.licenses' to 'exe.licenses' before calculation information technology to projection. If the default namespace of your project is not prepare (is an empty string) yous do not have to rename the resources file before adding it to project.

You can too generate the license resource manually for the course library assembly (*.dll) in the same way. But identify licenses.config in the binder with your licenses.licx (and modify /target:MyApplication.exe to /target:YourClassLibraryName.dll).

Licensing Mono Projects

Since automated license generation and embedding is non possible with Mono y'all accept to add together and compile license manually every bit described above.

Troubleshooting

When something'south wrong with license data you get one of the following exceptions on connecting to server:

Exception text	Possible reasons and what to do
License non found...	This more often than not indicates that license data could non exist found, or you try to apply it in some way that does not suit the kind of awarding. For example: File licenses.licx, required for dotConnect for Oracle to function properly, could not be institute. File licenses.licx is not added as embedded resources. File App_Licenses.dll not found in ASP.Cyberspace 2.0 applications. To fix the problem determine type of your application and read corresponding department in this topic. This exception can exist thrown by OracleDataAdapter.Make full method under .NET Compact Framework, in case when OracleConnection had never been opened. To avoid the trouble just open up (or open and close) any connection earlier calling the OracleDataAdapter.Fill up method.
License not valid...	This means that license data was found but information technology is incorrect. It ordinarily happens in the post-obit cases: The project was earlier compiled with old or trial version of dotConnect for Oracle. File licenses.config used by a class library does not refer to launched executable. The App_Licenses.dll belongs to other application or needs to exist recompiled. Something's wrong with the operating system or installation of dotConnect for Oracle. Y'all are building your project on a estimator with no dotConnect for Oracle installed (for case, it is not installed on your build server), and the compiled license resources is not added to the project. If you encounter ane of these problems, exercise the following (the numbers of deportment correspond to the numbers of the bug in the higher up list): Delete all files from the bin and obj folders and rebuild the project. Specify the executable in the licenses.config file. Rebuild App_Licenses.dll for the electric current application. Perform the following steps: uninstall dotConnect for Oracle; remove all Devart.* and policy.*.Devart.* files from the GAC; clear the Programme Files\Devart\dotConnect and Program Files\Common Files\Devart\dotConnect folders; re-install dotConnect for Oracle. In that location are ii means to solve the problem: Install dotConnect for Oracle on the estimator where you build your project. Compile the license resources (*.licx file) on a reckoner, where dotConnect for Oracle is installed, and and then add together the consequence file (*.licenses) to your project equally an embedded resource. After this you can build your project on a computer with no dotConnect for Oracle installed. If this does non assist, send a minor compiled binary with sources to our support address, so we tin can investigate the problem in more details.
Pitiful, your trial menses has expired...	This exception indicates that you used trial version of dotConnect for Oracle, and the 30 days trial menstruum is expired. To continue using dotConnect for Oracle register it or uninstall from your car. You tin too see this message if the application was compiled with registered version of dotConnect for Oracle, only deployed with trial assembly Devart.Information.Oracle.dll. If this is the case, replace onetime files with latest assemblies.

coxshomeady1975.blogspot.com

Source: https://www.devart.com/dotconnect/oracle/docs/licensing.html

Share this post