Hey, Alejandro,

There is no question that data handling (and data binding) can and will be improved in Whidbey.

But one needn't think that cherished features have been truly lost in the current version of .NET. It's all about paradigm shift. For example, I'm involved in upgrading a large Fox application to .NET, where stored procedures are being developed for result sets. Over the last few weeks, we had to make significant changes to result sets used for reports - in most instances, we were able to do so in our stored procs, and without C# code changes.

Our result sets are designed to be client-agnostic. We've found this approach to be quite clean, and arguably better long-term.

For those instances where some special data munging is needed that wasn't done in the back-end, I've found the capabilities in ADO.NET (filtering, relations, etc.) to be sufficient. IMO, the capabilities in ADO.NET are sometimes understated.

Same goes for reflection - there's certainly a learning curve when one is building a knowledge base of how to use it in place of macros. There is certainly a shift in the way one does things, but at this point I really don't feel I've truly lost anything. What you potentially gain is a langauge with some great OOP capabilities.

Those building business apps in .NET are less likely to view these as issues.

Kevin