Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...To LINQ or not to LINQ, that is the questionTo LINQ or not to LINQ, that is the question
Previous
 
Next
New Post
5/20/2008 5:32 PM
 

I'm a little wary jumping into the unknown waters of LINQ and ASP.NET 3.5. Is it really "ready for primetime" and stable with respect to DNN 4.8? I would hate to develop new modules using LINQ and ASP.NET 3.5 only to find that older modules misbehave in this environment.

Is the productivity with LINQ is that much better that it is worth the learning curve "pain"?

I would love to hear folks thoughts on this - especially if you have deployed modules with LINQ and ASP.NET 3.5 on a live business site with other third-party modules.

 
New Post
5/21/2008 1:54 AM
 

3.5 is the way of the future - however - be aware that your millage may vary with some modules that do not seem to run well under 3.5.

As for LINQ on the other hand - really its just another database abstration tool.

Once you get the hang of it though - creating generic forms and grids is very easy - and much faster than
hand hacking data classes - sure codesmith can be handy in some areas - but you still run into
round trip issues whenever you change a tables schema.

As for stable etc - yep - its very solid - the 3.5 sp1 beta is not as stable - but hey its a beta so whatever,

Westa

 
New Post
5/21/2008 8:25 AM
 

I have to agree with Wes, but I have not had any problems with older modules running on asp.net 3.5 (yet).

The learning curve is definitely worth it. I've been using it for 4 months now and not only does it allow me to make a module wit a 50%-75% time and code savings, Linq is actually "fun" to use because of the intellisense help when writig a query.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
5/21/2008 10:47 AM
 

So here I am looking at LINQ too. I have created my LINQ surface, pulled in my tables, and got everything working in a sandbox (NOT DNN). I have had my curiosities  satisfied and started recreating everything in a DNN environment and hit my first snag. Why can't my LINQ datasource find my DataContext class? I checked the namespace and everything is kosher... Any idea's?


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
New Post
5/21/2008 11:52 AM
 

Never Mind. I got it.


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...To LINQ or not to LINQ, that is the questionTo LINQ or not to LINQ, that is the question


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out