A couple of important changes have been made in the presets for Entity framework v1 and v4 in the upcoming build.

It was discovered that when using multiple groups and the grouping mechanism is set to AsSeparateProjects, the vs.net project name generated wasn't reflecting the group, but always had the 'projectname' as its name. This has the disadvantage that when you add all vs.net projects to 1 solution, you get conflicts and it doesn't work.

We've changed this to be the group name in this case, or more importantly, we changed the [projectName] directive in the presets to [containerName] as it should have been.

This also has effect on people with the default grouping mechanism where everything is 1 project: the project name is now made pascal cased, as well as the context name.

Also, we made the change that we now generate per database type a persistence project or in the case of v1 style, a complete set of classes + edmx/context file. Before, we generated all meta-data and mappings in a single edmx file but this was not usable at runtime as the EF doesn't offer a switching mechanism between the different database types in the edmx file.

This has the effect that if you use multiple database types (e.g. SQL server and firebird) with EF, for every database a folder is created now with the persistence project.

The changes will be in the v3 build of July 28th or later.

In the next build, August 5th, we'll rollback this change:

We've changed this to be the group name in this case, or more importantly, we changed the [projectName] directive in the presets to [containerName] as it should have been.

as it was 1) unnecessary and 2) causes problems with vs.net filename creation: the rootnamespace active at that point was the project name, whic already contained the groupname, and the change we made would create project names with just the group name.

Our apologies for any inconvenience this might have caused. To workaround this today, change [containedName] in the vs.net project tasks to [projectName]