>I see and have read c# being used for WPF; I'm not sold on it being a complete solution yet, perhaps seeing Adobe's new development tool, Microsoft will work harder. I really hate being dragged along by Microsoft in their battle for being the biggest; these language/library wars are very expensive; Microsoft now says all future development is to be done in WPF! I don't have 8,000 Indian programmers working for me, like Microsoft does; my company pays American wages! (Nothing against Indians.)

>I've been reading about Linq and I'm not yet seeing it as necessary for my coding style, >I've been getting along so far without it; sure that may change.

>Be well.


Derek,
I can certainly empathize with your feelings. But you don't need 8,000 programmers to be productive! WPF does have a learning curve but it has some strong similarities to ASP.Net as far as content and code behind. Once you start think of xaml as akin to html it gets easier.

As far as LINQ is concerned, I havent applied it to all situations butLINQ to SQL Server is the way to go (or another good ORM tool, SubSonic??). I promise you, if you take the time to learn the basics that time will be saved in productivity over and over. LINQ just makes SQL Apps too easy. I love it. Absolutely.

An excellent primer on LINQ is actually on Scott Guthrie's blog: http://weblogs.asp.net/scottgu/search.aspx?q=linq&o=Relevance

That will get you started. Seriously, if you are using SQL Server and not LINQ you owe it to yourself to give it a try.