Re: Add MFC Class CObject fails

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Jonathan Payne (jpayne_at_NOSPAM.dsl.pipex.com)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 16:43:14 -0000

I'm working on a similar sized project and I am seeing the same problems.
The only solution I have found is to not use the wizards (not really a
solution).

You might also want to hide the Class View window as it seems to kill
performance if you are working on a large project.

Also, if you are using MFC in DLLs, you might want to take a look at this
post:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&selm=eaqB3H1IDHA.2240%40TK2MSFTNGP11.phx.gbl
(it could save you a lot of time if you hit this bug).

Oh and using the source control integration is really slow and can lead to
crashes when you do a take.

And the linker sometimes bombs after doing an incremental build.

Sorry this post is a little negative - there are lots of good things about
the new IDE and compiler but it is worth knowing about the down sides.

Jonathan

(I am hoping if I mention the these problems enough, the next version of the
IDE might get some serious stress testing and the some of these issuse can
be fixed)

"Bill Roper" <anonymous@discussions.microsoft.com> wrote in message
news:B36E043E-A022-44A4-B1D5-5A25E7103540@microsoft.com...
> We (our company's development group) continue to struggle with VC++ .NET
2003. In an effort to get the system working, we have now completely
rebuilt all of our VC++ 6 projects from scratch, which *has* improved things
somewhat.
>
> We are now able to add property pages and property sheets via the wizard,
which is a substantial improvement over having to do so by hand; the browser
appears to be working again. These are good things.
>
> However, when I try to add a CObject-derived class via the MFC Class
Wizard, the app starts sucking down all of the processing power it can get
and *never* returns. This is not a good thing.
>
> We're working with a very large project here (more than 4000 files shared
among 14 projects in the solution), so I suspect that's part of the problem,
but it appears that something is clearly broken here.
>
> Any thoughts?

Quantcast