Make sure you have uninstalled the trial version correctly. There should be no old (trial) assemblies present in your system. Uninstall dotConnect for Adobe Commerce and check your Global Assembly Cache and local folders for Devart.* assemblies. Remove all Devart.* files and reinstall dotConnect for Adobe Commerce.

Close all running IDEs and help collections, then run the installation package of the newer version. You will be prompted to uninstall the previous version; agree and then proceed to installing the newer build.

To deploy an application written with dotConnect for Adobe Commerce, you need to:

• deploy the Devart runtime assemblies used by your application;
• include the technical license resource;
• in case your application uses provider factories, you also need to expose dotConnect for Adobe Commerce to the system.

For the detailed description of each of these steps, please refer to the Deployment and Licensing topics in dotConnect for Adobe Commerce help.

Select the "Minimal" type when prompted by the installer.

Devart data providers use a common assembly (Devart.Data.dll), so it is necessary to install compatible providers versions. We release our ADO.NET data providers in a single pack, thus releases from the same date should be compatible. Also, Devart data providers should warn you before installation if an incompatible version of Devart.Data.dll was detected.

You should put the Devart.Data, Devart.Data.Magento, and Devart.Data.Magento.Entity.EF4 (for applications using Entity Framework v4 or v5) or Devart.Data.Magento.Entity.EF6 (for applications using Entity Framework v6) assemblies in the Bin folder of your application (or place these assemblies in the Global Assembly Cache). Make sure that your application is licensed correctly (take a look at the Licensing article for more information).

Information about provider registering is available in the Deployment article.

All upgrades to future versions are free to users with an active dotConnect for Adobe Commerce Subscription.

The dotConnect for Adobe Commerce Subscription Program is an annual maintenance and support service for dotConnect for Adobe Commerce users.

Users with a valid dotConnect for Adobe Commerce Subscription get the following benefits:

• Access to new versions of dotConnect for Adobe Commerce when they are released
• Access to all dotConnect for Adobe Commerce updates and bug fixes
• Product support through the dotConnect for Adobe Commerce Priority Support program
• Notification of new product versions

Priority Support is an advanced product support program which offers you expedited individual assistance with dotConnect for Adobe Commerce-related questions from the dotConnect for Adobe Commerce developers themselves. Priority Support is carried out over email and has a two business day response policy.

Yes, you can. dotConnect for Adobe Commerce version licenses are perpetual.

dotConnect for Adobe Commerce uses .NET component licensing. To build an operational application, dotConnect for Adobe Commerce requires a valid license. If no license is available, dotConnect for Adobe Commerce does not work.

Usually you do not have to care about embedding the license in your application. When you install dotConnect for Adobe Commerce, the system is configured so that licensing is done transparently. The license is automatically added to the project when you place a MagentoConnection component onto a form.
In some cases, you have to manually add the license. For instructions on how to add the license manually, refer to the Licensing topic in the dotConnect for Adobe Commerce help.

This generally indicates that license information cannot be found, or you try to apply it in some way that does not suit the kind of application. For example:

• The licenses.licx file, required for dotConnect for Adobe Commerce to function properly, cannot be found.
• The licenses.licx file is not added as an embedded resource.
• The App_Licenses.dll file is not found in ASP.NET applications.

To fix the problem, determine the type of your application and read the corresponding section of the "Licensing" topic.

This means that license information is found but it is incorrect. It usually happens in the following cases:

1. The project was earlier compiled with an old or trial version of dotConnect for Adobe Commerce.
2. The licenses.config file used by a class library does not refer to the launched executable.
3. The App_Licenses.dll file belongs to other application or needs to be recompiled.
4. Something is wrong with the operating system or installation of dotConnect for Adobe Commerce.

If you encounter one of these problems, do the following (the numbers of actions correspond to the numbers of the problems in the above list):

