Curious about OpenAccess.35 vs OpenAccess.40 extensions

[cori]

I'm a relative n00b to OpenAccess ORM, so please excuse any perceived denseness...

I added an OA domain model to a migration project with great success - was able to relatively quickly populate a database from data in a complex set of Excel spreadsheets.  The console app that's doing the work is running .Net 4.0, and the references for the project have both the Telerik.OpenAccess.40.Extensions and the Telerik.OpenAccess.35.Extensions dlls.

Now I'm taking the model from there and creating its own class library to use in another portion of the project, and I noticed that even though the library project is also .Net 4.0 only the Telerik.OpenAccess.35.Extensions dll references are added when I add the Data Model to the project.

What's the difference between the two (if it's not .Net 3.5 vs .Net 4.0 as I assumed) and how does OpenAccess choose between them?

Thanks!

[PetarP]

Hi cori,

 You only need to add reference to Telerik.OpenAccess.40.Extensions in case you use our old implementation of the astoria data services provider. If you don't need our context that implements the IUpdatable interface then you should not need to include a reference to the .40.Extensions assembly but only to 35. 
I hope my response was useful to you.

Regards,
Petar
the Telerik team

[cori]

That makes perfect sense, thanks.  I probably added them to my original project myself - I am certainly not using Astoria.

Thanks!