GenDotNet Code Generation Tools

New Post: Why the move away from Xslt?

chriseyre2000 — Mon, 04 Aug 2008 16:58:47 GMT

Is there a compelling reason why the xslt approach will not work?
This seems to be a Code Smith / ASP style of generation.

Source code checked in

KathleenDollard — Sat, 29 Mar 2008 22:57:40 GMT

First public CTP - Nothing before this is usable, but CodePlex doesn't allow deleting changsets

UPDATED WIKI: Directions

KathleenDollard — Sat, 29 Mar 2008 22:35:25 GMT

Directions

We don’t yet support SQL Server Express. We’ve tested only with SQL Server 2005, but anticipate SQL Server 2000 and 2008 would also work

_If you haven’t built using the Build Notes – do that before continuing. _

Setting Up the Database

You need a database available that has single column primary keys on all tables. Neither Northwind nor AdventureWorksLT, nor NorthwindEF fill this requirement, so we’ve created a sample database for contacts. We anticipate upgrading this database periodically, so don’t include data, or plan to version your data. The only reason you’d want data in this database is for testing.

Assuming you plan to use GenDotNetSample

Create a database with some name on your server, preferably GenDotNetSample
Open your favorite query tool (like Microsoft Sql Server Management Studio) and change the name in the USE statement (first line) if you named it something other than GenDotNetSample
Run the scripts in the Database directory
Check that this database exists and contains four tables and no stored procedures

Create the ORM File

The ORM file must be present for the database to be managed correctly. While the morphing process supports an extremely rich mapping, it’s incredibly complex and we plan to abandon it in favor of a better process in April. Thus, we are not documenting the potential of this file in detail, just explaining that it must be there. The contents for GenDotNetSample are:

// multi-line
<orm:MappingRoot xmlns:orm="http://kadgen.com/KADORM.xsd"
xmlns:kd="http://kadgen.com/Special.xsd"
MapDataStructure="GenDotNetSample"
TransactionType="ADONET"
Namespace="GenDotNet.Samples"
TransactionForRetrieve="false"
RetrievePattern="Select_Object"
RetrieveChildrenPattern="SelectChildrenFKeyObject"
RetrieveAlternatePattern="ByCriteria"
SetSelectPattern="SelectAll_Object"
CreatePattern="Insert_Object"
UpdatePattern="Update_Object"
DeletePattern="Delete_Object"
Generate="CRUDS"
CollectionType="Plural">

<orm:SQLFunctionReplacement>
<orm:SQLFunction Name="getdate" ReplaceWith="System.DateTime.Today" NETType="System.DateTime"/>
</orm:SQLFunctionReplacement>



<orm:Mapping Name="GenDotNet.Samples">
</orm:Mapping>

</orm:MappingRoot>

// single line
If you named your database something other than GenDotNetSample, you must change the name in the MapDataStructure attribute in the MappingRoot element.

Run the Project

Run the project either in debug mode or via the executable. You’ll see a temporary (and very ugly) user interface.

Select your server if needed
Select the GenDotNetSample database or other database
Press the button “Make Sp Metadata”
Press the button "Generate Select"

Make Sp Metadata accomplishes two things. It extracts metadata from the database and it morphs it based on the ORMFile. You can run these steps separately via these buttons.

Generate Select creates a script in the SQL Output directory and loads this script into your database. Feel free to delete your stored procedures and rerun the tool to recreate them.

UPDATED WIKI: Directions

KathleenDollard — Sat, 29 Mar 2008 22:34:55 GMT

Directions

Setting Up the Database

Create a database with some name on your server, preferably GenDotNetSample
Open your favorite query tool (like Microsoft Sql Server Management Studio) and change the name in the USE statement (first line) if you named it something other than GenDotNetSample
Run the scripts in the Database directory
Check that this database exists and contains four tables and no stored procedures

Create the ORM File

The ORM file must be present for the database to be managed correctly. While the morphing process supports an extremely rich mapping, it’s incredibly complex and we plan to abandon it in favor of a better process in April. Thus, we are not documenting the potential of this file in detail, just explaining that it must be there. The contents for GenDotNetSample are:

