469,631 Members | 1,270 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,631 developers. It's quick & easy.

Error using Event Wizard "...parent class code is read only"

When attempt to use the Event Wizard I get the following error message:

"Add/Remove of the function impossible, because the parent class code is
read only"

The Project was convert from VC 6.0. The files in question do not have the
Read-Only Attribute on.
Any Ideas?
Nov 17 '05 #1
8 1481
Hello John,
We have reviewed this issue and are currently researching on it. We will
update you ASAP. Thanks for your patience!

regards,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties and confers no rights.

Nov 17 '05 #2
Hello John,
We have reviewed this issue and are currently researching on it. We will
update you ASAP. Thanks for your patience!

regards,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties and confers no rights.

Nov 17 '05 #3
Hi John

Based on my understanding, the problem is you could not use the event
wizard to add a event handler to your MFC class which is converted from the
VC6 program. Please let me know if I have misunderstood anything.

In order to isolate your problem, would you please give us some more
detailed information about this problem:

1. Have you used some source control system with this MFC project, such as
the Visual Source Safe with the VStudio?

2. Is it a project-dependent issue--I mean if you have another VC6 MFC
project and convert it to VC2003, does this problem occur?

3.Which class you this problem with, is it a MFC generic class(e.g.
CButton) or a custom MFC class you derived?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! :C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 17 '05 #4
Hi John

Based on my understanding, the problem is you could not use the event
wizard to add a event handler to your MFC class which is converted from the
VC6 program. Please let me know if I have misunderstood anything.

In order to isolate your problem, would you please give us some more
detailed information about this problem:

1. Have you used some source control system with this MFC project, such as
the Visual Source Safe with the VStudio?

2. Is it a project-dependent issue--I mean if you have another VC6 MFC
project and convert it to VC2003, does this problem occur?

3.Which class you this problem with, is it a MFC generic class(e.g.
CButton) or a custom MFC class you derived?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! :C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 17 '05 #5


Hi Gary,

Your basic understanding is correct.

1.. The project members are eventually saved in VSS. However, I don't
feel this is part of the problem, since the problem does happen on a PC that
is connected to VSS .
2.. I have not tried it on other projects, yet . See #3
3.. The class that fails is: cBaseFrame derived from CFrameWnd (class
cBaseFrame : public CFrameWnd)
1.. I have been flipping back to VC 6.0 and using Class Wizard to insert
the Event Functions framework (Menu Commands)
2.. If I specify a class derived from CWnd it works.. all is well
Seems that a class derived from CframeWnd is the problem.

Hope this helps..

JEK

""Gary Chang[MSFT]"" <v-******@online.microsoft.com> wrote in message
news:XK**************@TK2MSFTNGXA01.phx.gbl...
Hi John

Based on my understanding, the problem is you could not use the event
wizard to add a event handler to your MFC class which is converted from the
VC6 program. Please let me know if I have misunderstood anything.

In order to isolate your problem, would you please give us some more
detailed information about this problem:

1. Have you used some source control system with this MFC project, such as
the Visual Source Safe with the VStudio?

2. Is it a project-dependent issue--I mean if you have another VC6 MFC
project and convert it to VC2003, does this problem occur?

3.Which class you this problem with, is it a MFC generic class(e.g.
CButton) or a custom MFC class you derived?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! :C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Nov 17 '05 #6


Hi Gary,

Your basic understanding is correct.

1.. The project members are eventually saved in VSS. However, I don't
feel this is part of the problem, since the problem does happen on a PC that
is connected to VSS .
2.. I have not tried it on other projects, yet . See #3
3.. The class that fails is: cBaseFrame derived from CFrameWnd (class
cBaseFrame : public CFrameWnd)
1.. I have been flipping back to VC 6.0 and using Class Wizard to insert
the Event Functions framework (Menu Commands)
2.. If I specify a class derived from CWnd it works.. all is well
Seems that a class derived from CframeWnd is the problem.

Hope this helps..

JEK

""Gary Chang[MSFT]"" <v-******@online.microsoft.com> wrote in message
news:XK**************@TK2MSFTNGXA01.phx.gbl...
Hi John

Based on my understanding, the problem is you could not use the event
wizard to add a event handler to your MFC class which is converted from the
VC6 program. Please let me know if I have misunderstood anything.

In order to isolate your problem, would you please give us some more
detailed information about this problem:

1. Have you used some source control system with this MFC project, such as
the Visual Source Safe with the VStudio?

2. Is it a project-dependent issue--I mean if you have another VC6 MFC
project and convert it to VC2003, does this problem occur?

3.Which class you this problem with, is it a MFC generic class(e.g.
CButton) or a custom MFC class you derived?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! :C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Nov 17 '05 #7
Hi John,
1.. The project members are eventually saved in VSS. However, I don't
feel this is part of the problem, since the problem does happen on a PC thatis connected to VSS.


Except the concern of the VSS, this problem could be caused by some related
solution files being corrupted. In such scenario, you can try to
delete(rename) your solution's .suo file and .ncb file, then reload the
solution in the VS2003 IDE, the .suo file and .ncb file will be regenerated
by the IDE.

If the above workaround does not work, maybe you need to test your project
in another machine in order to check whether this is a VS2003 IDE(machine)
specific issue or a code deficit issue. If your project is OK in another
test machine, then there may be some problems in the VS2003 of your current
working machine, I suggest you can do a VS2003 reparation to it.
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! :C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 17 '05 #8
Hi John,
1.. The project members are eventually saved in VSS. However, I don't
feel this is part of the problem, since the problem does happen on a PC thatis connected to VSS.


Except the concern of the VSS, this problem could be caused by some related
solution files being corrupted. In such scenario, you can try to
delete(rename) your solution's .suo file and .ncb file, then reload the
solution in the VS2003 IDE, the .suo file and .ncb file will be regenerated
by the IDE.

If the above workaround does not work, maybe you need to test your project
in another machine in order to check whether this is a VS2003 IDE(machine)
specific issue or a code deficit issue. If your project is OK in another
test machine, then there may be some problems in the VS2003 of your current
working machine, I suggest you can do a VS2003 reparation to it.
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! :C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default...sdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 17 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by Grant Richard | last post: by
1 post views Thread by fl | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.