llblgen

 

From: [email protected] [mailto:[email protected]]
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 free) then I highly recommend purchasing the
$20 IntelliSense add-on. Especially if you are just getting starting in
LINQ.

 

In the interests of full-disclosure, Joe (the author of LINQPad) is a friend
but I use LINQPad as a general snippet compiler for a bunch of different
stuff (including keeping a TV schedule).

 

I have tried to get FluentNHibernate and LINQtoNHibernate working together
once before and it was a painful experience. Once I had it working though,
it was great.

On Wed, Jul 14, 2010 at 9:14 AM, James Chapman-Smith
<[email protected]> wrote:

+1 for LINQPad

 

From: [email protected] [mailto:[email protected]]
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 won't look back.

 

Having spent a lot of yesterday trying to get a .nettiers project compiling,
I'm so thankful for LINQ.

 

Dylan.

 

 

  _____  

From: [email protected] [mailto:[email protected]]
On Behalf Of [email protected]
Sent: Wednesday, 14 July 2010 10:48 AM
To: [email protected]
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 and browsing the closest I got was this:
http://msdn.microsoft.com/en-us/vcsharp/aa336746.aspx

 

Ben

 


  _____  


From: [email protected] [mailto:[email protected]]
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.

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 the time and you'll be flying with the LINQ syntax.

http://msdn.microsoft.com/en-us/vbasic/bb688085.aspx

 

Corneliu.

 

On Wed, Jul 14, 2010 at 9:05 AM, Peter Arvoll <[email protected]>
wrote:

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 change to the database schema it's much quicker to modify
the dbml file (or delete the changed entiries and drop them back on)
than to re generate the data access objects and modify stored procs. I
am talking LINQ to SQL here as it doesn't have the facility to update
the model from a database.

And LINQ can be used for more than just data access. It's a very neat
way to interaction with collections of objects where previously you
would have had to loop through the collections to do tasks linq had
the foreach syntax. And it's easy to create a subset of an object
collection too.

LINQ to XML is in my opionion a much easier way (and faster
development wise) to consume an XML file.

I have not had any commercial experience with NHibernate so I am not
able to compare there.

Thanks
Peter


On Wed, Jul 14, 2010 at 1:18 AM, Les Hughes <[email protected]> wrote:
>
> Hi All,
>
> I'm about to start working on a mid-sized data-centric app (accounting
area)
> which is mostly just lots of forms which display data, edit/write data,
and
> then spitting out some pretty reports, etc with the data sitting in SQL
> Server. (Think of old-school MSaccess  apps)
>
> Wanting to avoid as much SQL plumbing as I can, I'm looking to use
> nHibernate for a lot of the lifting, but haven't had a chance to look
around
> at perhaps some better packages/practices/etc which exist.
>
> At this stage I have spent near zero time with Linq, and have only heard
of
> a few other packages in passing (Fluent/Active Record/etc), and am
wondering
> what (if anything) I should spend some time looking in to.
>
> My query is:
>
> - Is nHibernate still the way to go? What do the rest of the .NETters use
> for their data access layers? And why? Is Linq worth the learning curve?
>
> Any feedback would be greatly appreciated.
>
> Thanks in advance,
> --
> Les Hughes
> [email protected]
>

 


This email is intended for the named recipient only.  The information it
contains may be confidential or commercially sensitive.  If you are not the
intended recipient you must not reproduce or distribute any part of this
email, disclose its contents to any other party, or take any action in
reliance on it.  If you have received this email in error, please contact
the sender immediately and delete the message from your computer.
  _____  


To find out more about the Sunshine Coast Regional Council, visit your local
office at Caloundra, Maroochydore, Nambour or Tewantin or visit us online at
<http://www.sunshinecoast.qld.gov.au/> www.sunshinecoast.qld.gov.au.  If
correspondence includes personal information, please refer to
<http://www.sunshinecoast.qld.gov.au/sitePage.cfm?code=disclaimer> Council's
Privacy Policy.

This email and any attachments are confidential and only for the use of the
addressee.  If you have received this email in error you are requested to
notify the sender by return email or contact council on 1300 00 7272 and are
prohibited from forwarding, printing, copying or using it in anyway, in
whole or part. Please note that some council staff utilise Blackberry
devices, which results in information being transmitted overseas prior to
delivery of any communication to the device. In sending an email to Council
you are agreeing that the content of your email may be transmitted overseas.
Any views expressed in this email are the author's, except where the email
makes it clear otherwise. The unauthorised publication of an email and any
attachments generated for the official functions of council is strictly
prohibited. Please note that council is subject to the Right to Information
Act 2009 (Qld) and Information Privacy Act 2009 (Qld).




-- 
Michael M. Minutillo
Indiscriminate Information Sponge
Blog: http://wolfbyte-net.blogspot.com

Reply via email to