Best strategy for incorporating LINQ into a Windows Form Application: C#, LINQ, .NET Forms, VS 2008

Best strategy for incorporating LINQ into a Windows Form Application

I'm playing around with LINQ for a few future projects and was curious, design wise, what people feel is the best approach to handling LINQ in a windows form application regarding:

1) Determining if an object is new or just needs to be updated.
2) What needs to be declared as instance-level variables in the form class

For example, if I have a Data Context dc and a LINQ Object Person,

1) What is the best mechanism to determine if this object already exists in the dc or if it needs to be created.

2) Is there a way to update only the fields that changed? Know what changed?

3) Do I just hold onto the data-context or do I need more?

What approaches are others using?

Instant Access to this Solution

Plus...

30 Day FREE access, no risk, no obligation

Collaborate with the world's top tech experts

Unlimited access to our exclusive solution database

Never be left without tech help again

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

"The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.

"Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin

"Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

I also recommend linq it has made life much easier for me. I tend to take the same approach with linq be it a web application or windows form application. The first step that I take is that I always create a Repository class to handle most of my heavy lifting. Within the repository class, bare minimum I define the method that retorns all objects, the method to return one object, the method to create a new object, the method to delete an object and the method to save objects. I started doing this after reading Scott Guthrie's nerddinner snipper, an example is below.

using System;
 
public class RateCardAuditRepository : IRateCardAuditRepository
{
    private readonly PersonDataContext Db = new PersonDataContext();
 
    public IQueryable<Person> GetPersons()
    {
        return Db.Persons;
    }
 
    /// <summary>
    /// Returns a single person entity based off of it's primary key
    /// </summary>
    /// <param name="id"></param>
    /// <returns></returns>
    public Person GetPerson(string id)
    {
        return Db.Persons.SingleOrDefault(d => d.ID == id);
    }
 
    /// <summary>
    /// Adds a new item to the data base table
    /// </summary>
    /// <param name="Person"></param>
    public void AddNewItem(Person Person)
    {
        Db.Persons.InsertOnSubmit(Person);
    }
 
    /// <summary>
    /// Deletes an item from the data base table
    /// </summary>
    /// <param name="Person"></param>
    public void DeleteItem(Person person)
    {
        Db.Persons.DeleteOnSubmit(person);
    }
 
    /// <summary>
    /// Persists table changes to the data base.
    /// </summary>
    public void Save()
    {
        Db.SubmitChanges();
    }
}

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:

Select all Open in new window

Question

Best strategy for incorporating LINQ into a Windows Form Application

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

C#

LINQ

.NET Forms

VS 2008

Language Integrated Query - LINQ

C# Programming Language

Visual Studio

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Need individual assistance?

Our experts are ready to help.

Want to learn from the best?

Read articles from industry experts.

Working on a long term project?

Store your work and research.

What Makes Experts Exchange Unique?

Trusted by the world's most respected brands.

Faithfully serving IT professionals since 1996.

Related Solutions

Free Tech Articles

Cloud Class Webinars

Join the Community

Give a Little. Get a Lot.

Answers

3 Ways to Join

The Experts

The Experts

Testimonials

Testimonials

Testimonials

Business Clients

Business Clients

In the Press

In the Press

In the Press