// multi-line
<orm:MappingRoot xmlns:orm="http://kadgen.com/KADORM.xsd"
xmlns:kd="http://kadgen.com/Special.xsd"
MapDataStructure="GenDotNetSample"
TransactionType="ADONET"
Namespace="GenDotNet.Samples"
TransactionForRetrieve="false"
RetrievePattern="Select_Object"
RetrieveChildrenPattern="SelectChildrenFKeyObject"
RetrieveAlternatePattern="ByCriteria"
SetSelectPattern="SelectAll_Object"
CreatePattern="Insert_Object"
UpdatePattern="Update_Object"
DeletePattern="Delete_Object"
Generate="CRUDS"
CollectionType="Plural">

<orm:SQLFunctionReplacement>
<orm:SQLFunction Name="getdate" ReplaceWith="System.DateTime.Today" NETType="System.DateTime"/>
</orm:SQLFunctionReplacement>



<orm:Mapping Name="GenDotNet.Samples">
</orm:Mapping>

</orm:MappingRoot>

// single line
If you named your database something other than GenDotNetSample, you must change the name in the MapDataStructure attribute in the MappingRoot element.

Run the Project

Run the project either in debug mode or via the executable. You’ll see a temporary (and very ugly) user interface.

Select your server if needed
Select the GenDotNetSample database or other database
Press the button “Make Sp Metadata”
Press the button "Generate Select"

UPDATED WIKI: Directions

KathleenDollard — Sat, 29 Mar 2008 22:34:19 GMT

Directions

Setting Up the Database

Create a database with some name on your server, preferably GenDotNetSample
Open your favorite query tool (like Microsoft Sql Server Management Studio) and change the name in the USE statement (first line) if you named it something other than GenDotNetSample
Run the scripts in the Database directory
Check that this database exists and contains four tables and no stored procedures

Create the ORM File

The ORM file must be present for the database to be managed correctly. While the morphing process supports an extremely rich mapping, it’s incredibly complex and we plan to abandon it in favor of a better process in April. Thus, we are not documenting the potential of this file in detail, just explaining that it must be there. The contents for GenDotNetSample are:

// multi-line
<orm:MappingRoot xmlns:orm="http://kadgen.com/KADORM.xsd"
xmlns:kd="http://kadgen.com/Special.xsd"
MapDataStructure="GenDotNetSample"
TransactionType="ADONET"
Namespace="GenDotNet.Samples"
TransactionForRetrieve="false"
RetrievePattern="Select_Object"
RetrieveChildrenPattern="SelectChildrenFKeyObject"
RetrieveAlternatePattern="ByCriteria"
SetSelectPattern="SelectAll_Object"
CreatePattern="Insert_Object"
UpdatePattern="Update_Object"
DeletePattern="Delete_Object"
Generate="CRUDS"
CollectionType="Plural">

<orm:SQLFunctionReplacement>
<orm:SQLFunction Name="getdate" ReplaceWith="System.DateTime.Today" NETType="System.DateTime"/>
</orm:SQLFunctionReplacement>



<orm:Mapping Name="GenDotNet.Samples">
</orm:Mapping>

</orm:MappingRoot>

// single line
If you named your database something other than GenDotNetSample, you must change the name in the MapDataStructure attribute in the MappingRoot element.

Run the Project

Run the project either in debug mode or via the executable. You’ll see a temporary (and very ugly) user interface.

Select your server if needed
Select the GenDotNetSample database or other database
Press the button “Make Sp Metadata”
Press the button "Generate Select"

UPDATED WIKI: Home

KathleenDollard — Sat, 29 Mar 2008 22:27:35 GMT

Project Description
A code generation tool with a granular approach encouraging evolution in individual components. The generation engine and templates are based on VB9.0 XML literals which gives the most robust and powerful generation engine to date. Templates are created against isolated metadata models allowing a plug and play approach to metadata sources.

Be sure to read the Build Notes before attempting to build the project - or you will almost certainly fail!

Note from Kathleen:

