At Line 2406 in WinFrm.cpp, ShowWindow is called. This occurs during the 'ProcessShellCommand(cmdInfo)' call within the InitInstance function which is part of the CWinApp derived class created by the MFC AppWizard.Could you make the otherwise very simple tasks of creating instances of the document, frame and view objects any more complicated and obtuse? Oh, that's right; you Redmondians think obfuscation is a good thing ... It's not!This errant ShowWindow call occurs before the correctly placed and timed ShowWindow call within the InitInstance member function itself which is immediately after the ProcessShellCommand call. It looks like this errant ShowWindow call can be avoided with a flag, but this is the behavior of an MFC application, 'out of the box.'What's going on over their in MFC land at Microsoft?We application developers would like to be the ones to call ShowWindow. We don't want you MFC guys calling it for us deep within your MFC code.I know it does this 'by design.' It's a defective design!Thank you so much for looking into this !
Visual Studio/Silverlight/Tooling version
What category (if any) best represents this feedback?
Steps to reproduce
Operating System Language