Original address
https://channel9.msdn.com/showpost.aspx?postid=31152
The origin is a person's remarks of the VC development group "MFC is only used to support old code, and the new code should not be written in MFC, but should use C # or Managed C ."
BLKBAM view: I am still very early
The author's point of view: I have a profound lesson on the WFC, and my time is wasted.
SIMO's view: The MFC will stick to the NT core and the COM mechanism. Mr. Box '' COM IS Not Dead - It's Just Done 'can also be used for MFC. VB6 is slowly dying.
View of Charles: This is evolution.
CIDER's point of view: MFC died of this point for at least 5 years.
Sven Groot View
: MFC stop development does not mean you to develop. .NET is Microsoft's current strategy, but not yours. SHREYASONLINE
: Nothing is permanent
The author's point of view: The MFC will not extend for the new API, and Microsoft has changed C for .NET to change the C . So I don't think MFC8 is worthwhile. I am very happy that I can use Java. Cider
Views: Java and C # are developed by C , so don't just criticize Microsoft invent of managed C . From your experience, you shouldn't be a guy who is also a cloud, let go of yourself. But the biggest IT company has a lot of bets, which side you are? Warren's point of view: You are complaining
.NET compatibility? Is there any mono on Linux? Tom Malone's view: Mono always supports a branch of .NET, but the server uses Linux and Mono, the client continues to use Windows and .net is also good.
Rossj
: But there is a guy to ensure that "only one written, you can run". What language is there any language?
Dweller view
: MFC matures. WinFX still keeps the non-hosting interface MIKE DIMMICK: MFC is not already improved to support .NET and WINFORM?
The author's point of view: If there is an abstract layer, then I can write a cross-platform code. I mean is how much time I have invested above, and Microsoft is promoting new technologies. This happened in WFC, VB K-6, MASM, and Quick Basic, and now it is in the point of view of mfcrossj: What is the reason you do not use?
WINELIB? Is it not finished?
Eddwo's view: I see you very interested in WinFX's hosting interface. But I have seen the high-level API of the document is hosted. Only the bottom layer Avalon API is non-hosted. Although you can use unmanaged programs to handle intermediate language code, will the non-managed program have all the features of Avalon?
Author's view
: WINELIB is a disaster, full of problems. I think Windows Longhorn will have a regular library, so I will continue to develop on Windows, but I will continue my development on Linux and use an existing cross-platform development plan.