_One of the rules of CodePlex is that you have to post your project within 30 days of opening it. This is probably a very good rule, however it has been very painful for us. I had prototyped the things in this project in samples for my blog and felt very optimistic. However, immediately after posting to the private group, I realized based on their feedback that the project needed restructuring. Between this and getting the infrastructure back working on the projects I’m using as test beds, it’s been a tough thirty days and the rest of the group has not had a stable build long enough to contribute. Thus I take complete responsibility for the weakness of this CTP.
I’ve elected to release only source code at this time. This is because if you want an automatic solution that works with your projects you should wait for the next CTP.
On the other hand, there is stuff in this build worth releasing as long as you recognize it as an early CTP._

Kathleen

This March CTP focuses on two core features:

- Isolated metadata model
- Template infrastructure

These are the two aspects of the system that most affect templates.

The remaining portions of the CTP exist only to allow creation and running of templates.

- User interface – OK, we know it’s hopeless. Look for a new version in April or May
- Generation engine – it doesn’t include System.Addin so your assemblies aren’t unloaded.
- Metadata – only my historic metadata is currently supported. We anticipate EDMX and perhaps other support in April (See Legacy Tools)
- Language neutral, C#/VB templates – not active in this CTP.
- Samples – only one lonely sample right now

We’ve got a ways to go with this; the important thing in this CTP is having a stable core of metadata/infrastructure to build templates on. That’s the first step. Many steps remain.

If you're dying to get started - download the source, follow the Build Notes, check out the Directions and see a discussion of the Sample Select Stored Procedure Template.

UPDATED WIKI: Sample Select Stored Procedure Template

KathleenDollard — Sat, 29 Mar 2008 22:26:05 GMT

SelectSpTemplate

I haven’t got the hang of getting code into wiki, so please open up the code and follow along. It’s one of the reasons we’re temporarily making you download the source.

Yes, it’s VB. This approach relies on the text processing features of VB 9.0 XML literals.

Imports

There are a number of imports you can explore to find out more about the overall architecture if you are impatient without documentation. The most important thing to note is that there is zero dependence on the specific wrapper. You are running against the SpInputMetadata wrapper, but the template does not know this – it only knows you’re using the stored procedure model.

SqlServerBase

Inheriting from SqlServerBase provides for reuse of some key code segments. This is not required, but is convenient.

Id

This is a Guid ID specific to this template. It allows better error management, although that’s not used in this example.

StoredProcedureName

The template is responsible for establishing the name of each file it produces. This flows down as the StoredProcedureName property which can be any naming you like. The NamingFactory will later provide support for flexible name templating separate from the template.

GenerateContents

This is where you’re template code goes. The infrastructure already created the framework, so all you need is the actual code you want output – deleting the previous stored proc and creating the new one has already been done.
In this case, there’s two calls into the SqlServerBase’s OutputRetrieve method. Once is for the main recordset, and the other occurs for each child. Thus the stored procedure returns the parent entity and each child entity.
You’ll notice a few odd looking things about this template. The <code> element indicates to VB that it’s entering an XML literal. Within the literal <%= separators offset code. The embedded expression can be a function call or a LINQ expression.

“But wait! This is XML we’re creating” I can hear you say. Here’s the beauty of XML literals that makes them a true text processing engine. The .Value method concatenates the contents of all the XML elements in depth first order. If you look at the OutputRetrieve function you’ll see it and it’s nested functions create additional XML nodes. But when the .Value executes these are concatenated into a single string, exactly the code for the stored procedure.

In this case, the output is identical to manually concatenating all the results. I believe it is essential to readability to offset the code you’re outputting from the code running the template. Thus, all the output is in code blocks.

If you’re used to CodeSmith, there’s a probably initial freak-out factor. You are not looking at the structure of your output with a few embedded things in it. You’re looking at code. But you can trace down easily to precisely the point of any problem, and have better code support to fix it. There’s also a tight set of recommended naming that’s really essential to managing the very large templates you’ll create in .NET code.

UPDATED WIKI: Sample Select Stored Procedure Template

KathleenDollard — Sat, 29 Mar 2008 22:25:19 GMT

SelectSpTemplate

