Pro Entity Framework 4 0 Depositfiles_9

Chia sẻ: Up Upload | Ngày: | Loại File: PDF | Số trang:21

Thêm vào BST

Báo xấu

112
lượt xem 8
download

Download Vui lòng tải xuống để xem tài liệu đầy đủ

Tham khảo tài liệu 'pro entity framework 4 0 depositfiles_9', công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả

Chủ đề:

Bình luận(0) Đăng nhập để gửi bình luận!

Lưu

Nội dung Text: Pro Entity Framework 4 0 Depositfiles_9

CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK WPF Data Binding This section discusses binding with Windows Presentation Foundation (WPF). In this example, you focus on the sales side of things, pulling in SalesOrderHeader and SalesOrderDetail information to populate a simple WPF form. If you’ve never developed an application with WPF before, don’t fear. This example doesn’t go deep into the intricacies of WPF (there are many great WPF books out there), but you get an idea of how to build a simple EF data binding application for WPF. Creating a Project Binding in WPF is quite different from a Windows form because WPF has no built-in binding controls. The first thing you need to do is create the project; in the existing solution that you’ve been using, choose File ➤ Add ➤ New Project. This opens the Add New Project dialog, show earlier in Figure 13-1. This time, however, you want to select the WPF Application template. Give it the name WPFBinding, and click OK. Just like your WinFormsBinding project, add a reference to the EF40Data project to this WPFBinding project. Before you start adding code, drag a WPF list box onto the window. Again, you aren’t going for a well-designed layout—you simply need a list box. In the code, I’ve renamed Window1 to MainWindow. You may want to do the same to avoid any confusion. Adding Some Code Let’s add some code. Modify the code behind the MainWindow to look like the following. Notice the addition of some using statements (besides the default using statements), some variable declarations at the Window level, and some code in the Loaded event for the window: using EF40Data; using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Windows; using System.Windows.Controls; using System.Windows.Data; using System.Data.Objects; using System.Collections.ObjectModel; using System.Windows.Documents; using System.Windows.Input; using System.Windows.Media; using System.Windows.Media.Imaging; using System.Windows.Navigation; using System.Windows.Shapes; namespace WPFBinding { /// /// Interaction logic for MainWindow.xaml /// public partial class MainWindow : Window { private EF40Entities context; private List soh; 245
CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK public MainWindow() { InitializeComponent(); } private void Window_Loaded(object sender, RoutedEventArgs e) { context = new EF40Entities(); soh = context.SalesOrderHeaders.OrderBy(o => o.AccountNumber).ToList(); listBox1.ItemsSource = soh; } } } Running the Project To run this project you need to set it as the default project. In Solution Explorer, right-click the WPFBinding project, and select Set as Default Project from the context menu. Press F5 to run the application. When the WPF form displays, you should immediately notice that the data in the list box doesn’t look right, as shown in Figure 13-14. Figure 13-14. WPF main form The problem in this example is much like the problem you had with the data grid in the previous example: the columns in the list box don’t know where to get the data. Sure, you bound the list box 246
CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK control using the ItemsSource property, which is the method that WPF uses to bind controls. But you haven’t defined the appropriate columns, nor have you defined how the columns get their data from the query results. In essence, you haven’t given the list box any specific instructions, so the list box by default calls the ToString method when trying to display objects. Thus, the list box displays the string representation of each source in the object. Displaying string representations of everything isn’t very useful. The fix to the problem of displaying string representations isn’t in the code, but in the WPF XAML. Switch to design view for the window, and you should see some XML in the design window. This is where you need to make your changes. Go to the window in design view and add the following code in bold in the form’s XAML window. Your results should appear similar to those in Figure 13-15. Figure 13-15. XAML window 247
CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK Before you run this code to test it, let’s look at what you’re doing. You’re adding to the list box control itself. First, you define the rows and what they look like, via the ListBox.ItemTemplate. The ItemTemplate is used to specify the visualization (visual structure) of the data objects. Inside the ItemTemplate, you use a DataTemplate, because that is what helps you specify how each item appears in your next element, the StackPanel. The StackPanel arranges each child element into a single line that can be oriented either horizontally or vertically. In this example, you want the rows laid out horizontally. You then use the TextBlock element to define your columns and display the data. However, this is just simple XAML. The key here is the Text property of each TextBlock, which allows you to specify your binding properties. The Binding property lets you specify where the TextBlock gets its data via binding. The Path property specifies the name of the entity property from which it’s bound. Now you’re ready to run the project again. Press F5; when the form displays, you should a nice listbox with two columns that display the account number and the purchase order number, as shown in Figure 13-16. Figure 13-16. Displaying account numbers and purchase orders The list box knows where it’s getting the values because you defined that in the code. You had to define the list box columns and specify where the columns get their data. Displaying Related Detail As is, the form isn’t very useful. It simply displays sales header information: account numbers and related purchase orders. Let’s modify this window a bit to display related sales detail information. With the window in design mode, size the window so that there is extra space below the list box, and place eight labels, seven text boxes, and one combo box on the window. See Figure 13-17. 248
CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK Figure 13-17. Completed form You can modify the window so that as you select on a row within the list box, related sales order detail information is displayed in the new controls you placed in the window. Displaying the details isn’t as difficult as you may imagine. After you’ve placed and arranged the controls, binding them is simple. No extra code needs to be written—in fact, the only thing you need to do is modify the TextBox elements to include the binding details. The syntax from the form in the following code example shows two ways the controls can be bound. The first method is to include a completely separate Binding child element of the TextBox element, shown in the first bold code. The second method is to include the binding within the Text property of the TextBox element, as shown in the second highlighted section of code: 249
CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK Either method works—use whichever is more readable for you. The key here is the information that shows how the binding takes place. First, notice the ElementName property, which specifies the name of the binding source object. Next is the familiar Path property, which specifies the name of the entity property from which the element is bound. Last, notice that some text boxes have a StringFormat property, which specifies how to format the string when it’s displayed in the text box. Because you’ve already placed the controls (labels, text boxes, and a combo box) on the window, the only thing you need to be concerned about is the binding information. You’re ready to test. Run the project again; and when the form displays, select the first record in the list box. The text boxes should display the related sales order detail information for the selected sales order header record in the list box. You can test this form easily. Open the form in design view, and add a button to the form. Set the Content property to Save. In the Click event, add the following code: context.SaveChanges(); Run the project again; and when the form displays, change the Tax value. (In my test, I changed the value from 1057.28 to 2057.28.) Watch the Total value when you click the Save button. It changes, doesn’t it? The Total value is a calculated column in the database, so the fact that the field on the form updates when you change and save the Tax value shows that binding is working and that the values are being saved and updated in the database. 250
CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK What you haven’t done is hook up the combo box. Guess what your homework assignment is? Yep, you get to hook up the combo box. However, I won’t leave you without a hint. You first need this declaration in the code behind the window: private List sp; Here is the code to put in the Window_Loaded event, underneath the code to get the sales order header data sp = context.SalesPersons.OrderBy(s => s.SalesPersonID).ToList(); comboBox1.ItemsSource = sp; Next, you need to modify the XAML code for the combo. The hint for this is that the SalesPerson information comes from the SalesOrderHeader, and you need to use the navigation properties to get to the contact info if you want to display the name of the sales person. Got it? As you’ve probably gathered from this chapter, data binding with the EF is flexible and powerful regardless of the application type. There are certain nuances you need to be prepared to work with depending on the environment, as you’ve seen in this chapter, such as displaying relational data in grids or working with data sources in WPF. Yet regardless of what issues you may run in to, data binding with the EF makes for rapid application development with the flexibility of working with EF objects. 251
CHAPTER 13 ■ DATABINDING WITH THE ENTITY FRAMEWORK 252
■ INDEX Index ■ SPECIAL CHARACTERS & Added state, 88 NUMERICS added value, 84 AddingNew event, 243 * syntax, 74 AdditionalContactInfo class, 181 *:* (many-to-many) association, 46, 160 AdditionalContactInfo property, 161 _ (underscore character), 162 AdditionalContactInfo table, 6 + (plus) button, 244 AdditionalContactInfo view, 35 = assignment, 68 AddObject method, 88, 243 => operator, 68 Address textbox, 204 1:* (one-to-many) type, 46 AddToProductModel method, 89 1:1 (one-to-one) type, 46 AdventureWorks database, 15, 110, 112, 152, 169, 188 ■A AdventureWorks2008Entities class, 67, 83 AdventureWorks2008Entities objects, 58, 86 AcceptAllChanges method, 85 AdventureWorksEntities class, 205–206 AcceptAllChangesAfterSave( ) method, 85 AdventureWorksModel value, 189 Active property, 42 Age column, Rider table, 149 Add Association dialog box, 117 All enumeration, 195 Add button, 241–242 AllRead enumeration, 195 Add Code Generation Item option, 138–139 AllWrite enumeration, 195 Add foreign key properties to the entityname app.config file, 58, 78, 219, 224, 231 Entity check box, 116–117 Append Only enumeration, 84 Add Function Import dialog box, 107 assembly directive, 135 Add Function Import option, 37, 106–107 Association element, 52–53 Add menu option, 24 Association item, 147 Add method option, 47 Association object, 22 Add New Data Source link, 233 association set, 112 Add New Item dialog box, 14, 127–128, 138–139, Association Set Name property, 112 188, 190 association sets, 112 Add New Project dialog box, 170, 202, 245 associations Add Reference button, 235 adding, 116–117 Add Reference dialog box, 170, 230–231, 235 of CSDL section, 55–56 Add Reference option, 230 for entities, 45–46 Add References dialog box, 171 first class, 113 Add Service Reference dialog box, 203–204, 207, foreign keys (FK), 119 233 independent, 119 Add Service Reference option, 202–203 rules for generating, 46 Add Service Reference wizard, 205 AssociationSet element, 53, 118 Add tab, Update Wizard, 97 AssociationSetMapping element, 57, 112 AddContactProcedures.sql file, 209 253
■ INDEX Average operator, 80 adding references, 170–171 AWCodeOnlyData project, 222 building project, 176–180 AWCodeOnlyUI project, 222 connecting DataGridView control, 178– AWModel.cs class, 172–173, 176 179 AWService.svc file, 192, 204 loading some rows, 177–178 running application, 179–180 ■B configuration classes adding, 172 binary assembly, 217, 219 creating, 173–175 Binding element, 249 data project, 168–170 binding, entity classes, 232 installing EF Feature CTP, 167–168 Binding Navigator counter, 244 method to create EDM, 32–33 BindingNavigator control, 236–238 POCO information, 180–183 BindingSource control, 237, 239, 242, 244 testing model, 175–176 Brand entity, 148 User-Interface (UI) project, 170–173 BrandID column, 149 CodeOnlyData project, 171, 181 BrandName column, Brand table, 149 CodePlex web site, 13 breakpoint, 65, 87 Column column, 47 Build menu, 218 column mapping, 47 Build Solution option, 218 column, Rider table, 149 BusinessEntity record, 103 Columns property, 240 BusinessEntity table, 35 CommandText property, 78 BusinessEntityID property, 47 common language runtime (CLR) types, 83 button2 button, 208 Community Technology Preview, 165 compilation, verifying for model-first design, 152 ■C Complex Property, Add menu, 43, 161 Complex Property option, Add menu, 24 Cascade option, OnDelete property, 115 complex types cascading deletes, 45 of entities, 40–45 catch block, 220–221, 226 handling of with model-first design, 161–162 CellPhone property, 42, 161 support for in version 4.0, 11 change tracking, in POCO, 182–183 support in POCO, 181 Choose Model Contents dialog box, 124 complex types node, 41–42, 161 Choose Toolbox Items dialog box, 165 conceptual layer, 56 Choose Your Data Connection dialog box, 152 conceptual mapping, 5 Choose Your Data Connection option, 189 conceptual model, 5 Choose Your Database Objects dialog box, 110, conceptual model node, 41 113, 124, 210, 212 Conceptual Schema Definition Language (CSDL), Clarius Corporation, 128 40, 49, 117–118, 138, 169, 218 Class entity, 148 of Entity Data Model Runtime section Class Library project, 110, 168 associations, 55–56 Class1.cs file, 124 EntityType element, 54–55 classes, generated by Entity Data Model, 58–61 overview, 53 ClassID column configuration classes, code-only model design Class table, 150 adding, 172 Rider table, 149 creating, 173–175 ClassName column, Class table, 150 connection exceptions, 223–225 Click event, 64, 75, 89, 91, 122, 206–207, 243–244, Connection Properties dialog box, 15–16 250 Connection String property, 219 closing braces, 65, 132 section, 78, 224 CLR (common language runtime) types, 83 Console.WriteLine method, 131 code-only, 167–186 254
■ INDEX Contact class, 32, 174–175, 181 model-driven, 6–8 Contact Employees collection, 122 overview, 5 Contact entity, 43, 45 data binding with Entity Framework (EF), 229– Contact object, 120–121, 123 251 Contact property, 182, 214 in windows forms, 229–244 Contact table, 6, 179, 215 add function, 242–244 ContactConfiguration.cs class, 172–173 creating data sources, 232–236 ContactID FK property, 122 creating new form, 229–232 ContactID property, 112, 114, 123 creating project directory, 229 Contacts object, 122 delete function, 244 Content property, 250 form code, 236–238 Content tab, 198 grid control, 238–242 ContextBuilder variable, 176–177 save function, 244 Contexts region, 58 WPF data binding, 245–251 Copy to Output Directory property, 218 adding code, 245 copy/paste error, 131 creating project, 245 CounterStuff class, 133 displaying related detail, 248–251 Create Complex Type option, 41 running project, 246–248 Create Database Wizard, 10, 152 Data Connection page, 17 create, read, update, delete (CRUD) operations, Data Connection screen, 27 215 Data Definition Language (DDL), 29–31, 153–154, CREATE TABLE statement, 164 163 Create, Update, Delete (CUD) oprerations, 83 Data Flow Diagram (DFD), 4 CreateObject method, 183 data integrity, 53 CreateProductModel method, 89 Data node, 14 CRUD (create, read, update, delete) operations, Data object templates, 14 215 Data Service template, 190–193 .cs file, 193 Data Source Configuration Wizard, 234 C-S Mapping Content section, 152 Data Sources Configuration Wizard, 233 C-S Mapping Specification Language (MSL) data sources, creating data binding in windows section, of Entity Data Model Runtime forms, 232–236 section, 56–57 Data Sources window, 232–233, 236, 238 CSDL. See Conceptual Schema Definition database Language generating after creating EDM, 27–31 .csdl extension, 218 generation rules CsdlToSsdlAndMslActivity, 165 for associations, 160 CUD (Create, Update, Delete) oprerations, 83 for tables, 159–160 Custom Tool property, 140–141 generation script customization, 163–166 Customer entity, 26 Database binding, 234 CustomerAddress property, 25 Database data source, 236 CustomerCity property, 25 Database Generation Wizard, 159, 163 CustomerFirstName property, 24 Database Generation Workflow property, 163 CustomerID property, 25–26 database model, 7 CustomerLastName property, 25 Database Objects page, 19–20 CustomerPhone property, 25 Database Schema Name property, 163 CustomerState property, 25 Database Script Generation section, 163 CustomerZipCode property, 25 Database type, 233 database-driven, data access, 5–6 ■D database-first, method to create EDM, 14–19 data-binding, 232 data access, comparison of options for DataGrid control, 238 database-driven, 5–6 255
■ INDEX DataGridView control, connecting in code-only .edmx file, 47–49, 97, 101, 140, 158 model design, 178–179 EF. See Entity Framework DataPropertyName property, 241 EF40CreationScript.sql file, 123 DataReader class, 2 EF40Data node, 235 DataReader object, 3–5 EF40Data project, and relationships, 123 DataSet class, 2 EF40Data solution, 231 DataSet object, 4–5 EF40Entities data model, 242 DataSource property, 178–179, 239 EF40Template.tt, 143 DataTemplate, 248 EF4FeatureCTP2.exe file, 167 datetime variables, 120 EFDemo.Designer.cs file, 58 DDL (Data Definition Language), 29–31, 153–154, ElementName property, 250 163 elements debug attribute, template directive, 129 association, of SSDL section, 52–53 deferred execution, of query, 79 EntityType DeferredLoadingEnabled property, 182 of Conceptual Schema Definition element, 51, 53 Language (CSDL) section, 54–55 Delete button, 105, 242, 244 of Storage Model (SSDL) section, 52 delete function, 105 EmailAddress property, 42 Delete operation, 38 EmailAddress2 property, 181 Delete procedure, 216 Employee class, 32 Delete tab, Update Wizard, 97 Employee collection, 120–122 deleted value, 84 Employee entity, 47 DeleteFunction element, 102 Employee object, 120–123 DeleteObject( ) method, 91–92, 105 Employee property, 46 DeletePerson procedure, 97, 100 Employee role, 56 Dependent element, 53 Employee table, 6, 35, 52, 112, 207 Dependent field, 116 Employee type, 207 dependent objects, adding, 120–121 Employee view, 35 Dependent Property field, 116 EmployeeAddresses property, 213 derived type, 32 EmployeeConfiguration.cs class, 172, 174 design view, 247 Employee.Contact property, 123 design window, 247 Employee.cs class, 222 Designer surface, Designer tool, 37 Empty Model option, 147 Designer window, 20–22, 35–37, 217 Empty model template, 22 designer.cs. extension, 58 EndEdit method, 243–244 detached value, 84 EndProperty elements, 57 DetectChanges( ) method, 85 entities DetectChangesBeforeSave enumeration, 85 adding, 87–89 DFD (Data Flow Diagram), 4 associations for, 45–46 Discover button, 203–204 complex types, 40–45 DisplayMember property, 178 creating in empty model with model-first DoCounter method, 133 design, 148–150 Download button, 167 deleting, 91 DROP statements, 153, 157 features of, 8 DROP TABLE statement, 164 navigation properties of, 9, 46–47 and ObjectContext class ■E ObjectStateEntry class, 83–84 tracking and saving changes, 84–85 Edit Columns dialog box, 240 relational inserts, 89–91 EDM. See Entity Data Model scalar properties, 40 EDM Designer, 9 updating, 85–87 EdmFunctionAttribute attribute, 11 256
■ INDEX Entities region, 59 POCO support, 10 entity classes, binding, 232 related object-deferred loading, 10 Entity connection string section, 17 Entity Framework (EF) 3.5 Entity Data Model (EDM), 13–61 and relationships, 110–113 checking, 213–214 restrictions in, 180 classes generated by, 58–61 Entity Framework (EF) Feature CTP, 167–168, creation methods, 13 170, 176 code-only, 32–33 Entity Framework (EF) functions, 98–99 database-first, 14–19 Entity Framework (EF) project, building for model-first, 22–26 performance, 216–219 Designer window, 35–37 Entity Framework EDM, 200 entities, 38–47 Entity item, 147 associations for, 45–46 entity key, 40 complex types, 40–45 Entity Key property, 24 navigation properties of, 46–47 Entity Model Code Generator tool, 11 scalar properties, 40 Entity Name property, 19–20 generating schema and database, 27–31 Entity object, 22 making plural or singular names, 19–21 Entity property, 23–24 Mapping Details window, 38–47 Entity Relationship Model (ERM), 3–4 Model Browser window, 37 entity set, 38 Runtime section parts, 50–57 Entity Set Name property, 19–20, 39 CS MSL section, 56–57 Entity Set names, 20 CSDL section, 53–56 Entity SQL, option to query Entity Data Model, SSDL section, 50–53 74–76 and stored procedures, 93–97 entity type, 38 table inheritance, 31–32 EntityClient updating, 209–213 EntityCommand, 78 viewing XML of, 48–50 EntityConnection, 77–78 Entity Data Model (EDM) template, 14, 22 overview, 76 Entity Data Model (EDM) Wizard, 11, 14–15, 22, EntityClient Provider for the Entity Framework, 58, 110, 147, 231 12 Entity Designer Database Generation Power Pack EntityCommand class, 77 tool, Microsoft, 165 EntityConnection class, 77, 173, 176 Entity Framework (EF), 208 EntityContainer element, 51, 53, 67, 235 comparison of data access options EntityContainerMapping element, 57 database-driven, 5–6 EntityFramework, 67 model-driven, 6–8 EntityFunctions class, 11 overview, 5 EntityKey class, 91 database-independent support, 12–13 EntityKey values, 83 entity features, 8–9 EntityModelCodeGenerator tool, 58, 140 need for, 2–5 EntityObject class, 180 overview, 4–5 EntityObject Generator template, 137–138 and T4 templates, 137–142 EntitySet element, 32, 160 version 4.0 features EntitySet name, 91 complex types, 11 EntitySet property, 32, 213 LINQ-to-entities function support, 11 EntitySetMapping element, 57 model browser improvements, 11–12 EntitySetRights enumeration, 195 model-first support, 10 EntitySets, 53 object-layer code generation, 11 EntitySQL exceptions, 226–227 overview, 10 EntitySQLException class, 226 plurality naming, 11 EntityState property, 84 257
■ INDEX EntityType element, 11 Form1.cs file, 64 of CSDL section, 54–55 FROM clause, 66–67, 69–70, 99 of SSDL section, 52 from operator, 70 EntityType names, 20 function, 11 EntityType property, 213 Function elements, 98, 102 EntityTypeMapping element, 57, 101–102 Function Import mapping, 106 enumerable object, 87 functions ERM (Entity Relationship Model), 3–4 delete, 105 eSqlBlast tool, 227 insert, 102–104 Events button, 241 mapping of, 99–102 Exception class, 221–223 select, 105–106 exception handling update, 104 connection exceptions, 223–225 using in queries, 106 EntitySQL exceptions, 226–227 ■G Exception class, 221–223 overview, 219 GDW (Generate Database Wizard), 152, 158–159 query exceptions, 225–226 Generate Database from Model item, 152 try/catch blocks, 219–220 Generate Database Script from Model option, 27– using statement, 221 28 Exception.Message property, 222 Generate Database Wizard (GDW), 152, 158–159 ExecuteReader method, 78 GenerateDatabaseScriptWorkflow item, 165 execution of query get accessor, 183 deferred, 79 GetObjectByKey method, 91 immediate, 80–81 Go button, 204 overview, 78–79 graph, Entity Framework, 9 expressions, Lambda, 68 grid control, data binding in windows forms Extensible Markup Language. See XML displaying data with, 239–241 extension attribute, output directive, 129 navigating relation in, 241 extension directive, 130 overview, 238 testing, 241–242 ■F group operator, 72–73 finally block, 220–221 ■H Finish button, 20 first class associations, 113 HAVING clause, 66 First operator, 80, 87 HumanResources.Employee table, 114 FirstName column, Rider table, 149 Fixed Length property, 24 ■I FK. See foreign keys FK_SalesOrderHeader_SalesPerson_SalesPersonI ICollection type, 182–183 D key, 57 Id field, 161 FlagsAttribute attribute, 85 ID property, 23, 25 for loop, 131–132 IEntityWithChangeTracker interface, 180, 182– foreach block, 65 183 foreach line, 65 IEntityWithKey interface, 180 foreach statement, 70, 79 IEntityWithRelationships interface, 180, 182–183 foreign keys (FK), 30, 53, 112, 116 immediate execution, of query, 80–81 in relationships include foreign key columns in the model option, adding dependent objects, 120–121 113, 125 manually setting, 121–122 independent associations, 119 overview, 119 inheritance, 7–8, 22 setting automatically, 122–123 258
■ INDEX inherits attribute, template directive, 129 ListBox.ItemTemplate, 248 InitializeService method, 194 Load event, 177, 179, 222 inline code directives, 131 Loaded event, 245 INNER JOIN, 66 logical model, 5 InnerException property, 221–222, 226 ■M Insert button, 102–104 insert function, 102, 215 Main method, 133 Insert operation, 38 ManagerID property, 112, 114 INSERT statement, 90 Many relationships, 109 InsertFunction element, 102 many-to-many (*:*) association, 46, 160 InsertPerson function, 99 mapping InsertPerson procedure, 98, 103 functions, 99–102 Installed Templates list, 14, 165 stored procedures for performance, 215–216 IntelliSense, directives of, 129 Mapping Details window, 37–47, 99, 215 Internet Options dialog box, 198 mapping element, 57 IObjectSet interface, 173 mapping fragment element, 57 IQueryable interface, 70–71, 76 mapping layer, 56 IsComposable attribute, 98 mapping schema language, 218 IsIdentity( ) property, 174 mapping specification language (MSL), 49, 101, isNew variable, 243 119, 158 IsRequired property, 174–175 mapping warnings, 151 IsSupportTeam column, Team table, 149 Mapping window, 37 ItemDescription property, 25 mappings, creating with model-first design, 152– ItemID property, 25–26 159 ItemName property, 25 Max Length property, 24 ItemsSource property, 247 Max operator, 80 ItemTemplate, 248 MaxLength property, 174–175 IValidator class, 142–143 MergeOption enumeration, 84 Message property, 221–222, 226 ■J MessageBox class, 220 join operator, 73 Metadata Artifact Processing property, 217–219 join syntax, 74 metadata files, EDM, 49 MetadataException class, 225 ■K method-based, syntax to query EDM, 68–69 Microsoft.Data.Entity.Ctp assembly, 171 Key element, 52, 55 Microsoft.Data.Entity.Ctp component, 170 Microsoft.Data.Entity.Design.DatabaseGeneratio ■L n namespace, 165 Microsoft.Data.Objects.ContextBuilder class, 176 Lambda expressions, 68 Microsoft.SqlServer.ConnectionInfo class, 135 language attribute, template directive, 129 Microsoft.SqlServer.Management.Sdk.Sfc, 135 language directive, 130 Microsoft.SqlServer.Smo, 135 Language INtegrated Query. See LINQ MiddleName column, Rider table, 149 lass Library project, 145 MidName column, 3 lazy loading, in POCO, 182 Model Browser, 105–106 LINQ (Language INtegrated Query), 69, 207 model browser LINQ (Language Integrated Query)-to-Entities improvements to in version 4.0, 11–12 function, 11 and stored procedures, 97–98 LINQ (Language Integrated Query)-to-Entities Model Browser tab, 211 query, 69–74 Model Browser window, 37, 41, 161 List object, 80 model contents option, 14–15 259
■ INDEX model-driven, data access, 6–8 None enumeration, 85, 195 model-first None option, OnDelete property, 115 database generation rules, 159–160 NoTracking enumeration, 84 database generation script customization, n-tier development 163–166 overview, 187 design WCF Data Service creating Associations and Navigation building, 187–194 properties, 150 consuming, 201–208 creating conceptual model, 145–147 testing, 194–201 creating entities in empty model, 148–150 n-tier environment, 188 creating mappings and database, 152–159 Nullable property, 24 overview, 145 ■O saving model, 151 verifying compilation, 152 Object data source, 235 handling of complex types, 161–162 object materialization, 83 method to create EDM, 22–26 object names of EDM, making plural or singular, overview, 145 19–21 support for in version 4.0, 10 Object type, 233–234 modeling applications, others vs. Entity ObjectContext cache, 84 Framework, 3–4 ObjectContext class, 33, 58 ModelName.edmx.sql file, 29 and entities, 83–85 ModificationFunctionMapping element, 102 and syntax to query EDM, 67 modified value, 84 object-layer code generation, support for in ModifiedDate column, 87 version 4.0, 11 ModifiedDate property, 86, 88 ObjectQuery class, 84, 173 ModifyDateTime property, 25 ObjectQuery type, 76 Motocross EDM, 163 ObjectQuery, 238 MSL (mapping specification language), 49, 56–57, Object-Relational Mapping (ORM), 4 101, 119, 158 ObjectResult class, 238 .msl extension, 218 ObjectResult, 238 multiplicity attribute, 45, 109 ObjectSet class, 65, 173 ObjectStateEntry class, and entities, 83–84 ■N ObjectStateManager class, 84–85 Name association, 56 ObjectStateManager object, 83 Name attribute, 52 OnDelete property, 45, 115 Name property, 88, 236, 243 One relationships, 109 namespace directive, 135 one-to-many (1:*) type, 46 Namespace element, 54 One-to-Many association, 112, 160 navigation properties, 46–47, 112 one-to-one (1:1) type, 46 navigation property, 9 one-to-one association, 160 Navigation Property check box, 117 one-to-one mapping, 6 NavigationProperty element, 55 one-to-zero association, 160 NET Framework Data Provider for SqlClient for open bracket, 132 Entity Framework, 12 Open With dialog box, 48, 117, 152 .NET/COM assembly, 235 Open With option, 117, 152 New Connection button, 15 Operator column, 47, 100 New Item option, 14 ORDER BY clause, 74 new keyword, 121 Order entity, 26 New Project dialog box, 14, 188, 229–230 Order type, 39 NHibernate, 4 orderby clause, 70 non-derived type, 32 OrderBy method, 68 260
■ INDEX orderby operator, 70 Product class, 90 OrderID property, 25 Product Model Binding Navigator, 244 ORM (Object-Relational Mapping), 4 Product Model ID, 244 OUTER JOIN, 66 Production.Product table, 87 output directive, 129 Production.ProductModel table, 87 overwrite warning, 157 ProductModel class, 88, 236, 244 OverwriteChanges enumeration, 84 ProductModel column, 241 ProductModel entity, 237, 242 ■P ProductModel node, 236 ProductModel object, 89, 243 p variable, 75 ProductModel table, 87, 244 element, 99 productModelBindingNavigationSaveItem Parameter/Column column, 100 button, 243 PasswordHash property, 174 productModelBindingSource, 239, 242–243 PasswordSalt property, 174 ProductModelID column, 90, 244 Paste option, 231 ProductModelID property, 236 Path property, 248, 250 ProductModelID value, 90–91 People entity, 104 ProductModelName column, 241 People for the Entity Set Name property, 20 Products class, 238–239, 244 people variable, 70 Products entity, 236 performance tuning Products node, 236 building Entity Framework project, 216–219 productsBindingSource, 239, 241 stored procedure mapping, 215–216 ProductSubCategory entity, 236 Person class, 59 ProductSubCategoryName column, 241 Person entity, 46–47 project directory, creating data binding in Person object, 103 windows forms, 229 Person record, 103 Projects tab, 171, 230 Person role, 56 Properties page, 23, 36 Person table, 35, 52, 103 Properties pane, 46 PersonDemographics view, 35 Properties window, 37, 44, 163, 217, 232, 241 physical model, 5 Property column, 100 Plain Old CLR Objects (POCO), 32–33, 168, 170 Property element, 52 change tracking, 182–183 Provider attribute, 51 complex-type support, 181 ProviderManifestToken attribute, 51 lazy loading, 182 proxy instance, 182 overview, 180 ProxyCreationEnabled property, 183 support for in version 4.0, 10 plurality naming, support for in version 4.0, 11 ■Q Pluralize or singularize generated object names checkbox, 19, 212 queries, using functions in, 106 pluralize or singularize generated object names query exceptions, 225–226 option, 113, 125 query execution plus (+) button, 244 deferred, 79 POCO. See Plain Old CLR Objects immediate, 80–81 PreserveChanges enumeration, 84 overview, 78 primary key query variable, 79 constraint, 30 query-expression, syntax to query Entity Data derived type, 160 Model (EDM), 63–67 non-derived type, 159 querying Entity Data Model (EDM) Principle element, 53 EntityClient Principle field, 116 EntityCommand, 78 Principle Key field, 116 EntityConnection, 77–78 261
■ INDEX overview, 76 RiderID column, Rider table, 149 overview, 63 role attribute, 45 query execution rowguid property, 88 deferred, 79 RowPrePaint event, 241 immediate, 80–81 RSS Feed feature, Internet Explorer, 198 overview, 78 Runtime section of Entity Data Model querying options Conceptual Schema Definition Language Entity SQL, 74–76 (CSDL) section EntityClient, 76–78 Associations, 55–56 LINQ to Entities, 69–74 EntityType element, 54–55 overview, 69 overview, 53 syntax CS Mapping Specification Language (MSL) method-based, 68–69 section, 56–57 and ObjectContext class, 67 overview, 50 overview, 63 Storage Model (SSDL) section query-expression, 63–67 Association element, 52–53 EntityType element, 52 ■R overview, 50 ReadMultiple enumeration, 195 ■S ReadSingle enumeration, 195 Reference.cs file, 205 SalesOrder entity set, 39 references, code-only model design, 170–171 SalesOrderDetail entity type, 39, 245 references dialog box, 170 SalesOrderHeader entity type, 39, 245, 251 References node, 170, 202, 230 SalesPerson entity, 39, 184, 200, 251 Referential Constraint dialog box, 116 SalesPerson property, 213 ReferentialConstraint element, 53, 118–119 SalesPerson type, 39 reflector tool, 217 SalesPersonConfiguration.cs class, 184–185 Refresh tab, Update Wizard, 97 SalesPerson.cs class, 183 RegisterConfig method, 186 SalesPersons property, 214 related object-deferred loading, support for in SalesTerritory data, 196 version 4.0, 10 SalesTerritory property, 214 relational inserts, 89–91 SalesTerritoryConfiguration.cs class, 184, 186 relationships SalesTerritory.cs class, 184 adding association, 116–117 Save button, 242, 244, 250 direction of, 53 SaveChanges event, 244 EF40Data project, 123 SaveChanges( ) method, 86, 88, 90, 92, 99, 103, in Entity Framework (EF) 3.5, 110–113 105, 122, 219, 244 foreign keys SaveChanges(Boolean) constructor, 84–85 adding dependent objects, 120–121 SaveChanges(SaveOptions) constructor, 85 manually setting, 121–122 SaveOptions method, 85 overview, 119 SaveOptions overload, 85 setting automatically, 122–123 scalar properties, 25, 42 overview, 109–110 scalar properties, of entities, 40 Referential Constraints, 116 Scalar Property, Add menu, 24, 40, 42 WinForms project, 113–116 scalar property data type, 40 XML differences from version 3.5, 117–119 Scalar Property option, 24, 148 REST (REpresentational State Transfer), 194, 201 scalar property types, 35 restrictions, in Entity Framework (EF) 3.5, 180 ScalarProperty element, 57 Results window, 87–88, 90 schema attribute, 98 Rider entity, 148 Schema element, 51, 54 Rider table, 160 schema, generating after creating EDM, 27–31 262
■ INDEX schema overwrite warning, 28 SSMS (SQL Server Management Studio), 85–86, scope, of T4 code 158 example project, 133–134 StackPanel, 248 listing SQL databases, 135–137 Storage Model (SSDL) section, of Entity Data overview, 132 Model Runtime section returning computer's processes, 134–135 Association element, 52–53 sealed class, 182 EntityType element, 52 Select button, 105–106, 108 overview, 50 SELECT clause, 66–67, 69–70 Storage Schema (SSDL), 28, 158 option, 99 .Store appendage, 54 select operator, 70 store command, 69 SELECT statement, 74, 79, 87 store layer, 56 SelectedIndexChanged event, 178–179 store schema definition language (SSDL) file, 49, SelectedValue property, 179 218 SelectPerson procedure, 97, 106 stored procedures Sequence Control Workflow, 165 delete, 105 Server Management Objects (SMO), 136 and Entity Data Model (EDM), 93–97 Service type, 233 Entity Framework (EF) functions, 98–99 ServiceReference1 node, 205 insert, 102–104 services mapping for performance, 215–216 adding references, 202–206 Model Browser, 97–98 utilizing, 206–208 overview, 93 Services in Solution option, 203–204 select, 105–106 set accessor, 183 update, 104 Set as Default Project option, 246 Stored Procedures node, 97, 210–211 SetEntitySetAccessRule method, 195 StoreGeneratedPattern property, 40, 150 Settings button, 198 string data types, 55 Settings dialog box, 198 String scalar properties, 36, 40 SharePoint objects, 233 StringFormat property, 250 SharePoint site, 233 Summary and Settings dialog box, 157 SharePoint type, 233 Summary and Settings form, 153 Show All Files button, Solution Explorer, 205 Summary and Settings screen, 153–154 Show Data Sources option, 232 .svc file, 192 singleton value, 87 System.Activities.Components tab, 165 SMO (Server Management Objects), 136 System.Data assembly, 171 SOAP Service Description Language (SSDL), 98 System.Data.Entity namespace, 231 Solution Explorer window, 159, 165 System.Data.Entity reference, 191 SPRINT.net, 4 System.Data.EntityClient namespace, 76 .sql file, 158–159 System.Data.Objects namespace, 65, 83 SQL Server Management Studio (SSMS), 85–86, System.Data.Objects.DataClasses namespace, 83 158 System.Data.Services.Web reference, 191 SQL Server Profile, 87 System.Data.SqlClient provider, 51, 63 SQL Server Profiler, 86–87, 90, 103–105, 108 System.Exception namespace, 221 SQL Server query, 67 System.ServiceModel.Web reference, 191 .sql window, 158 System.Windows.Forms namespace, 236 SQLConnection class, 176 ■T SqlConnection variable, 177 SqlFunctions class, 11 T4. See Text Template Transformation Toolkit SSDL (SOAP Service Description Language), 28, table column mapping, 47 49, 98, 158, 218 Table name, derived type, 160 .ssdl extension, 218 Table name, non-derived type, 159 263
■ INDEX table-per-hierarchy option, 31 T-SQL query, 66 table-per-type option, 31 T-SQL statement, 90 TablePerTypeStrategy.xaml file, 165 .tt file, 165 Tables node, 210 Turn on feed reading view checkbox, 198–199 Team entity, 148 Type attribute, 55 TeamID column, Rider table, 149 Type property, 24 TeamID column, Team table, 149 ■U TeamID property, 150 TeamName column, Team table, 149 UDF (user-defined function), 98 template directive, 129 UI (User-Interface) project for code-only model Test Connection button, 16 design, 170–173 Text File template type, 127 UML (Unified Modeling Language), 4 Text property, 248–249 unchanged value, 84 Text Template Transformation Toolkit (T4) code underscore character (_), 162 generation Unified Modeling Language (UML), 4 customization example, 142 UnitMeasure column, 244 overview, 127 UnitMeasure entity, 236 scope of code UnitMeasure table, 244 example project, 133–134 UnitMeasure1 column, 244 listing SQL databases, 135–137 Update button, 104 overview, 132 update function, 104 returning computer's processes, 134–135 Update Model from Database option, 96, 209–210 templates Update Model Wizard, 11 adding template using Visual Studio 2008, Update operation, 38 127–128 Update Wizard, 96–97 and Entity Framework (EF), 137–142 UpdateFunction element, 102 installing T4 Editor, 128–129 UpdatePerson procedure, 97, 100 overview, 127–132 Use Original Value checkbox, 215 writing T4 code, 129–132 user-defined function (UDF), 98 TextBlock element, 248 User-Interface (UI) project for code-only model TextBox element, 249 design, 170–173 TextBox elements, 249 using block, 221 TextFile1.txt file, 127 using statement, for exception handling, 221 TextTemplate.tt file, 127–128 throw statement, 220 ■V Title column, 87 Title value, 85–86 VALUE clause, 75 ToArray operator, 80 ValueMember property, 178 ToDictionary operator, 80 Value/Property column, 47 TODO comment, 194 version 4.0 features, 10–12 ToList operator, 80 Visual Studio Class Library project, 123 ToLongDateString method, 226 Visual Studio environment, 158 ToLookup operator, 80 Visual Studio Server Explorer window, 158 Toolbox, Designer tool, 22, 37, 147 Visual T4 utility, Clarius, 128 Toolbox window, 161, 165 Tools menu, 198 ■W ToShortDateString method, 226 warnings, mapping, 151 ToString method, 247 WCF. See Windows Communication Foundation Total value, 250 Web option, 190 try block, 219–221 WHERE clause, 66, 70, 199 try/catch blocks, for exception handling, 219–220 264