In this blog entry by James Kyton, he talks about the next versions of Windows (Fiji and Vienna...in that order). Fuji seems to be Vista 1.1 as it is adding features that were dropped. Of most interest to me is the fact that the WinFS name is rearing is head again. The article states that for Fiji:
While I think its interesting that the new drop of WinFS will be shown at the upcoming TechEd (too bad I couldn't get there this year), what I have seen so far doesn't have me too excited. I played with Beta 1 a bit and was certainly a FanBoy for the early WinFS with Vista before that got yanked.
I have built a test-vista machine to do some WinFX stuff on and it got me wondering...why do I need to run the WinFX runtime installation on Vista? Isn't this supposed to be pre-installed? Aren't some built-in Vista apps already using WinFX? I am so confused. Anyone know?
Hey everybody look...its not a Silverlight post ;)
I really like this post by Adam Barr in response to Scoble's blog about what happened to WinFS. I think Adam is right on with his take on how long-term projects are scheduled. Whether this is what happened to WinFS or not is up to speculation...ok...let me speculate.
After spending hours digging through Longhorn builds to try and understand WinFS, I have to say that I am really bummed that it is getting pushed out. I think I understand Redmond's approach here, but they've been promising something like WinFS for years now.
Today, I am quoted in e-Week about my opinion of what's happening to Longhorn...specifically about WinFS. Hope I didn't offend anyone in Redmond ;)
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 spent a couple hours digging back into the new WinFS. So far it seems interesting, but only as a new datastore. It doesn't seem to be trying to be the Object File System from teh Cairo days, though that may be because of it's bolted-on status on XP. It is still stored in a SQL Server engine, so that is good. It also looks like the actual files (not just the metadata) are being stored there.
I will probably update my WinFS DB Explorer and release it next week with the new bits. Being able to look at the DB would be fun!
As any of my readers will probably know, WinFS is a hot/sore spot for me. To my surprise, Tom Rizzo dropped a Beta of WinFS (and it supposedly is backwards compatible with XP) on MSDN a day or two ago.
|Building a Web App with ASP.NET Core, MVC6, EF Core, Bootstrap and Angular (updated for 2.0)|
|Using Visual Studio Code for ASP.NET Core Projects (new)|
|Implementing and Securing an API with ASP.NET Core|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|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|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||22.214.171.124||Runtime Framework||.NETCoreApp,Version=v2.0|
|App Path||D:\home\site\wwwroot\||Runtime Version||.NET Core 4.6.26020.03|
|Operating System||Microsoft Windows 10.0.14393||Runtime Arch||X86|