I'm in over my head here, but I'll take a stab at helping. To be honest, I must admit the bulk of my knowledge is based upon reading and research I've been doing for work I'll be getting into later this year. At best, I am reguritating what I have read, rather than giving advice from personal experience.
Based upon your description of how you are going to be working with your database, you may want to look at the ADO Entity Framework. It will quickly let you model your database in code, including entity relationship diagrams, and create classes for reading and updating the DB for you. Then you use LINQ-To-Entites in your business logic to get and update your data. This is the current approach Microsoft is pushing, so take the advice for what it is worth. Good Luck, -- R.B. Davidson On Feb 16, 9:07 am, graphicsxp <[email protected]> wrote: > Hello, > > My question might be a bit off topic, hopefully not. I'm about to > develop a WCF service that will eventually be used by all our client > applications. > I'm at the stage where I should decide what my DataContract(s), that > is my entities, are going to be. We've got the database design in > place, so I can imagine my entities will be more or less based on the > database's tables, with some modifications of course. What I'd like to > find out is what is the best way to generate my entities ? Should I > write everything by hand ? Should I create a LINQ-to-SQL file and > create my entities from there ? In fact, I would really like to have > a proper class diagram showing all my entities an associations, and > then generate the code from it. Is LINQ-to-SQL appropriate for that ? > Or should I use something else ? > > If someone has some experience in generating Data Contract(s) classes > for WCF, I'd really appreciate some insights. > > Thanks
