Update 1/11/08: Between beta 2 and beta 3 there was a breaking change in the way events are fired during codegen. The metadata item that is being generated is no longer supplied as the "sender" of the event. Instead it comes in the TypeSource property of the eventArgs passed to the event handler. The code below has been modified to reflect this change. Thanks to hannah39 for pointing out the issue.
In response to the recent Entity Framework beta 2 release, I've gotten a question or two about how to take advantage of the new CodeGen Events feature, because we don't seem to have any good samples available to help folks wrap their head around this one. Then someone posted a question to the EF forum the other day asking if it's possible to add custom attributes to the generated classes, and I thought, "Aha! Two birds to be taken down with one stone." Even better, I sent a quick message to one of my teammates, Jeff Reed, who responded with a sample that was exactly what I was looking for making my job especially easy.
The first thing you need to know about using CodeGen events is that both edmgen.exe, the commandline tool for things like generating EF classes from a conceptual schema, and the new EF designer integrated with visual studio are built on top of a public API which you can use in your own programs, and when you use the API you can exercise more control over the process. The namespace where this API lives is System.Data.Entity.Design, and the references docs for it are now available online.
The simplest way to use this is to just write a little console app which would replace edmgen.exe for the purpose of generating your classes. Basically you create an instance of EntityClassGenerator, register an event handler for the OnTypeGenerated or OnPropertyGenerated event, and then call the GenerateCode method passing in either two strings with the name of an input file (your CSDL) and an output file (which will contain the generated code) or an XMLReader for input and a TextWriter for output. The event handler receives an eventArgs instance which not only describes the type or property being generated but also contains members which can be modified in order to affect what is output.
So, for a simple example, we can add an attribute called "MyFooAttribute" to the class generated for each Entity type in the CSDL file. The code would look something like this:
const string MyAttributeName = "MyFooAttribute";
static void Main(string args)
string schema = @"
<Schema Namespace='CNorthwind' Alias='Self'
<PropertyRef Name='CustomerID' />
<Property Name='Address' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='City' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='CompanyName' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='ContactName' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='ContactTitle' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='Country' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='CustomerID' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='Fax' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='Phone' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='PostalCode' Type='String' MaxLength='1024' Nullable='false' />
<Property Name='Region' Type='String' MaxLength='1024' Nullable='false' />
<EntitySet Name='Customers' EntityType='Self.Customer' />
using (XmlReader reader = XmlReader.Create(new StringReader(schema)))
StringWriter codeWriter = new StringWriter();
EntityClassGenerator generator = new EntityClassGenerator();
generator.OnTypeGenerated += new TypeGeneratedEventHandler(AddAttributeToType);
IList<EdmSchemaError> errors = generator.GenerateCode(reader, codeWriter);
string generatedCode = codeWriter.ToString();
// prove that the attribute was generated
private static void AddAttributeToType(object sender, TypeGeneratedEventArgs eventArgs)
StructuralType structuralType = eventArgs.TypeSource as StructuralType;
if (structuralType != null && structuralType.Name.Equals("Customer"))
CodeAttributeDeclaration attribute = new CodeAttributeDeclaration(MyAttributeName);
If you have Orcas Beta 2 with the EF Beta 2 installed, you can create a new console application, add a reference to system.data.entity.dll and system.data.entity.design.dll and then paste this code into VS and everything should compile and run nicely.
If you decide to play around with this, you'll want to take a look at the documentation for the members of TypeGeneratedEventArgs which will tell you that not only can you add attributes, but you can also set a base type or add interfaces or members to the type. And don't forget to take a look at the docs for PropertyGeneratedEventArgs which shows that you can add attributes to properties as well as additional statements that will appear in the getter or setter of the property. In several cases, these members take CodeDom classes as arguments, and you can find more info about the CodeDom online as well.
I've had this post kicking around in my inbox for a while but hadn't got round to consuming it. It talks...
wow thats realy amazing!!
is it possible to hang on the Events of Code-generation in Visual Studio 2008 (Beta 2)?
(Custom Tool: EntityModelCodeGenerator)
Maybe with an AddIn ?
This looks exactly like what I have been looking for but I can't get it to work with Visual Studio 2008 and Beta 3 of the Entity Framework. Did something change?
More info: The error is on
Yes, it looks like there was a breaking change in between beta 2 and beta 3 which somehow got lost.
This line in the AddAttributeToType event handler:
StructuralType structuralType = sender as StructuralType;
needs to be changed to:
StructuralType structuralType = eventArgs.TypeSource as StructuralType;
I'll update the code in the blog entry above. Thanks for pointing this out.
In previous posts, I’ve described CSDL annotations , how to extract CSDL from EDMX and introduced you
The first release of Entity Framework supports explicit loading. This means that if you are navigating
The Entity Framework enables developers to reason about and write queries in terms of the EDM model rather than the logical schema of tables, joins, foreign keys, and so on. Many enterprise systems have multiple applications/databases with varying degrees
Part of the Entity Framework FAQ . 2. Architecture and Patterns 2.1. Does Entity Framework have support
Code works fine. I would like to do one more thing though. I would like to remove the Browsable(false) attribute from EntityReference properties.
Can anybody help?
The mechanisms for customizing codegen in v1 are fairly limited, and I don't know of any way to use them to remove at attribute. In v2 we hope to create a much more flexible system which would support this kind of thing as well as many more customizations.
In the meantime your alternatives are probably something like this:
1) Modify the output of codegen by hand or with some postprocessing script. (Not what I would really recommend.)
2) Use a completely separate mechanism to generate the code yourself--maybe something like t4 to generate from templates. You could base your templates on what codegen outputs as a starting point and then modify. This would be a fair amount of work, though.
3) You could consider creating a property on the partial class which exposes the EntityReference under a different name and not put Browseable(false) on it. Inconvenient because it has a different name, but probably the easiest thing to do.
You understand of course that none of these alternatives are very elegant, but I guess I'm gonna have to go with one of them. Most probably the first one.