We are using the standard .NET approach for handling connection strings. And this is storing the connection string in a configuration file. If you open up the context class that is generated by the rlinq file you will see that the default constructor passes the connection string name to the base class. This is the name of the connection string that the runtime is trying to resolve from the configuration file.
Can you make sure that your running application has a connection string with that name in its configuration file. Another solution to this problem would be to pass in the actual connection string to the context constructor, which would make sure that it is not resolved from and needed in the configuration file.
I hope this proves to be helpful.
the Telerik team
Q3’11 of Telerik OpenAccess ORM is available for download. Register for the What's New in Data Tools webinar to see what's new and get a chance to WIN A FREE LICENSE!