Feedback
Did this article resolve your question/issue?

   

Article

When should gacutil.exe be used to register Connect for ADO.Net assemblies?

Information

 
TitleWhen should gacutil.exe be used to register Connect for ADO.Net assemblies?
URL Namewhen-should-gacutil-exe-be-used-to-register-connect-for-ado-net-assemblies
Article Number000178924
EnvironmentProduct: Connect for ADO.Net Oracle driver
Version: 4.2
OS: Windows
Database: Oracle
Application: N/A
Question/Problem Description
A variety of problems may arise when switching versions of assemblies that are being used by an application. It is important to remember that once the Connect for ADO.Net provider assemblies are installed and registered, they are stored in the GAC (Global Assembly Cache).  If a different revision of the same assemblies are needed, the new set needs to be registered in the GAC.  Skipping this important step can lead to errors or unpredictable results.
Steps to ReproduceConnect to Oracle / Sybase with connection string containing BindDateTimeAsDate=TRUE.
DDTek.Oracle.dll File version 4.2.0.12606
DDTek.Sybase.dll File version 4.2.0.7505
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Be sure to register each new set of assemblies with the gacutil.exe tool.  Typically, this is done by openning a Developer Command Prompt and performing the following command on each of the DLLs in the new set being used:

gacutil /if <assembly name>
 
Workaround
Notes
Last Modified Date11/30/2016 5:35 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.