Hi Cerebrus, thank you for your answer, that's exactly what i've figured out when attempting to develop the user interface layer. i'm not under pressure anymore, but still working on this application. I'll come back with more questions if needed. thanks again! cheers, Daniela
On Feb 10, 3:04 am, Cerebrus <[email protected]> wrote: > Not sure if you still require an answer, but here's my two ¢. > > Entity Framework (EF) is just an ORM tool that helps you map the > database tables into strongly typed classes that can be used in your > code in confluence with your data access layer. If you have entity > classes defined, you do not need EF. > > On Feb 7, 7:44 pm, Dani <[email protected]> wrote: > > > > > > > > > Hi all! > > > I'm reformulating my previous question, i guess it's a bit complicated > > to read .. > > > I've got a back end library with my entities classes defined so the > > access to the database has already been taken care of. > > > Now I need to create a small web project in ASP.Net MVC3 where I can > > fit this back end library in. Then, Entity Framework is not needed (at > > least this is what I reckon). > > > My database has only two tables: > > > - Invoice > > - Detalis (with foreign key to Invoice table) > > > many thanks in advance! > > cheers, > > > Daniela -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
