This question is locked. New answers and comments are not allowed.
Hi,
A lot of people, myself included, are aware of Microsofts entrance on the O/R market - presenting the Entity framework as a new project type inside VS2008.
I read a lot about it, and went for a spin.
After a couple of minutes I had my database mapped and was ready to go.
Later I discovered that some many-many tables were not mapped, and found that updating/refreshing just a part of the model was a "no go" - but maybe I missed something. Also had to close/open VS2008 a couple of times because the visual table mapper "went out of business" from time to time.
I use Linq2Sql today, and the transformation to Entity framework seemed very easy.
1. I like the table layout design direct in VS2008 - also know from Access, Linq2Sql and so on - maybe you could implement this approach in OpenAccess?
I can confim a statement read in several blogs,- "The product are not mature, I will wait for version 2".
Another statement "out there" are that Linq2Sql will not have Microsofts full attention in the future, it's all about the Entity Framework from now.
Therefore I, like others, are looking for alternatives - better alternatives.
2. Microsoft are committed to support LINQ, and your roadmap show me that Telerik are going that way to, right?
3. Can you please state, from your perspective, the pro/cons on using OpenAccess instead of just "jumping the Microsoft wagon" and go with the Entity framework?
4. Microsoft have several advantages regarding integration the Entity Framework into VS2008(and other products), where do you stand here?
Have been reading a lot on ORM products "out there" and have come to the conclusion that is's all a kind of religion - it's like the old times "Netscape/IE" - "Unix, Linux, Mac or Windows" - but all we want are to map our relational date into some objects, doing a little of modifying, insert, update and delete - or the other and more abstract way around,- define our classes, interfaces, relations and create the database.
It is, in my mind, crucial that the interface between the database and the model are rock solid - I am looking for a real WYSIWYG interface, and if it could create some automated unit tests it would be news to me.
Regards,
Bo Hessner
A lot of people, myself included, are aware of Microsofts entrance on the O/R market - presenting the Entity framework as a new project type inside VS2008.
I read a lot about it, and went for a spin.
After a couple of minutes I had my database mapped and was ready to go.
Later I discovered that some many-many tables were not mapped, and found that updating/refreshing just a part of the model was a "no go" - but maybe I missed something. Also had to close/open VS2008 a couple of times because the visual table mapper "went out of business" from time to time.
I use Linq2Sql today, and the transformation to Entity framework seemed very easy.
1. I like the table layout design direct in VS2008 - also know from Access, Linq2Sql and so on - maybe you could implement this approach in OpenAccess?
I can confim a statement read in several blogs,- "The product are not mature, I will wait for version 2".
Another statement "out there" are that Linq2Sql will not have Microsofts full attention in the future, it's all about the Entity Framework from now.
Therefore I, like others, are looking for alternatives - better alternatives.
2. Microsoft are committed to support LINQ, and your roadmap show me that Telerik are going that way to, right?
3. Can you please state, from your perspective, the pro/cons on using OpenAccess instead of just "jumping the Microsoft wagon" and go with the Entity framework?
4. Microsoft have several advantages regarding integration the Entity Framework into VS2008(and other products), where do you stand here?
Have been reading a lot on ORM products "out there" and have come to the conclusion that is's all a kind of religion - it's like the old times "Netscape/IE" - "Unix, Linux, Mac or Windows" - but all we want are to map our relational date into some objects, doing a little of modifying, insert, update and delete - or the other and more abstract way around,- define our classes, interfaces, relations and create the database.
It is, in my mind, crucial that the interface between the database and the model are rock solid - I am looking for a real WYSIWYG interface, and if it could create some automated unit tests it would be news to me.
Regards,
Bo Hessner