On Dec 18, 2007 8:18 AM, MB Software Solutions <
[EMAIL PROTECTED]> wrote:

> Stephen Russell wrote:
> > On Dec 18, 2007 3:54 AM, Alan Bourke <[EMAIL PROTECTED]> wrote:
> >
> >
> >> For once the 'ol Fox gets a mention in the context of LINQ.
> >> http://www.regdeveloper.co.uk/2007/12/18/visual_studio_2008_review/
> >>
> >>
> >
> > -----------------------------------------------------------------
> >
> > I read the article and wonder what they mean by reference.  "First, LINQ
> is
> > exactly what its name suggests: query extensions built into .NET
> languages,
> > reminiscent of dBase and FoxPro, except that LINQ is more flexible
> because
> > it can target arbitrary data sources, such as an XML document, or any
> > enumerable .NET object. Second, LINQ to SQL is what software architect
> Matt
> > Warren describes in an illuminating blog
> > post<
> http://blogs.msdn.com/mattwar/archive/2007/05/31/the-origin-of-linq-to-sql.aspx
> >as
> > "possibly Microsoft's first
> > ORM <http://www.service-architecture.com/object-relational-mapping/> to
> > actually ship in ten years of trying.""
> >
> > I don't see the cross over.  Can you Select id, name, city from
> laCustomer
> > or lXMLDocument where CustType ="Active" ?  That is what linq brings to
> the
> > table that was not present in the past.  Granted you don't write it like
> > that.
> >
> > I feel that the article was in error about the use of WPF.  We are
> working
> > on a major tools rewrite using WPF and WCF and Linq.  It's a learning
> issue
> > on how to work with a different set of controls but they bind with data
> very
> > well!  The article made no mention that the core of 3.5 was released in
> 2006
> > as 3.0 with addons to 2.0 named WPF, WCF, WF, and cardspace.
> >
> >
>
> I see M$ still recommends the Win Forms approach however for LOB (line
> of business) applications, and advises against WPF for the same:
>
>    Further, Microsoft itself has muddied the waters by declaring that
>    WPF is not suitable for line-of-business applications. According to
>    Microsoft technical product planner Glenn Block
>    <
> http://blogs.msdn.com/gblock/archive/2007/10/26/wpf-composite-client-guidance-it-s-coming.aspx
> >:
>    "Win Forms is the recommended breadth solution for LOB application
>    development for the foreseeable future."
>
--------------------------------------------------------------------------

"2. *WPF does not offer the "Drag" and "Drop" Win Forms **development*
*experience.
*CAB  development scenarios depend upon the rich tooling and productivity
experience provided by Visual Studio.  The WPF developer experience is
entirely different  and incompatible.  We feel that customers  will not
succeed in mechanically migrating their existing WinForms applications to
WPF  and should not try. There are no upgrade wizards  such as the VB6 to
VB.NET migration tools.  The transition from WinForms to WPF requires
substantial effort and most developers face a steep learning curve. For
these  reasons, the new offering  will not focus on migration scenarios."

After reading that statement I think that the author has an agenda for his
"CAB" project to be released in the future.  Yes you can enable Drag and
Drop in WPF, it just takes a little work :)  You have to capture the mouse
clicks and override them.

I saw a replacement of a typical presentation you would see in powerpoint
using WPF instead.  Much nicer I have to say.


-- 
Stephen Russell
Sr. Production Systems Programmer
Mimeo.com
Memphis TN

901.246-0159


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to