Submitted by As the final runup to Vista RTM continues, Microsoft has announced that the .NET Framework 3.0 (formerly WinFX) has RTMed and is available on Microsoft Downloads. This is a significant milestone for the Developer Division, and delivers on some of the promises of Windows Vista programmability on earlier platforms.
Considering that .Net 3.0 is supposed to be the Win32 API replacement, effectively, for Vista, wouldn’t it have been sensible to release the programming platform well in advance and not weeks before the actual OS itself?
It was released well in advance. Just not in RTM form.
As long as I know, is not a replacement for the Win32API, not yet.
🙂
Considering that .Net 3.0 is supposed to be the Win32 API replacement, effectively, for Vista, wouldn’t it have been sensible to release the programming platform well in advance and not weeks before the actual OS itself?
It is not a replacement for the Win32 API.
But you have been able to download beta versions for a long time as well as tools to program for it.
.NET 3.0 is:
Windows Presentation Foundation Classes (WPF) [Avalon] – The technology for building rich Windows applications with special features for managing layout, text, 2-d and 3-d graphics and much more.
Windows Communication Foundation Classes (WCF) [Indigo] – A new framework for inter-process communication that will change the way we interact with web services and the way we implement remoting.
Windows Workflow Foundation Classes (WF) – This is a framework for creating workflow engines that can be incorporated into your application
Info Spaces [InfoCards] – A very nice way to deal with controlling how you identify yourself and how much information you provide on the web.
One correction: The name for Microsoft’s implementation of information cards is CardSpace.
It is not a replacement for the Win32 API.
.Net is now what Microsoft want you to use to program on Windows. In the case of Vista the Win32 API and COM is still there for legacy reasons, but you’re not going to be able to get access to any of the new Vista stuff like Avalon unless you do .Net. It’s that simple. For that reason it is replacing the Win32 API and COM.
Info Spaces [InfoCards] – A very nice way to deal with controlling how you identify yourself and how much information you provide on the web.
Wow. Pulled straight out of Microsoft’s marketing backside. I can identify myself well enough, thank you very much.
For that reason it is replacing the Win32 API and COM.
Nope. Native applications will still be using the Win32 API.
If you want a managed application, you should use .NET.
Hybrid applications use both.
http://msdn.microsoft.com/windowsvista/downloads/products/getthebet…
For that reason it is replacing the Win32 API and COM.
It’s still implemented using unmanaged code, for that reason it can’t replace win32.
Released to mirrors?
Rejected that monstrosity?
Returned the milk?
http://en.wikipedia.org/wiki/Release_to_manufacturing
Take this acronym lovers:
LMAOROTFLBTCSTCNDBFOOTWI FOAGWLLBGWTHROOTSAIAKBAYB
“I have a serious brain disease, please give me a cat.”
Released to mirrors
lol
I think I saw it on http://ftp.gwdg.de and mirror.pacific.net.au , lol 🙂
The current .net implementation is using the win32 api, to perform many things, so you might as well call it a nice wrapper around an api that should have died 10 years ago*.
*Yes I have developed software to the win32 api. It’s an interesting expierence.
*Yes I have developed software to the win32 api. It’s an interesting hack
There fixed that for ya