This question is locked. New answers and comments are not allowed.
Hi there,
are there people out using OpenAccess with LinqPad? I read some blog posts on how to use it. But there is currently no real driver present for OpenAccess. I prefer the simplicity of LinqPad, so I startet to write one by myself without the need to instanciate a scope etc. The result 'til now is promising and I have implemented very basic features. I'v planned to use LinqPad with queries like that:
from e in customers select e
No scope, no Extent-Method etc.!!!
By now I have several questions:
1. @Telerik: are there currently plans or even implemented parts on this topic in the near future? If yes, then I won't spent much more time on this topic.
2. What do you think about it? In which manner do you use LinqPad?
3. Which database(s) do you use with OpenAccess?
4. Do you use the new entity designer by now?
My plans for now:
1. Create basic connect dialog where you choose the model assembly, connection settings to database, etc.
2. investigate, whether it contains the new designer generated code or conventional model classes
2a. if conventional data model: create scope and extent-properties dynamically
2b. if designer generated code: use entity diagram as data source
3. Dynamically wrap it for use in LinqPad
4. Fill schema info in LinqPad
As long as I exclusively use MS-SQL by myself, I would see this in first place and implement other databases for connection settings later.
Greetings,
Daniel
are there people out using OpenAccess with LinqPad? I read some blog posts on how to use it. But there is currently no real driver present for OpenAccess. I prefer the simplicity of LinqPad, so I startet to write one by myself without the need to instanciate a scope etc. The result 'til now is promising and I have implemented very basic features. I'v planned to use LinqPad with queries like that:
from e in customers select e
No scope, no Extent-Method etc.!!!
By now I have several questions:
1. @Telerik: are there currently plans or even implemented parts on this topic in the near future? If yes, then I won't spent much more time on this topic.
2. What do you think about it? In which manner do you use LinqPad?
3. Which database(s) do you use with OpenAccess?
4. Do you use the new entity designer by now?
My plans for now:
1. Create basic connect dialog where you choose the model assembly, connection settings to database, etc.
2. investigate, whether it contains the new designer generated code or conventional model classes
2a. if conventional data model: create scope and extent-properties dynamically
2b. if designer generated code: use entity diagram as data source
3. Dynamically wrap it for use in LinqPad
4. Fill schema info in LinqPad
As long as I exclusively use MS-SQL by myself, I would see this in first place and implement other databases for connection settings later.
Greetings,
Daniel