Re: XAML and WPF -- SYSTEMIDOTNET

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: XAML and WPF
From: "ibm" <ibm@xxxxxxxxxx>
Date: Wed, 21 Oct 2009 14:52:54 -0500
List-archive: <http://archive.midrange.com/systemidotnet>
List-help: <mailto:systemidotnet-request@midrange.com?subject=help>
List-id: ".net use with the System i" <systemidotnet.midrange.com>
List-post: <mailto:systemidotnet@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/systemidotnet>, <mailto:systemidotnet-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/systemidotnet>, <mailto:systemidotnet-request@midrange.com?subject=unsubscribe>

True, I was looking into silverlight at one point and it seemed like LINQ was the only way.

-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx [mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Wednesday, October 21, 2009 1:58 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] XAML and WPF

Is LINQ the only way?

Don't see why LINQ would be the only way. You're in .NET any data access mechanism should work just fine.

-Walden

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.