1. Delete all files from the bin and obj folders and rebuild the project.
2. Specify the executable in the licenses.config file.
3. Rebuild App_Licenses.dll for the current application.
4. Perform the following steps:
   1. uninstall dotConnect for Adobe Commerce;
   2. remove all Devart.* and policy.*.Devart.* files from the GAC;
   3. clear the Program Files\Devart\dotConnect and Program Files\Common Files\Devart\dotConnect folders;
   4. re-install dotConnect for Adobe Commerce.

Probably, you compiled the application with the Trial edition of dotConnect for Adobe Commerce, and deployed it with assemblies from a non-trial version. In this case, time limit is actual as well. To eliminate the problem, just recompile the project.

To support server-side compilation you ought to have the special assembly App_Licenses.dll in the Bin directory of your site. To create this assembly, execute the Build Runtime Licenses command in the licenses.licx file context menu in the Solution Explorer view. The required assembly will be created automatically.

Note that this is not necessary for precompiled ASP.NET applications (if nothing is compiled on the server by user request). Precompiled applications are licensed as usual applications.

If any problems with licensing occurred in your project, you should use the License Information dialog box to resolve them. To open it, on the Tools menu point to Adobe Commerce and then click License Information.

No, end-users of your application do not require any license.

No, it is not. This is the Connection Pooling feature. The actual connection is not closed in order to be used later by your application. This boosts performance greatly.

The full text of the exception is "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached." It clearly states that you have run out of connections available. To solve the problem, increase the Max Pool Size connection string parameter value. The default value is 100. Another way to get extra connections is to clear one or all of the pools. Or you can turn connection pooling off using the Pooling connection string parameter.

You can clear the pool explicitly. Generally, the pool is cleared automatically when connections are idle or closed by the server. To force the operation, call the ClearPool or ClearAllPools methods. Another solution is to disable the pool completely (set Pooling=false in the connection string). If this does not help, the problem is not caused by pooling.

There are several ways to open dotConnect for Adobe Commerce documentation:

• Use the appropriate shortcut in the Start menu, for instance, Start -> Programs -> Devart dotConnect for Adobe Commerce -> Documentation .
• Open it from the Visual Studio: on the Tools menu point to Adobe Commerce and then click dotConnect for Adobe Commerce Help.
• Place the cursor on some class from Devart.Data.Magento and press F1.

There is also the same documentation in the chm format. You can download it from our web-site at the following address: www.devart.com/dotconnect/magento/dcMagento.chm. Downloaded CHM files are blocked on Windows operating systems by default. If the downloaded file shows an empty

Correctly installed documentation appears as a separate node in the combined collection of Visual Studio. If you can't find the dotConnect for Adobe Commerce node there, it is because topics filtering is enabled. To reveal the node, set the filter to "Devart Documentation", or "(unfiltered)", or "Visual C#", etc.
Another possible reason is that you installed some IDE after the installation of dotConnect for Adobe Commerce. In this case, use aforementioned methods to access documentation.

This can happen due to some patches from Microsoft installed on your system. Please read this page to find possible solutions to the problem. In most cases, it is enough to right-click the CHM file, select Properties, click the "Unblock" button and click "Apply" to show the contents.

dotConnect for Adobe Commerce supports the latest versions of ADO.NET Entity Framework.

dotConnect for Adobe Commerce comes with Demo Center application, which demonstrates main dotConnect for Adobe Commerce features. Among other features, this application demonstrates LINQ to Entities query execution.

Yes, there are some. First, the provider add-in (and hence menu item) is not available. Second, components are not registered in toolbox automatically (though you can do it manually). Finally, advanced Visual Studio integration (DDEX) is not available, except Microsoft Web Developer Express 2010.

This can happen if the installation encountered some problems. You can add the components to the toolbox manually. This procedure is described in the Installation article in the documentation.

Delete all policy files used by dotConnect for Adobe Commerce from the GAC.

dotConnect for Adobe Commerce assemblies are built with the /platform:anycpu option. So, you can use the provider's assemblies on any platform (x86 or x64). For more information, refer to https://msdn.microsoft.com/en-us/library/zekwfyz4.aspx