In Luca Bolognese's PDC presentation on ObjectSpaces, he stated in a diagram that you should use ADO.NET's objects DataSets/DataReaders if "You require maximum control/performance/functionality" That seems to indicate that we should not use ObjectSpaces if performance, funcationality and control are a requirement. If this is the case, it would seem that using ObjectSpaces in WinFS is very contrary. WinFS has to be quick...not just fast...lightning fast. We are talking about impatient users.
I think it is important that we get Mike Deem to respond to this in his Blog. I am going to forward this to him and post it up on the newsgroups, but maybe I am missing something.
I've been following some threads on the DevelopMentor .NET Mailing Lists about what is a good solution for O/R Mapping. I am intrigued by a couple of ideas, especially ones that no one seems to be talking about:
I have felt a little left out in the cold lately when it comes to O/R mapping. I have spent the last two years on my soapbox about using DataSets (more specifically Typed DataSets) as the answer to Business Objects. I have known I am odds with other data-centric authors/speakers out there, but I still think that Typed DataSets are a good solution now and in Whidbey. But what about ObjectSpaces?
I got to play with an Itanium 2 Box at the PDC today. Instead of following their script, I did what I've wanted to do for months...creating a huge DataSet. They had an interesting setup. You used a Pentium 4 box to develop code and then Terminal Service'd into a sixteen-way Itanium 2 machine to run the code. The 64 bit JIT's the IL to 64 bit code from the same assembly that the 32 bit JIT did to create the 32 bit code.
I say some interesting results:
Being at the PDC has been a blast, but a bit overwhelming. There is so much to see and so many people to meet. I have come away from the first few days with a couple of observations:
After attending most of the Keynote this morning at the PDC I am convinced that Microsoft is headed in the right direction, but it is still a long way off. 2005 or 2006 is too long to plan towards. On other note, Yukon and Whidbey will be here soon. Its about time to start planning for these technologies now.
I'll blog in more detail later tonight about what these technologies mean to you.
Other than LAX being 'smoked' in, there is not much to report today. A number of MS employees seem to be stuck at SeaTac waiting for the smoke from the bush fires to clear out. On my way in last night, we flew over the fires. It was pretty impressive. We were in a holding pattern over the fires and could smell the wood smoke in the plane. After a few nervous passengers asked the staff, we were reassured that it was only from the fires below
Since I am not registered for the pre-Conference sessions, there isn't much to do today. After walking around the conference hall, it is clear that this conference is all about Yukon, Whidbey and Longhorn. No doubt about it.
Well, I am off to LA Saturday morning. In all the years I've been doing this stuff, I've *never* been to a PDC. Now I am feeling overwhelmed with what to dig into while I am there. I am lucky that I've had the opportunity to see Longhorn, Whidbey and Yukon before the PDC, but just haven't had the time to dig into Indigo and Avalon.
I'll be blogging intensely throughout the PDC. I will be scouting out SQL Server for O'Reilly as well as trying to find more authors for ONDotnet.com. If you're there and want to share what you know with the managed software world.
Pretty wierd, but this White Lightning 2 car is powered by 6040 C Batteries. And with those batteries it broke the land-speed record going 245 MPH!
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS (New)|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Implementing ASP.NET Web API|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||220.127.116.11||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.24628.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|