I haven’t got the hang of getting code into wiki, so please open up the code and follow along. It’s one of the reasons we’re temporarily making you download the source.
Yes, it’s VB. This approach relies on the text processing features of VB 9.0 XML literals.

Imports

SqlServerBase

Inheriting from SqlServerBase provides for reuse of some key code segments. This is not required, but is convenient.

Id

This is a Guid ID specific to this template. It allows better error management, although that’s not used in this example.

StoredProcedureName

GenerateContents

UPDATED WIKI: Template infrastructure

KathleenDollard — Sat, 29 Mar 2008 22:24:34 GMT

Template Infrastructure

The template infrastructure is in the TemplateSupport project of the FullProject solution (or in TemplateSupport/TemplateSupport under the trunk).

Names in the infrastructure end with the suffix "Info." This distinguishes them from the metadata information which is suffixed with the word "Data." This is important because there are often identically named concepts that appear in two very different forms. For example: ObjectData represents data about the entity level for creating .NET code. What object are you creating code for and its metadata? The Template infrastructure has the quite distinct concept of ObjectInfo which contains data about the actual source code you're currently creating. The same ObjectData is likely to create several ObjectInfo’s, generally during the running of different templates.

TemplateInfrastructure supports both SqlServer and .NET templates. This includes the template interface and template base classes. The interface is used against the engine to allow you to entirely replace the TemplateBase. The TemplateBase is for your convenience.

Currently TemplateInfrastructure is documented through the discussion of the Sample Select Stored Procedure Template

UPDATED WIKI: Template infrastructure

KathleenDollard — Sat, 29 Mar 2008 22:06:10 GMT

Template Infrastructure

UPDATED WIKI: Directions

KathleenDollard — Sat, 29 Mar 2008 22:05:14 GMT

Directions

Setting Up the Database

Create the ORM File

The ORM file must be present for the database to be managed correctly. While the morphing process supports an extremely rich mapping, it’s incredibly complex and we plan to abandon it in favor of a better process in April. Thus, we are not documenting the potential of this file in detail, just explaining that it must be there. The contents for GenDotNetSample are:

// multi-line
<orm:MappingRoot xmlns:orm="http://kadgen.com/KADORM.xsd"
xmlns:kd="http://kadgen.com/Special.xsd"
MapDataStructure="GenDotNetSample"
TransactionType="ADONET"
Namespace="GenDotNet.Samples"
TransactionForRetrieve="false"
RetrievePattern="Select_Object"
RetrieveChildrenPattern="SelectChildrenFKeyObject"
RetrieveAlternatePattern="ByCriteria"
SetSelectPattern="SelectAll_Object"
CreatePattern="Insert_Object"
UpdatePattern="Update_Object"
DeletePattern="Delete_Object"
Generate="CRUDS"
CollectionType="Plural">

<orm:SQLFunctionReplacement>
<orm:SQLFunction Name="getdate" ReplaceWith="System.DateTime.Today" NETType="System.DateTime"/>
</orm:SQLFunctionReplacement>



<orm:Mapping Name="GenDotNet.Samples">
</orm:Mapping>

</orm:MappingRoot>

// single line
If you named your database something other than GenDotNetSample, you must change the name in the MapDataStructure attribute in the MappingRoot element.

Run the Project

Run the project either in debug mode or via the executable. You’ll see a temporary (and very ugly) user interface.

Select your server if needed
Select the GenDotNetSample database or other database
Press the button “Make Sp Metadata”
Press the button "Generate Select"

UPDATED WIKI: Directions

KathleenDollard — Sat, 29 Mar 2008 22:04:58 GMT

Directions

Setting Up the Database

Create the ORM File

The ORM file must be present for the database to be managed correctly. While the morphing process supports an extremely rich mapping, it’s incredibly complex and we plan to abandon it in favor of a better process in April. Thus, we are not documenting the potential of this file in detail, just explaining that it must be there. The contents for GenDotNetSample are:

