User-1005219520 posted
Hi ctaswell,
Dynamic Data (DD) does not display GUIDs by default. In general, GUIDs are not useful for humans to enter by hand, edit, insert. If you build a DD web site using the AdventureWorksLT (AWLT) database with either Link to SQL (L2S) or ADO Entity Framework (EF)
and view the address table, the rowguid column will not be displayed. To display it, use the ScaffoldColumn attribute (passing in true).
Using the Address table of AWLT again as a sample, I add the following Address entity constructor to my partial class to initialize a new GUID. I'm now able to insert a new address into the table.
public partial class Address {
public Address() {
rowguid = Guid.NewGuid();
}
}
I don't consider this an ideal solution as a bogus GUID gets generated for each row fetched from the DB, but it does solve the problem. The EF folks seem to prefer you edit the wizard generated EDMX file and add the
StoreGeneratedPattern="Computed"
attribute to the rowguid property of Address entity in the SSDL.
<Property
Name="rowguid"
Type="uniqueidentifier"
Nullable="false"
StoreGeneratedPattern="Computed"/>
<Property
Name="ModifiedDate"
Type="datetime"
Nullable="false"
StoreGeneratedPattern="Computed"/>
There are many samples using Entity Framework in
the Dynamic Data documentation on MSDN.
The first versions of our documents had only Link to SQL
All sample contain VB and C#.
as only Link to SQL was supported at the time of writing.
We are in the process of updating the documents.
All new document will show any differences between Link to SQL and Entity Framework.
Many of the newer samples use Entity Framework, and all the new content should
show differences between the two data models.
We would appreciate your feedback on our documentation.
My blog Differences When Working with the ADO.NET Entity Framework to LINQ to SQL
might have some items to help get you started.
A new update to Dynamic Data on MSDN will show in a couple weeks.
We've added several new samples using EF and updated others.
Among many other addtions, the update shows how to use the OnSavingChanges
method in a partial class to validate all properties in an entity.
Let me know if this is something you need before the update appears.
Below is the partial class I like to use with the Address table of AWLT. Note I did cheat a bit and apply the
StoreGeneratedPattern="Computed"
attribute to the ModifiedDate property of the Address entity.
using System;
using System.ComponentModel.DataAnnotations;
namespace AdventureWorksLT2008Model {
[MetadataType(typeof(Address_MD))]
public partial class Address {
public Address() {
rowguid = Guid.NewGuid();
}
}
partial class Address_MD {
[ScaffoldColumn(true)]
public object rowguid { get; set; }
[ScaffoldColumn(false)]
public object ModifiedDate { get; set; }
[ScaffoldColumn(false)]
public object AddressID { get; set; }
}
}
