project just because it's a mess to try to do in on a file by file basis. I
I agree with David about MSDN. It only takes up disk space if you load it
locally. And the web version is getting more unusable all the time as well
since so many links don't work or lead to obsolete help pages. I've found
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
Has anyone seen these problems before? VS2003.
I want to add a virtual method to my project, and I get the error
"Add/Remove of the function is impossible, because the parent class code
is read only"
Now, OF COURSE the parent class is read-only; the parent class is
CDocument, and all my
standard files such as the MFC source, Platform SDK, etc. are read-only,
but since VS
would not have to modify the parent class files anyway, it has no reason
to complain that
they are read-only!
Another recent one is when I go to add a new MFC class to my project. I
don't recall the
exact text of the message, but it said something along the lines of
Cannot add MFC classes to non-MFC projects
There is nothing I can find that suggests why VS suddenly thinks my MFC
project is no
longer an MFC project.
Two major problems here are that the messages do not have message codes
that could be
looked up; just the annoying MessageBox popping up, with no useful
information at all in
it that could be used to find an MSDN article explaining it, and that the
search mechanism
in the MSDN is so screwed up that it is useless when given the text of the
message (the
minute 500-hit limit has GOT to go! And a USABLE filter-creation
mechanism MUST be
implemented!)
[For example, it might be useful if the MessageBox said something like
Cannot add the "OnOpenDocument" method because the file
<filename here>
<problem description here>
It is hard to believe that it wants to modify the parent class file and
requires
read/write access. Although it IS possible that the programmer who wrote
this particular
piece of code called the wrong validation function, asking to validate the
parent rather
than the class itself. (I checked the file status of the document file of
the class to
which I want to add this; it is definitely NOT read-only)]
And it should, if it thinks the project is not an MFC project, create a
message box with a
hyperlink to the document explaining exactly why it thinks this is not an
MFC project.
MessageBox with fixed text as a concept should be killed off inside
Microsoft. Lumping
together more than one cause of a message to a single message is a
Fundamentally Bad Idea;
every message should be unique to its situation. Therefore, a failure to
add a function
and a failure to delete a function are separate concepts and need separate
error messages.
Also, it is probably the case that the MSDN doesn't actually document the
error messages
anyway, which is a VERY serious defect!
Any ideas?
joe
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm