On Thu, Jul 15, 2010 at 3:04 PM, DotNet Dude wrote:
> Would LLBLGen still be your choice when only custom stored
> procedures are used?
Depends how "only" only is.
It's hard for me to answer this unbiasedly. I would say "yes" still,
but that's because I know I wouldn't be using "only" custom sto
Would LLBLGen still be your choice when only custom stored procedures are used?
On Thu, Jul 15, 2010 at 12:00 PM, silky wrote:
>> This question seemed to diverge off into the Linq direction, but I didn't
>> see anyone confirm or deny if nHibernate is the way to go or not.
>>
>> Some time ago I wr
>> I'll be needing to decide what to invest my time into. latest EF?
nHibernate? llbgen? Any further comments on what to use? I know (and
love) Linq.
>> I'm not an expert but with LinqPad and Resharper I get by. Linq is
amazing.
Mentioned in a previous post that I was using EntitySpaces 2010 w
I'm using NHibernate with ASP.NET MVC and with WCF REST services and I'm
very happy with it.
There is lots more info available these days on the net about setting up and
running NH, but the learning curve is definitely there.
There are also some extra add ons available (Fluent NHibernate, NH
Vali
This question seemed to diverge off into the Linq direction, but I didn't
see anyone confirm or deny if nHibernate is the way to go or not.
Some time ago I wrote an app and used Linq to SQL and was really happy with
how simple it made things. Then there was the on again off again future of
Linq to
Hello Les,
You must check out llblgen
The time savings are amazing.
It is worth every cent. It is a mature, reliable product.
It is sooo much easier than nhibernate.
Linq is not a data layer - it is a very useful thing, well worth
knowing, but it does not address your needs.
Llblgen wor
Nic Roche wrote:
http://msdn.microsoft.com/en-us/vcsharp/bb688085.aspx
Nic
http://msdn.microsoft.com/en-us/vcsharp/bb688085.aspx ==
http://msdn.microsoft.com/en-us/vbasic/bb688085.aspx
I think the 'vcsharp' and 'vbasic' directories are just virtual dirs
meant for making more readable/sear
http://msdn.microsoft.com/en-us/vcsharp/bb688085.aspx
Nic
Subject: RE: Advice for Data Access - Hibernate/Linq/Fluent/etc
Date: Wed, 14 Jul 2010 10:47:56 +1000
From: ben.robb...@jlta.com.au
To: ozdotnet@ozdotnet.com
Great link Corneliu, do you know if there is an equivalent page for C
llblgen
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Michael Minutillo
Sent: Wednesday, 14 July 2010 12:52 PM
To: ozDotNet
Subject: Re: Advice for Data Access - Hibernate/Linq/Fluent/etc
+1 for LINQPad and LINQ.
If you do try LINQPad (which is
: 'ozDotNet'
Subject: RE: Advice for Data Access - Hibernate/Linq/Fluent/etc
I have never considered using LINQ to SQL because it was worthless in n-tier
scenarios where the classes could not be serialized away from the context.
(is this still the case?)
Greg
Currently using EntitySpaces 2010 for our data access layer
http://www.entityspaces.net/Portal/Default.aspx
Has support for LINQ.
Very happy with the product. Support is great.
Does cost, unlike nHibernate, but its not that expensive.
You could also check out lightspeed
(http://www.mindscape
Get a hold of LinqPAD (www.linqpad.net) and you won't look back.
Great for learning LINQ and for experimenting.
Having spent a lot of yesterday trying to get a .nettiers project compiling,
I'm so thankful for LINQ.
I have enjoyed the way the netTiers generated classes are binary
seriali
:
> +1 for LINQPad
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Dylan Tusler
> *Sent:* Wednesday, 14 July 2010 10:20
> *To:* 'ozDotNet'
>
> *Subject:* RE: Advice for Data Access - Hibernate/Linq/
+1 for LINQPad
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Dylan Tusler
Sent: Wednesday, 14 July 2010 10:20
To: 'ozDotNet'
Subject: RE: Advice for Data Access - Hibernate/Linq/Fluent/etc
Get a hold of LinqPAD (www.linqpad.net) and you
to:ozdotnet-boun...@ozdotnet.com] On
Behalf Of ben.robb...@jlta.com.au
Sent: Wednesday, 14 July 2010 10:48 AM
To: ozdotnet@ozdotnet.com
Subject: RE: Advice for Data Access - Hibernate/Linq/Fluent/etc
Great link Corneliu, do you know if there is an equivalent page for C#?
After a bit of Googling
-boun...@ozdotnet.com] On Behalf Of Corneliu I. Tusnea
Sent: Wednesday, 14 July 2010 7:14 AM
To: ozDotNet
Subject: Re: Advice for Data Access - Hibernate/Linq/Fluent/etc
I think the simplest/lightest/quickest way to craft an ORM over
a DB is LINQ to SQL
I think the simplest/lightest/quickest way to craft an ORM over a DB is LINQ
to SQL.
You can't make it any simpler that than. I don't understand why MS stopped
developing.
They try too hard to move in the "we love everyone and every db camp at the
expense of our own SQL".
Have this page open all
Hi Les
I my opinion LINQ is worth the learning curve because it allows fairly
rapid development of applications compared to an application with
dedicated business objects and associated stored procedures. We code
generate all of our data acces objects and stored procedures but when
there's a chang
18 matches
Mail list logo
