LLBLGen.com Forums Announcements feed

Important: NHibernate changes coming up by Otis

Otis — Thu, 05 Aug 2010 10:30:37 GMT

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

Quote:

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]

Important: Entity Framework changes coming up by Otis

Otis — Thu, 05 Aug 2010 10:30:23 GMT

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

Quote:

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.

Important: NHibernate changes coming up by Otis

Otis — Wed, 28 Jul 2010 09:58:32 GMT

We discovered that multiple database types in a single nhibernate project didn't work in practice: the code of databases enumerated later on in the code generation process overwrote the already generated code. This was due to a problem in the presets: it should generate the code per database in a specific folder, if required. We have addressed this 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.

We added N:M support for NHibernate to the upcoming build as well.

Important: Entity Framework changes coming up by Otis

Otis — Wed, 28 Jul 2010 09:54:39 GMT

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.

Bitwise AND predicate uploaded by Otis

Otis — Fri, 09 Jul 2010 07:44:04 GMT

TomV wrote:

Hello Otis,

I'm also not able to find this link. Is it still available?
Or has llblgen in meantime already some support for bitwise fields?

Best regards,
TomV

In which database? We support them in oracle in v3.

Bitwise AND predicate uploaded by TomV

TomV — Fri, 09 Jul 2010 06:45:37 GMT

Hello Otis,

I'm also not able to find this link. Is it still available?
Or has llblgen in meantime already some support for bitwise fields?

Best regards,
TomV

Beta of ADO.NET dataservices templates posted! by WayneBrantley

WayneBrantley — Wed, 09 Jun 2010 17:59:50 GMT

AquaMan,
Look at the work in this thread:

http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=16377&HighLight=1

LLBLGen Pro v3.0 RTM has been released! by vikramka

vikramka — Tue, 01 Jun 2010 02:10:19 GMT

Congratulations. I just ordered an upgrade.

Can't wait to finally see what Entity Framework and nhibernate are all about.

LLBLGen Pro v3.0 RTM has been released! by Ian

Ian — Mon, 31 May 2010 04:17:24 GMT

Congratulations on the release. Loving the Element Grouping. Why isn't this in SQL Server Management Studio?!

LLBLGen Pro v3.0 RTM has been released! by Otis

Otis — Sun, 30 May 2010 18:59:17 GMT

Thanks Sven .