Excel Vba Made Easy and Visual Basic 6 Made Easy
Re:Yep. I just did some searching and you are right. It is because I have the Standard edition. It's ok though, I will grab the enterprise edition from college tomorrow.
Thanks a lot for your help guy!
Dan
C-Section Recovery & Health Guide
Re:By the way, the best site to learn Win32 using MFC: CodeProject (http://www.codeproject.com)
The Potent Visualization Technique
Re:Perhaps it is because you have a "Standard" copy of VC++. Not sure, so you may want to experiment with that Settings dialog to see if that option is there.
My Visualization
Re:Hi guy. Thanks a lot for your helpful reply
Questions 1 and 2 are completely answered to me now. But question 3, about where I go to Project, then to settings, then to the General tab, I see the pulldown menu for Microsoft Foundation Classes, and it only has one option which is Use MFC in a Shared DLL, which is the currently selected one obviously. I tried the pulldown menu and there are no other options. All I have open right now is the project itself in the workspace. Any reason why Use MFC in a Static Library is not listed?
Thanks again
Dan
Alternative Hepatitis C Treatments
Re:Hi,
RE: (1)
In the resource editor, just double click the button, and a dialog comes up to ask you what method you want the on-click handler to map to. Just edit the name (if needed), and click OK. A method by that name will be automatically added.
RE: (2)
There are many ways to do this, but it really depends on what kind of changes you are making. If you use the ClassWizard, the changes may impact multiple files. The way I do it is to just copy the whole project (directory) in a different directory, and go from there.
RE: (3)
By default, your project will by "dynamically" liked to the MFC DLL's. If you *don't* want to have to distribute the DLL's, then go the Project's Menu Item->Settings-> General Tab, and where it says"Microsoft Foundation Classes" (Combo Box), select "Use MFC in a static Library. When you build the executable, all the code needed by MFC will be put into your executable and you will not need the DLL's. However, this will increase your executable size as well as the build-time. So, do this *just* for your Release build; leave it alone for the Debug build (Select the build type in the same Project Settings dialog – there is a Combo Box at the left which specifies the Debug/Release project type).
0 Comments.