#ado.net entity framework

Export to word using MVC 4

In previous article I had told you how to export data into excel, in this article I will tell you…

It is all perfectly fine to have a model but useless to you unless you can filter out only the information you want to send back to your page. Below I have created basic query:

        /// <summary>         /// Populates the query stem.         /// </summary>         /// <remarks>It was written to select out a new lightweight entity because it complains that it cannot create         /// a new instance of Business class. Specifically, it gives the following error:         /// The entity or complex type ‘CarnotaurusModel.Business’ cannot be constructed in a LINQ to Entities query         /// So we create dynamic lightweight instance of Business. Let’s say BusinessLW.         /// We then stuff it in a generic list and update our view to reflect this.</remarks>         public void PopulateQueryStem()         {             Int32 entityTypeStringID = (int)this.searchType;             this.query = (from b in model                           // equivalent of where clause filter on the type of business entity                           where b.Entity_type_string_id == entityTypeStringID                           select new BusinessLW                           {                               ID = b.Business_id,                               Title = b.Trading_name,                               ShortTitle = b.Search_name,                               Address = b.Address.Description,                               Postcode = b.Address.Postcode,                               Phone = b.Phone,                               // equivalent of select clause filter on trading businesses                               IsTrading = b.Is_trading == 1,                               // equivalent of select clause filter on haunted business addresses                               IsHaunted = b.Address.Address_extra.Any(e => e.Is_haunted == true)                           });         }

The Asp.net dynamic data entities web application compounds several layers into one. I know that Object Relational Mapping (ORM) is supposedly the future but when layers are not exposed, it can cause serious optimisation issues as well as making testing almost impossible. This is the case with both the ADO.NET Entity Framework (EF) model and the LINQ to SQL model. These are the only out of the box model providers availabe to Asp.net dynamic data entities web application. These do not work well, if at all with Microsoft Access.