// multi-line
<orm:MappingRoot xmlns:orm="http://kadgen.com/KADORM.xsd"
xmlns:kd="http://kadgen.com/Special.xsd"
MapDataStructure="GenDotNetSample"
TransactionType="ADONET"
Namespace="GenDotNet.Samples"
TransactionForRetrieve="false"
RetrievePattern="Select_Object"
RetrieveChildrenPattern="SelectChildrenFKeyObject"
RetrieveAlternatePattern="ByCriteria"
SetSelectPattern="SelectAll_Object"
CreatePattern="Insert_Object"
UpdatePattern="Update_Object"
DeletePattern="Delete_Object"
Generate="CRUDS"
CollectionType="Plural">

<orm:SQLFunctionReplacement>
<orm:SQLFunction Name="getdate" ReplaceWith="System.DateTime.Today" NETType="System.DateTime"/>
</orm:SQLFunctionReplacement>



<orm:Mapping Name="GenDotNet.Samples">
</orm:Mapping>

</orm:MappingRoot>

// single line
If you named your database something other than GenDotNetSample, you must change the name in the MapDataStructure attribute in the MappingRoot element.

Run the Project

Run the project either in debug mode or via the executable. You’ll see a temporary (and very ugly) user interface.

Select your server if needed
Select the GenDotNetSample database or other database
Press the button “Make Sp Metadata”
Press the button "Generate Select"

UPDATED WIKI: Directions

KathleenDollard — Sat, 29 Mar 2008 22:04:11 GMT

Directions

Setting Up the Database

Create the ORM File

The ORM file must be present for the database to be managed correctly. While the morphing process supports an extremely rich mapping, it’s incredibly complex and we plan to abandon it in favor of a better process in April. Thus, we are not documenting the potential of this file in detail, just explaining that it must be there. The contents for GenDotNetSample are:

// multi-line
<orm:MappingRoot xmlns:orm="http://kadgen.com/KADORM.xsd"
xmlns:kd="http://kadgen.com/Special.xsd"
MapDataStructure="GenDotNetSample"
TransactionType="ADONET"
Namespace="GenDotNet.Samples"
TransactionForRetrieve="false"
RetrievePattern="Select_Object"
RetrieveChildrenPattern="SelectChildrenFKeyObject"
RetrieveAlternatePattern="ByCriteria"
SetSelectPattern="SelectAll_Object"
CreatePattern="Insert_Object"
UpdatePattern="Update_Object"
DeletePattern="Delete_Object"
Generate="CRUDS"
CollectionType="Plural">

<orm:SQLFunctionReplacement>
<orm:SQLFunction Name="getdate" ReplaceWith="System.DateTime.Today" NETType="System.DateTime"/>
</orm:SQLFunctionReplacement>



<orm:Mapping Name="GenDotNet.Samples">
</orm:Mapping>

</orm:MappingRoot>

// single line
If you named your database something other than GenDotNetSample, you must change the name in the MapDataStructure attribute in the MappingRoot element.

Run the Project

Run the project either in debug mode or via the executable. You’ll see a temporary (and very ugly) user interface.

Select your server if needed
Select the GenDotNetSample database or other database
Press the button “Make Sp Metadata”

This accomplishes two things. It extracts metadata from the database and it morphs it based on the ORMFile. You can run these steps separately via these buttons.

Press the button Generate Select

This creates a script in the SQL Output directory and loads this script into your database. Feel free to delete your stored procedures and rerun the tool to recreate them.

UPDATED WIKI: Directions

KathleenDollard — Sat, 29 Mar 2008 22:03:38 GMT

Directions

Setting Up the Database

Create the ORM File

The ORM file must be present for the database to be managed correctly. While the morphing process supports an extremely rich mapping, it’s incredibly complex and we plan to abandon it in favor of a better process in April. Thus, we are not documenting the potential of this file in detail, just explaining that it must be there. The contents for GenDotNetSample are:

// multi-line
<orm:MappingRoot xmlns:orm="http://kadgen.com/KADORM.xsd"
xmlns:kd="http://kadgen.com/Special.xsd"
MapDataStructure="GenDotNetSample"
TransactionType="ADONET"
Namespace="GenDotNet.Samples"
TransactionForRetrieve="false"
RetrievePattern="Select_Object"
RetrieveChildrenPattern="SelectChildrenFKeyObject"
RetrieveAlternatePattern="ByCriteria"
SetSelectPattern="SelectAll_Object"
CreatePattern="Insert_Object"
UpdatePattern="Update_Object"
DeletePattern="Delete_Object"
Generate="CRUDS"
CollectionType="Plural">

