| T O P I C R E V I E W |
| hunt007 |
Posted - Feb 18 2014 : 8:51:17 PM
1>
Unhandled exception at 0x76de2eec in devenv.exe: 0xC000041D: An unhandled exception was encountered during a user callback.
> KernelBase.dll!_RaiseException@16() + 0x48 bytes
clr.dll!RaiseTheExceptionInternalOnly() + 0x149 bytes
clr.dll!IL_Throw() + 0xf5 bytes
Microsoft.VisualStudio.Shell.Design.ni.dll!611b7620()
[Frames below may be incorrect and/or missing, no symbols loaded for Microsoft.VisualStudio.Shell.Design.ni.dll]
Microsoft.VisualStudio.Editors.ni.dll!12cb2590()
Microsoft.VisualStudio.Editors.ni.dll!12cb2620()
System.Windows.Forms.ni.dll!6caed793()
System.Windows.Forms.ni.dll!6cadcc32()
Microsoft.VisualStudio.Editors.ni.dll!12cb1958()
System.Windows.Forms.ni.dll!6caecc35()
System.Windows.Forms.ni.dll!6cad76b4()
System.Windows.Forms.ni.dll!6cb6bab6()
System.Windows.Forms.ni.dll!6cd6c6a3()
System.Windows.Forms.ni.dll!6c486308()
System.Windows.Forms.ni.dll!6c48e71a()
System.Windows.Forms.ni.dll!6c485fa1()
System.Windows.Forms.ni.dll!6c485f89()
System.Windows.Forms.ni.dll!6ca0f8e6()
user32.dll!__InternalCallWinProc@20() + 0x23 bytes
user32.dll!_UserCallWinProcCheckWow@36() + 0x1a4 bytes
user32.dll!_DispatchClientMessage@24() + 0xdc bytes
user32.dll!___fnDWORD@4() + 0x36 bytes
ntdll.dll!_KiUserCallbackDispatcher@12() + 0x2e bytes
user32.dll!_SendMessageWorker@24() + 0x117 bytes
user32.dll!_SendMessageW@16() + 0x12b bytes
comctl32.dll!Edit_NotifyParent() + 0x34 bytes
comctl32.dll!EditML_DeleteText() - 0x5b0 bytes
comctl32.dll!EditML_Char() + 0xa2 bytes
comctl32.dll!EditML_WndProc() - 0x38005 bytes
comctl32.dll!Edit_WndProc() + 0x4e1ea bytes
user32.dll!__InternalCallWinProc@20() + 0x23 bytes
user32.dll!_UserCallWinProcCheckWow@36() + 0x1a4 bytes
user32.dll!_CallWindowProcW@20() + 0x8b bytes
System.Windows.Forms.ni.dll!6c4864c6()
System.Windows.Forms.ni.dll!6c4864c6()
System.Windows.Forms.ni.dll!6c490117()
System.Windows.Forms.ni.dll!6c4900d6()
Microsoft.VisualStudio.Editors.ni.dll!12cbd190()
System.Windows.Forms.ni.dll!6c485fa1()
System.Windows.Forms.ni.dll!6c485f89()
System.Windows.Forms.ni.dll!6ca0f8e6()
Microsoft.VisualStudio.Platform.WindowManagement.ni.dll!69ec31ed()
user32.dll!__InternalCallWinProc@20() + 0x23 bytes
user32.dll!_UserCallWinProcCheckWow@36() + 0x1a4 bytes
user32.dll!_DispatchMessageWorker@8() + 0x200 bytes
user32.dll!_DispatchMessageW@4() + 0x10 bytes
VA_X.dll!1ee90588()
msenv.dll!SCM::FPushMessageLoop() + 0x8c bytes
msenv.dll!SCM_MsoCompMgr::FPushMessageLoop() + 0x2a bytes
msenv.dll!CMsoComponent::PushMsgLoop() + 0x28 bytes
msenv.dll!VStudioMainLogged() + 0x22a bytes
msenv.dll!_VStudioMain() + 0x78 bytes
devenv.exe!util_CallVsMain() + 0xdb bytes
devenv.exe!CDevEnvAppId::Run() + 0x693 bytes
devenv.exe!_WinMain@16() + 0x9c bytes
devenv.exe!operator new[]() + 0xb31c bytes
kernel32.dll!@BaseThreadInitThunk@12() + 0xe bytes
ntdll.dll!__RtlUserThreadStart() + 0x24 bytes
ntdll.dll!__RtlUserThreadStart@8() + 0x1b bytes
2>
Steps to repro, try editing a Resources.resx file |
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Aug 19 2014 : 3:28:50 PM
Does any form of editing cause this crash, or only some forms of editing?
I cannot reproduce this problem, simply using a simple macro that sets the file to read only, using the line you posted. So its possible you are doing a different type of editing, some specific action.
Or the macro could be a factor. Would you be able to post or send me a copy of the macro you are using, along with any instructions I need to know how to use it? If you need to send me any files, please submit them via the form:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up. |
| hunt007 |
Posted - Aug 19 2014 : 07:58:35 AM
I have a script which makes any new file open in VS immediately "read-only".
I also have macros mapped to keyboard shortcuts to make toggle files read-only/rw as I want.
If I open a .resx file, the macro marks it read-only. Now if vax is installed and I try to edit that file, it crashes.
Without VAX it doesn't.
Anyway, the bottom-line is vax shouldn't cause crash. |
| feline |
Posted - Aug 13 2014 : 12:32:50 PM
Are you editing the document using the macro, or are you editing the document manually?
Why are you setting the Resources.resx file to read only with an IDE macro? Especially why set it to read only when you are going to edit it? This just seems like an odd situation. |
| hunt007 |
Posted - Aug 13 2014 : 12:14:57 PM
this is waaay old, but anyways the issue occurs when u edit a Resources.resx that has been marked 'Read-Only' by using Visual Studio Macros - DTE.ActiveDocument.ReadOnly = True |
| feline |
Posted - Feb 19 2014 : 12:29:37 PM
Thank you for the bug report, and apologies for this problem.
Your step 2, how easily can you reproduce this? Are you just making a simple edit to the Resources.resx file in the text editor, treating this as a simple XML file? Or are you editing it via some other view in the IDE?
I have just loaded two Resources.resx files, one for a C# project and one for a VB.NET project, opening them via VA's Open File dialog, so I get XML files in the editor, and I am adding new lines and editing existing lines, and I am not seeing any problems here.
I am using VS2010, VA 2023 under Windows 7 64bit. Do you know if there are any other steps I should be following to reproduce the problem here?
If you have the time, could you please make a new default C# forms application and see if you see the crash when editing the Resources.resx this project contains? Its possible this is somehow a project specific problem, which this will test. |
|
|
