|
Not even close. MVC is a buzzword compliant architecture for web development. WPF/Metro/Win8/Win10/WindowsStore/Modern/WteTheyCallItTomorrow style apps are the intended WinForm replacement and use something called the MVVM (model, view, view model) architecture.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
It seems as though I might not be far off the mark already!
|
|
|
|
|
Rage wrote: There is absolutely no relations between MVC and MFC
Wat M and C doh!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Rage wrote: MFC = Microsoft Foundation Classes, an API that made Windows Programming easier than plain Win32
Er no. MFC is a set of C++ classes (aka bloatware) wrapped around the Win32 APIs. And it certainly did not make Windows programming easier, quite the reverse in fact.
|
|
|
|
|
Richard MacCutchan wrote: quite the reverse in fact
I liked it, and found it far more easy than having to deal with all the messaging thing.
Richard MacCutchan wrote: MFC is a set of C++ classes (aka bloatware) wrapped around the Win32 API
An ... API then.
|
|
|
|
|
They have nothing in common except they are programming related acronyms.
|
|
|
|
|
|
Wow, great minds come together (see my other post). 
|
|
|
|
|
About 16 letters of the alphabet. 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
How Win10 going, I upgraded from 8 a few things (SVN for a start) went side ways but nothing like the problems you seem to having...
|
|
|
|
|
I think it's because I upgraded from 7 (like most people are probably going to)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You better MFC the SQL for the ADO because the .NET and the MVC are WPF.
Of course you can also JVM the WCF for the AOP if OOP isn't what you JEE...
Hope it helped, good luck! 
|
|
|
|
|
Ahh I was missing TLA's! 
|
|
|
|
|
No, there were plenty Three Letter Acronyms in there.
I think what you're missing is the Two Letter Acronyms! 
|
|
|
|
|
|
MFC is dead, long live MVC 
|
|
|
|
|
MFC is dead, I mean when I last saw him he looked peaky, but...
|
|
|
|
|
It's not dead, it's just resting.
It's still provided with VS2013 and IIRC also with VS2015. I don't know how much new development is being done with it...
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
In web-land (and people who like slow quirky windows applications) MFC was replaced by WPF.
Many people didn't like WPF because basically XAML didn't work so well. So instead of fixing it, they made us all use MVC to separate our code and presentation and, when we had difficulty with that then MVVM came along.....
... (600 lines later) So basically as an industry we have no idea what we are doing. 
|
|
|
|
|
Why the joke icon ? 
|
|
|
|
|
Ahh, it was WPF not MFC, I though it felt wrong typing it!
|
|
|
|
|
I think the joke is on me...
|
|
|
|
|
Quote: So basically as an industry we have no idea what we are doing. Poke tongue |
So not just me then!
|
|
|
|
|
COBOL. The future is COBOL.
And turtles. If you like shell scripting.
|
|
|
|
|
From below I think you meant WPF and MVC
MVC is MS Web development - Model View Controller where the View is the web page )although the term itself is a generic one referring to the pattern, it has been adopted by MS as their web technology that replaced Webforms)
WPF is Windows Presentation Foundation - the technology which has replaced WinForms by describing the View in XAML (XML related human-readable hierarchical view descriptions) and allowing simple binding between controls on the view and object properties.
So, if you want to stay MS and work on desktop applications - WPF may be the way to go - although IMHO better now to look at Windows 10 application development.
IF you want to go Web then MVC is the way to go.
If you want to dip your toe into the future then Windows 10 Universal Apps is probably the way to go - this uses Xaml too, so WPF might be a good introduction.
PooperPig - Coming Soon
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