<orm:SQLFunctionReplacement>
<orm:SQLFunction Name="getdate" ReplaceWith="System.DateTime.Today" NETType="System.DateTime"/>
</orm:SQLFunctionReplacement>



<orm:Mapping Name="GenDotNet.Samples">
</orm:Mapping>

</orm:MappingRoot>

// single line
If you named your database something other than GenDotNetSample, you must change the name in the MapDataStructure attribute in the MappingRoot element.

Run the Project

Run the project either in debug mode or via the executable. You’ll see a temporary (and very ugly) user interface.

Select your server if needed

Select the GenDotNetSample database or other database

Press the button “Make Sp Metadata”

This accomplishes two things. It extracts metadata from the database and it morphs it based on the ORMFile. You can run these steps separately via these buttons.

#Press the button Generate Select
This creates a script in the SQL Output directory and loads this script into your database. Feel free to delete your stored procedures and rerun the tool to recreate them.

UPDATED WIKI: Build Notes

KathleenDollard — Sat, 29 Mar 2008 21:51:19 GMT

Build Notes

The code exists in two projects: FullProject under the Trunk and LegacyTools under LegacyTools. These are separate because this CTP is built on my past code gen tool. The old stuff is being replaced as part of the conversion, but of course this takes time. This CTP focuses on the core isolated metadata, template support infrastructure, and engine structure. The old metadata extraction tools are still used. These are caught in a web of dependencies in the old project. To give an idea of scope, there are 1000 files in the legacy stuff and 500 in the new, so there is a ton of crap we’re getting rid of. We don't want to contaminate the new project with this old crap, which results in the two projects which complicates the build.

To build, follow these instructions:

Open Visual Studio 2008 with the Trunk/FullProject.sln
Open a second instance of Visual Studio 2008 with Trunk/LegacyMetadataTools/LegacyTools.sln
Rebuild solution the LegacyTools solution. If it doesn’t build, report the problems
In the FullProject solution, in the SimpleUI project, set a reference

Right click, and Add a reference
Go to the Browse tab
Go up to the trunk and down to reference to Trunk/LegacyMetadataTools/LogicWrappers2008/bin/debug
Set a reference to LogicWrappers2008.dll

Set SimpleUI as the startup project
Rebuild Solution on FullProject

Go next to Directions to get started.

I look forward to any comments you may have. Please keep expectations reasonable. We’ve concentrated on a solid metadata and template infrastructure framework as well as a lot of work (some of which is not yet released around System.AddIn usage) on how the engine will work.

UPDATED WIKI: Build Notes

KathleenDollard — Sat, 29 Mar 2008 21:49:10 GMT

Build Notes

Open Visual Studio 2008 with the Trunk/FullProject.sln
Open a second instance of Visual Studio 2008 with Trunk/LegacyMetadataTools/LegacyTools.sln
Rebuild solution the LegacyTools solution. If it doesn’t build, report the problems
In the FullProject solution, in the SimpleUI project, set a reference

Right click, and Add a reference
Go to the Browse tab
Go up to the trunk and down to reference to Trunk/LegacyMetadataTools/LogicWrappers2008/bin/debug
Set a reference to LogicWrappers2008.dll

Rebuild Solution on FullProject

UPDATED WIKI: Build Notes

KathleenDollard — Sat, 29 Mar 2008 21:48:51 GMT

Build Notes

Open Visual Studio 2008 with the Trunk/FullProject.sln
Open a second instance of Visual Studio 2008 with Trunk/LegacyMetadataTools/LegacyTools.sln
Rebuild solution the LegacyTools solution. If it doesn’t build, report the problems
In the FullProject solution, in the SimpleUI project, set a reference

