ado.net-entity-data-model

This question already has an answer here: Missing “Ado.Net Entity Data Model” on Visual Studio 2013 9 answers After installed Visual Studio 2013 and create a new MVC4 internet application project : Visual Studio Doesn't have Ado.net Entity Data Model when i click on add->new item-> Why? I reinstall it but ther is no change ... uncleGe Here's an updated solution I found as I had the same problem with Visual Studio 2015: ado.net model for db is gone Visual studio 2015 Paraphrasing: Change your installation of Visual Studio 2015 and include the Microsoft SQL Server Data Tools (via Control Panel >

Suppose I have a database named MyDatabase which has two tables - MyTable1 and MyTable2 . Using the Code First approach with Entity Framework 4.x and .NET 4, I have generated a context named MyDatabaseContext which contains MyTable1s and MyTable2s . Normally, tables are accessed like MyDatabaseContext.Table1s.<Command> . In my database many tables share a couple of common fields (e.g. CreatedOn, ModifiedOn). I would like to to be able to dynamically substitute a table name so I can execute the same query against any table. What I really want (and which does not seem to be available) is

Is it possible to define primary and foreign keys for database Views in Microsoft SQL Server Management Studio? How? I'm trying to create an ADO.NET Entity Data Model to read from four old, poorly-formed database tables that I cannot modify. I've created views of just the data I need. The four views should map to a simple three-entity EDMX with one many-to-many relationship. I get this error when creating my Data Model: The table/view '...' does not have a primary key defined and no valid primary key could be inferred. This table/view has been excluded. To use the entity you will need to

I am using multiple layer project where the DataModel hosts the ADo.NET Entity model and DataAccess layer does the validation. However everytime I get a error like this The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid. I have tried connection strings <add name="SalesEntities" connectionString="metadata=res://*/SalesEntities.csdl|res://*/SalesEntities.ssdl|res://*/SalesEntities.msl;provider=System.Data.SqlClient;provider connection string="Data Source=.;Initial Catalog=Phoenix;Integrated Security=True

I know how to mark a group of fields as primary key in ADO.NET entities but i haven't found a way to declare unique constraints or check constraints. Is this feature missing on the designer or on the framework? Support for unique keys/constraints does not exist in ADO.NET Entities in v4.0, see the answer to " one-to-one association on a foreign key with unique constraint ", where Diego B Vega says: I know for sure we haven't added support for unique keys other than primary keys in 4.0. He does, however, provide a possible workaround/hack (which comes with all the normal caveats): As you are