What research? All versions of Visual Studio build C++ code into a native image.
While true, some versions produce horribly bloated images (ref. the .... was it CDialog library bug in one or two versions of MFC) making them quite unsuitable to use, or produce images impossible to run on anything but the "Latest And Greatest(tm)" Microsoft Operating System.
It does require research to find out about such things.
From my unfortunate experience ( both with VS or VB ) - the challenge is OS and its "references" to "new" VS versions.
In my cases my "old" VS 6 code was either automatically or semi-outomatically ( Do you want to convert it?) converted to LATEST VS on PC.
It is a "one way" conversion, no returns.
As has been said, moving up the chain of compilers is easier than moving down them.
I strongly suggest creating a brand new solution with VS 2008 and the copying the source files into the structure and adding them.
Migration projects/solutions from Visual Studio 1.52 up to Visual Studio 2010 have all sorts of problems, which only get worse with each conversion. These issues have largely been eliminated in 2010-2013 (though there are some edge cases that are problematic.)
The normal process, is that the compiler converts C language into object modules, and the linker combines object modules and libraries to create an executable program. Google will find you more detailed explanations it you need them.
The same menu, is also created inside in CMainFrm that all command events (even from the CDialog) are routed and handled in there.
The problem is that the acceleration keys in my CDialog are not shown, ie Alt+1 is hidden but the commands are routed just fine.
How can I force to view the acceleration keys inside the CDialog's CMenu ? Note, that I used the LoadAccelerators function successfully on my onInitDialog and I also tried to use ON_COMMAND(xxx,xxxx) in my CDialog without any success.
Can any body help me with C code to solve these two problems since i am not so familiar with C language..Thank you very much.
1.f(N) be the number of points with integer coordinates that are on a circle passing through (0,0), (N,0),(0,N), and (N,N). Figure out f(10000)=? Print out these points.
2.The number 145 is called a curious number,as 1! + 4! + 5! = 1 + 24 + 120 = 145. Find all curious numbers blow 10000 which are equal to the sum of the factorial of their digits. Print out them.
I am trying to make some reusable GUI components for several desktop application projects. These projects are all Windows (Win7), Visual Studio, C++ based. What do you think would be the best way to approach this problem?
Right now i was thinking about one of these 2 ideas:
- MFC ActiveX Control.
- MFC extension Dll.
So far ActiveX has the benefit of being able to be integrated directly in the VS resource editor and this would make the integration easier.
On the other hand, ActiveX would allow only 1 GUI component per .OCX (am i wrong here? is it possible to incorporate more that 1 control in an .OCX file?) and this would mean that i would have to distribute a lot of .OCX files and it would just not look right.
Can you tell me if ActiveX is still considered a "modern" way of doing things? I wouldn't want to use something that is about to be deprecated.