Re: Why VC++ ,Why not C#,VB for windows applications
- From: "Sgt. York" <york@xxxxxxxxxxxxxx>
- Date: Mon, 26 Jun 2006 07:46:56 -0700
Tim Ward wrote:
"Sgt. York" <york@xxxxxxxxxxxxxx> wrote in message
news:Ft2dnSKCrpuRXQPZnZ2dnUVZ_oCdnZ2d@xxxxxxxxxxxxxxxxxx
Mark Randall wrote:floor<nicetom786@xxxxxxxxx> wrote in message
3.What advantages does programming with MFC have over VB if I everMFC wipes the floor with VB (6) in terms of speed, but VB6 wipes the
build the same Windows application?
with MFC in terms of design environment etc, debugging etc.Amen to the former. Think Formula 1 versus a 1969 microbus. I'm just
finishing up a large porting project, a big VB6 app to MFC and have been
astounded by the results. Also, in terms of debugging, VB6 is
hopelessly inadequate in comparison to the machine-level debugging
afforded by the MFC development environment. There is no comparison.
Well, by the time I've put the clever stuff in a C++ DLL anyway (there are
all sorts of reasons to have to do this when the main GUI is in VB) I find
that I'm running the VB IDE under the VC++ debugger, so two nested debuggers
on the go at once ...
--
Tim Ward
Brett Ward Limited - www.brettward.co.uk
I've been doing this lately as well (running the VB "debugger" inside the VC debugger). There's some sort of twisted irony going on here ...
-York
.
- References:
- Why VC++ ,Why not C#,VB for windows applications
- From: nicetom786
- Re: Why VC++ ,Why not C#,VB for windows applications
- From: Mark Randall
- Re: Why VC++ ,Why not C#,VB for windows applications
- From: Sgt. York
- Re: Why VC++ ,Why not C#,VB for windows applications
- From: Tim Ward
- Why VC++ ,Why not C#,VB for windows applications
- Prev by Date: Re: Access Databases, MFC and VS2005
- Next by Date: Re: Why VC++ ,Why not C#,VB for windows applications
- Previous by thread: Re: Why VC++ ,Why not C#,VB for windows applications
- Next by thread: Re: Why VC++ ,Why not C#,VB for windows applications
- Index(es):
Relevant Pages
|