Unfortunately we still do not have enough documentation for the new visual designer and all associated functionality. We are working on improving the documentation as we speak.
Regarding the attach / detach functionality of the new context, we will be implementing this for the Q2 2010 release. It may be available earlier through some preview / beta release.
Regarding moving data through the layers of an n-layer application, you should not have problems using the persistent classes that are generated for you as long as you keep the instance of the context / scope alive. This is needed because a lot of functionality of a persistent class like for example lazy loading depends on the scope / context.
Yes, it is best if the persistent classes generated by OpenAccess are in a separate assembly / project.
And yes, for new development we recommend using the new visual designer and the context. This is where new development will be focused (on our side).
This exception that you are getting, "No persistent class could be found" can happen in two cases:
1. you have added an .rlinq item in an already enhanced project that was created earlier using the reverse mapping wizard. Due to the changes in the enhancer you cannot have a project where both approaches for working with OpenAccess coexist. You can either create an .rlinq item using the visual designer or use the reverse mapping wizard. An updated version is now available for download that (besides of containing some important fixes) will prevent you from mixing both approaches.
2. for some reason the product is not installed correctly and the assembly that contains the persistent classes cannot be enhanced
I hope this helps. Do not hesitate to write again if you have more questions or suggestions.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.