Article information
Article relates to	Telerik OpenAccess ORM
Created by	Ivailo Ivanov
Last modified	December 12, 2011
Last modified by	Ivailo Ivanov

DESCRIPTION

Due to the changes we have presented in the Q3 2011 release of Telerik OpenAccess ORM, in some cases you might experience issues after upgrading from an older version of the product. In this article you can find the list of most common issues and their resolutions.


PROBLEMS AND SOLUTIONS

1. Stored procedure methods have disappeared from the context
Solution: We have improved the stored procedure handling in the Q3 2011 release, leading to breaking changes in the code generation of the Domain Model class - the old format of stored procedure methods is deprecated and a new definition is available through the Stored Procedure Editor. However, there is a simple backward compatibility setting that can bring back the old stored procedure methods. The detailed solution is described in this Knowledge Base article. 

2. Missing extension methods for the context collections – RemoveAll<>(), Sort<>(), etc.
Solution: Detailed description of the change and a helper file with extension methods to be added to your project can be found here.

3. Replacing OpenAccess ORM assemblies directly on the test / live environment leads to errors
Solution: Due to breaking changes in OpenAccess ORM Enhancer tool, the assemblies that contain your Domain Classes need to be rebuilt on a development environment with the latest version of OpenAccess ORM, in order for them to be properly enhanced.

4. Update from Database or Update Database from model wizard is offering connection to be chosen again
Solution: Due to changes made in the RLINQ file connection definition, the connection should be selected again after the upgrade so that the changes can be applied automatically. This is a one-time only action and once performed, the connection will be properly stored and the wizards will skip that page.