1

Topic: Failure in Visual Studio 2019

This is occurring in 2019 Enterprise 16.7.2, but it's been happening for several versions at least.

ViEmu just stops working after certain basic operations (delete word, enter insert mode). An error bar appears on the top of the edit window at roughly the same time. Disabling and reenabling ViEmu fixes it until you do one of those operations again:

https://i.imgur.com/dOvBlsO.gif

These are the errors that appear in the log:

<entry>
    <time>2020/09/09 15:39:23.207</time>
    <type>Information</type>
    <source>Web Editor</source>
    <description>System.ArgumentException: Specified OLE variant is invalid.&#x000D;&#x000A;
        at System.Runtime.InteropServices.Marshal.GetObjectForNativeVariant(IntPtr pSrcNativeVariant)&#x000D;&#x000A;
        at Microsoft.VisualStudio.Html.Interop.CommandTargetToOleShim.TranslateInputArg(Guid&amp; guidCommandGroup, UInt32 commandID, IntPtr variantIn)&#x000D;&#x000A;
        at Microsoft.VisualStudio.Html.Interop.CommandTargetToOleShim.Exec(Guid&amp; guidCommandGroup, UInt32 commandID, UInt32 commandExecOpt, IntPtr variantIn, IntPtr variantOut)</description>
  </entry>
  <entry>
    <time>2020/09/09 15:39:23.694</time>
    <type>Error</type>
    <source>Editor or Editor Extension</source>
    <description>System.ArgumentException: Specified OLE variant is invalid.&#x000D;&#x000A;
        at System.Runtime.InteropServices.Marshal.GetObjectForNativeVariant(IntPtr pSrcNativeVariant)&#x000D;&#x000A;
        at Microsoft.VisualStudio.Html.Interop.CommandTargetToOleShim.TranslateInputArg(Guid&amp; guidCommandGroup, UInt32 commandID, IntPtr variantIn)&#x000D;&#x000A;
        at Microsoft.VisualStudio.Html.Interop.CommandTargetToOleShim.Exec(Guid&amp; guidCommandGroup, UInt32 commandID, UInt32 commandExecOpt, IntPtr variantIn, IntPtr variantOut)&#x000D;&#x000A;
        at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.InnerExec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;
        at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid&amp; pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)&#x000D;&#x000A;
        at Microsoft.VisualStudio.Editor.Implementation.CommandHandlerServiceAdapter.&lt;&gt;c__DisplayClass18_0.&lt;Exec&gt;g__executeNextCommandTarget|1()&#x000D;&#x000A;
        at Microsoft.VisualStudio.UI.Text.Commanding.Implementation.EditorCommandHandlerService.ExecuteStartingAtIndex[T](Func`3 argsFactory, FrugalList`1 buffersAndHandlers, Int32 startIndex, EditorCommandHandlerServiceState state, Action nextCommandHandler)&#x000D;&#x000A;
        at Microsoft.VisualStudio.UI.Text.Commanding.Implementation.EditorCommandHandlerService.&lt;&gt;c__DisplayClass14_0`1.&lt;ExecuteStartingAtIndex&gt;b__2()&#x000D;&#x000A;
        at Microsoft.WebTools.Languages.Shared.Editor.Completion.TypingCommandHandler.ExecuteChainedCommand(EditorCommandArgs args, Action nextCommandHandler)&#x000D;&#x000A;
        at Microsoft.WebTools.Languages.Shared.Editor.Completion.TypingCommandHandler.ExecuteCommand(EscapeKeyCommandArgs args, Action nextCommandHandler, CommandExecutionContext executionContext)&#x000D;&#x000A;
        at Microsoft.VisualStudio.UI.Text.Commanding.Implementation.EditorCommandHandlerService.&lt;&gt;c__DisplayClass14_1`1.&lt;ExecuteStartingAtIndex&gt;b__0()&#x000D;&#x000A;
        at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call, Predicate`1 exceptionFilter)&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;
        at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)</description>
  </entry>

2

Re: Failure in Visual Studio 2019

Can you please check the new version 3.11 and see if it's fixed:

   http://www.viemu.com/blog/2020/12/13/ne … sion-3-11/

Let me know if it isn't fixed and I will look into it asap.

Also, this version removes the user query about reversed ex ranges that you mentioned, hopefully it will be better now that that annoyance is gone.

Regards,

  -- Jon