upugrading version of dotconnect

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
Posts: 43
Joined: Mon 13 Oct 2008 13:23

upugrading version of dotconnect

Post by edstaffin » Mon 25 Aug 2014 10:32

Hi, Since only one version of devart can be installed at any given time, does that mean that if I want to roll out a new version of Devart that I have to update the references and redeploy all asp.net apps at the same time? In other words, if devart is currently at version 1, for example, and all my apps are referencing version 1 and then version 2 comes out. Do I have to update references in my app to v2 and redeploy everything? Or, as I hope, can I just deploy v2 of devart on the server and the existing apps will start using it without problem?
Thanks ... Ed

Devart Team
Posts: 2141
Joined: Wed 02 Nov 2011 09:44

Re: upugrading version of dotconnect

Post by Pinturiccio » Tue 26 Aug 2014 15:19

edstaffin wrote:Since only one version of devart can be installed at any given time
You can install different versions of dotConnect for Oracle on the same computer at the same time. For more information, please refer to http://forums.devart.com/viewtopic.php?t=30225

If you want to add the new dotConnect for Oracle assemblies to your project, please do the following:
1) Set "Specific Version = False"; in the properties of the Devart assemblies
2) Specify the assembly name without version in the licenses.licx file:
Devart.Data.Oracle.OracleConnection, Devart.Data.Oracle
3) If a major version of dotConnect for Oracle is changed, you need to rebuild the application for correct work of technical licensing.

After this you can just deploy new versions of Devart assemblies.

However, when a project is an ASP.NET application, there can be the following difficulties:
1. The web.config file usually contains several references with the exact assembly version. For example:

Code: Select all

  <add assembly="Devart.Data.Oracle.Web, Version=, Culture=neutral, PublicKeyToken=09AF7300EEC23701" />
  <add assembly="Devart.Data.Oracle, Version=, Culture=neutral, PublicKeyToken=09AF7300EEC23701" />
  <add assembly="Devart.Data, Version=,  Culture=neutral, PublicKeyToken=09AF7300EEC23701" />
That's why you also will need to modify the web.config file.
2. The records containing the specific version can also be in your web form, for example, when this form contains the OracleDataSource component:

Code: Select all

<%@ Register assembly="Devart.Data.Oracle.Web, Version=, Culture=neutral, PublicKeyToken=09af7300eec23701" namespace="Devart.Data.Oracle.Web" tagprefix="cc1" %>
In such case you will need to rebuild your application.

Post Reply