Again one problem I've been facing for many years.
In ResourceView when I select multiple items of different types (e.g. a dialog
box resource, a bitmap and a menu) and display their properties VC crashes as
soon as I press enter. I want to be able to do this mostly to change the
language property in one go instead of doing all resource items one by one. Hope
it'll be fixed in a near service pack, too.
FYI: the assembly line where the error occurs (memory exception, access denied)
is the following:
50091CD3 call dword ptr [eax+6Ch]
dword ptr [eax+6Ch]: 0000000A ???
Vince C.
Vince,
Which version(s) of VC++ does this occur with?
Dave
--
MVP VC++ FAQ: http://www.mvps.org/vcfaq
Visual Studio 6.0 SP5. It would have been nicer if I'd said it :-)
Vince C.
Thanks for posting in the group.
Based on my understanding, the issue is: In ResourceView of VC 6.0 SP5,
when you select multiple items of different types (e.g. a dialog box
resource, a bitmap and a menu) and display their properties, VC crashes as
soon as you press enter.
I did reproduce the problem that you describe. I will report it to our
product team and get back here with more information here as soon as
possible.
If you have any more concerns on it, please feel free to let me know.
Best regards,
Yanhong Huang
Microsoft Community Support
Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
By the way, we can send post notify email to you if there is useful update
for your posts in the newsgroup. If you want to receive the notify email in
the future, please register your no spam email address at:
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
Have a good day.
I have checked it with product group. This is a known issue with VS6. This
bug has been fixed in VS.NET and higher. Please Check the following KB
article.
http://support.microsoft.com/?id=240017
"FIX: Selecting Multiple Controls in ResourceView Causes VC to Fail"
Thanks very much. If you have any more concerns on it, please feel free to
post here.
:-) I would have bet this was fixed in VS.Net... But will the VStudio 6
community (I'm sure it's not so small even after .NET) have a chance to see this
problem solved one day?
Vince C.
Thanks very much for your update. :)
Based on the feedback from product team, there is no fix for VS6 on this
issue yet. If this issue affects you and your team quite much, I suggest
you submit a service request to Microsoft Product Support Service to ask
for a hotfix for it. Since it is a known product issue, it should be a free
support incident.
The link is: http://support.microsoft.com/default.aspx?scid=sz;en-us;top
If there is anything unclear, please feel free to post here.