Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>ObjectContext is not deprecated. Actually DbContext is just a layer on top of ObjectContext. DbContext API has much nicer/smaller API and is easier to work with. Also POCO entities are much cleaner. This was the reason to change code generation. If you still want to use ObjectContext and EntityObject based entities remove *.tt files under the *.edmx file. Double click the edmx file to open it in the designer. Click on the designer surface. In the properties change "Code Generation Strategy" from "None" to "Default".</p> <p><strong>EDIT</strong></p> <p>The behavior has changed a bit in the EF6 designer that ships with VS2013 (and is available for download for VS2012). If you are using EF5 the two options are: 'T4' and 'LegacyObjectContext'. If you are using EF6 the dropdown is disabled. If you would like to use ObjectContext in an EF6 app you need to use <a href="http://visualstudiogallery.msdn.microsoft.com/66612113-549c-4a9e-a14a-f629ceb3f89a">Entity Object generator for EF6</a> (note this link points just to one version of the template but there are actually a few versions depending on what you need - C# vs. VB.NET, WebSite non-WebSite - <a href="http://visualstudiogallery.msdn.microsoft.com/site/search?query=EF%206.x&amp;f%5B0%5D.Value=EF%206.x&amp;f%5B0%5D.Type=SearchText&amp;ac=2">here</a> is the list). You can find more details about changes in the EF6 tooling <a href="http://blog.3d-logic.com/2013/11/10/what-changed-in-the-ef-tooling-in-visual-studio-2013-and-visual-studio-2012-out-of-band/">here</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs ObjectContext deprecated in .NET 4.5?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPawel
    1. USPawel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs ObjectContext deprecated in .NET 4.5?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks. It's really strange that the "default" code generation strategy is not using any TT, and the default designer's modus operandi is to use DbContext TT. It would be clearer to me if it always used a TT and the default template had changed from ObjectContext to DbContext.
      singulars
      1. PO
      1. USAndré Pena
    2. COI agree it may be confusing. I think this is for historical reasons when in previous versions "default" meant without user's t4 files while "None" meant nothing because the user provides his own t4 templates. I also think that deafult actually uses t4 that are just not exposed.
      singulars
      1. PO
      1. USPawel
    3. COI filed a bug for this: http://entityframework.codeplex.com/workitem/686
      singulars
      1. PO
      1. USPawel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload