Frans Bouma's blog - All Comments

re: Dynamic Data and 3rd party o/r mappers is a fact

FransBouma — Sun, 18 May 2008 09:46:40 GMT

@andyb

Yes we're looking at implementing IUpdatable for LLBLGen Pro sometime soon, so Astoria support is also covered :)

re: Dynamic Data and 3rd party o/r mappers is a fact

andyb.uk — Fri, 16 May 2008 19:00:11 GMT

I'd be interested to hear if LLBLGen will support IUpdateable in its generation of code. That would help it support the clean sweep of new Data Services technologies from Microsoft, alongside LINQ and this Dynamic Data work. Exciting data times!

re: Linq to Sql support added to LLBLGen Pro

Dennis van der Stelt — Mon, 05 May 2008 12:43:46 GMT

Great story Frans, got everyone to look at me when I was ROFL-ing ;)

re: Linq to Sql support added to LLBLGen Pro

FransBouma — Sat, 03 May 2008 11:26:26 GMT

Kevin: they're on their way. If you don't receive them, they're probably caught by hotmail's spamfilter which blocks zip files. :)

re: Linq to Sql support added to LLBLGen Pro

Kevin Dan — Sat, 03 May 2008 06:54:14 GMT

Hi Frans,

I am not LLBLGen Pro customer, but I would like to check out LLBLGen Pro 2.6 Beta, along with LINQ to SQL support and Dynamic Data support.

Can you please drop LLBLGen Pro 2.6 Beta, classes (Dyanmic Data), and templates (LINQ2SQL) here: kevindan2000#hotmail.com.

Thanks, Kevin

re: Linq to Sql support added to LLBLGen Pro

FransBouma — Fri, 02 May 2008 06:41:14 GMT

pbz: it doesn't use the linq to sql designer, as it uses the llblgen pro designer :) The downside comes from the fact that the llblgen pro designer uses its own project file, so if you update the dbml file in vs.net 2008, these changes aren't reflected in the llblgen pro project.

re: Linq to Sql support added to LLBLGen Pro

pbz — Fri, 02 May 2008 03:18:49 GMT

OK, I'm confused :-) Does it use the LINQ to SQL designer, or does it have it's own? And if it has its own then why do you say "The only downside is that you can't update your model in the Linq to Sql designer anymore."

BTW: Great idea with having a file per entity. Can I specify what folders those files should go to?

re: Linq to Sql support added to LLBLGen Pro

Timothy Lee Russell — Thu, 01 May 2008 20:50:51 GMT

Scott and Guy:

I'm just a biased customer but one thing to consider is how much time this tool can save you -- in my case, LLBLGen Pro paid for itself in the first 3.82 hours.

Timothy

re: Linq to Sql support added to LLBLGen Pro

FransBouma — Thu, 01 May 2008 18:24:08 GMT

Neil: I messed with that abstract stuff a while, as it gave me a bit of a problem in inheritance hierarchies: the abstract class can't have a discriminator value, but it has to as it has to have a discriminator value. :) So you're in a catch 22. At least, I couldn't solve it without dropping the 'abstract'.

We don't support sealed indeed, as we find 'sealed' a keyword which shouldn't be used that much.

Thanks for the kind words! :)

For vs.net extension: we're looking at that for v3.

re: Linq to Sql support added to LLBLGen Pro

Neil McGuire — Thu, 01 May 2008 18:16:20 GMT

Just realized that the abstract base could come out as an "internal abstract partial class" if you change the Access Modifier. Sorry if anyone got confused.