Udostępnij za pośrednictwem

WinFX CTP here we come...

  • Artykuł

As Rudder say, we are well on our way to getting the first combined CTP drop of Indigo and Avalon out the door. It is a baby-step on the way to the final release, but an important baby step. While the install experience is not as seamless as we would like, the drop does runs great on XP… I can’t wait to see the apps you folks come up that use the cool features of Indigo and Avalon together. Please send me your links when you get an app up, I’d love to plug it here ;-)

Comments

  • Anonymous
    February 08, 2005
    To which VS2005 release will it be tailored? Because it's slightly disappointing right now that I can't run the december CTP of VS in parallel with Avalon.
  • Anonymous
    February 09, 2005
    The comment has been removed
  • Anonymous
    February 09, 2005
    Mario,

    Eric Rudder mentioned that the WinFX CTP (Avalon + Indigo) will be released along with a compatible VS 2005 CTP.

    I also heard that WinFX has a new name now - WAP or Windows API.

    Mujtaba.
  • Anonymous
    February 09, 2005
    Over by dead body! We are not going to call it WAP…
  • Anonymous
    February 09, 2005
    WAP? Blech. I really like the WinFX (Windows Framework) name.
  • Anonymous
    February 09, 2005
    :) I may have mis-heard.

    Anyways, as long as it keeps improving, most people won't care what's it called - WinFX, managed Win32/64 SDK, platform SDK, or whatever.
  • Anonymous
    February 09, 2005
    WAP? WAPI? Might as well call it Common Runtime Application Programming Interface :-) Keep it WinFX, the name sticks and sounds goods. :-)
  • Anonymous
    February 09, 2005
    I like WinFX (at least better than the alternatives mentioned).
    The only problem with it is that it's very close to WinFS when you say it.
  • Anonymous
    February 09, 2005
    Three questions on three features:

    Are there Video/Audio support?
    Are there Printing support?
    Are there Rich-Text support?
  • Anonymous
    February 10, 2005
    I concur with Kevin on that one. This came up some time ago when someone at MSFT asked on their blogs about suggestions (maybe it was this one?), and it still catches me to this day. It's kind of odd that two of the three pillars have codenames, but third doesn't and is very similar to the full API (and potentially the OS name). Too bad the .Net suffix got beaten to death prematurely, because "Storage/Display/Communication.Net" (whatever the pillars' true names would be + ".Net") would have actually deserved to have the ".Net" monikor.
    On the API name, I'm still putting my money on Longhorn being ultimately called "Windows FX" would have been better than calling the API WinFX, IMO, given what Aero is supposed to be. But then, "FX" also got beaten to death a couple of years ago. It's a testament to the versatility and durability of the letter 'X', I guess :)
  • Anonymous
    February 10, 2005
    WAP??? NO WAY