Right click, and Add a reference
Go to the Browse tab
Go up to the trunk and down to reference to Trunk/LegacyMetadataTools/LogicWrappers2008/bin/debug
Set a reference to LogicWrappers2008.dll

Rebuild Solution on FullProject

Go next to [Directions} to get started.

I look forward to any comments you may have. Please keep expectations reasonable. We’ve concentrated on a solid metadata and template infrastructure framework as well as a lot of work (some of which is not yet released around System.AddIn usage) on how the engine will work.

UPDATED WIKI: Home

KathleenDollard — Sat, 29 Mar 2008 21:47:36 GMT

UPDATED WIKI: Home

KathleenDollard — Sat, 29 Mar 2008 21:46:24 GMT

Project Description
A code generation tool with a granular approach encouraging evolution in individual components. The generation engine and templates are based on VB9.0 XML literals which gives the most robust and powerful generation engine to date. Templates are created against isolated metadata models allowing a plug and play approach to metadata sources.

**Delete the following note before publishing **

This project is currently in setup mode and only available to project coordinators and developers. Once you have finished setting up your project you can publish it to make it available to all CodePlex visitors.

There are three requirements before you publish:

- Edit this page to provide information about your project
- Upload the initial source code for your project
- Add your project license

Additional information on starting a new project is available here: Project Startup Guide.
Be sure to read the Build Notes before attempting to build the project - or you will almost certainly fail!

Note from Kathleen:

_One of the rules of CodePlex is that you have to post your project within 30 days of opening it. This is probably a very good rule, however it has been very painful for us. I had prototyped the things in this project in samples for my blog and felt very optimistic. However, immediately after posting to the private group, I realized based on their feedback that the project needed restructuring. Between this and getting the infrastructure back working on the projects I’m using as test beds, it’s been a tough thirty days and the rest of the group has not had a stable build long enough to contribute. Thus I take complete responsibility for the weakness of this CTP.
I’ve elected to release only source code at this time. This is because if you want an automatic solution that works with your projects you should wait for the next CTP.
On the other hand, there is stuff in this build worth releasing as long as you recognize it as an early CTP._

Kathleen

This March CTP focuses on two core features:

- Isolated metadata model
- Template infrastructure

These are the two aspects of the system that most affect templates.

The remaining portions of the CTP exist only to allow creation and running of templates.

- User interface – OK, we know it’s hopeless. Look for a new version in April or May
- Generation engine – it doesn’t include System.Addin so your assemblies aren’t unloaded.
- Metadata – only my historic metadata is currently supported. We anticipate EDMX and perhaps other support in April (See Legacy Tools)
- Language neutral, C#/VB templates – not active in this CTP.
- Samples – only one lonely sample right now

We’ve got a ways to go with this; the important thing in this CTP is having a stable core of metadata/infrastructure to build templates on. That’s the first step. Many steps remain.

UPDATED WIKI: Legacy Tools

KathleenDollard — Sat, 29 Mar 2008 21:41:43 GMT

Legacy Stuff

From a practical perspective, you can ignore the thousand or so files in trunk/LegacyMetadataTools

There’s a pile of legacy stuff that’s in the project right now because we need to do some sort of metadata extraction and morphing. Reusing this old code allowed us to focus on the critical areas of metadata models, template infrastructure, and laying the groundwork for a robust engine. The legacy mapping depends on an ORM file which must be present (see directions). The ORMFile is a pain to use. In April this will either be replaced or documented to allow mapping.

The legacy stuff is in a separate solution. Please see the Build Notes to see how to manage this separate solution during the build. The LogicWrapper2008 project provides a temporary bridge to the legacy stuff. This limits the dependencies between these two sections. It also hides the complexity of the legacy interfaces. The dozens of switches and dials which made up this very confusing interface are being reconsidered based on new ideas of decision responsibility. Look for more later. In the short term, I’ve hardcoded the most likely values into the LogicWrapper.

Because this is in a separate solution, the reference will easily become broken (let me know if you solve this) and debugging will be a pain. However, this is preferable to contaminating the new project with the old crap, all of this is slated for rewrite, hopefully with the EF modelers.

The legacy stuff exists in the LegacyMetadataTools directory.