Daily Usage Issues

NCrunch 3.28 fails to initialize after VS 2019 update to 16.3.10

Started by graemejob on 1,882 views

NCrunch was working fine for me before I updated VS 2019, but now it just shows the "You can enable NCrunch by selecting 'Enable' ..." message, and Enable is greyed out.

NCrunch Diagnostic Output:
[11:05:56.4939-UI-1] Initialising Package Integration
[11:05:56.4989-UI-1] GetServiceLocal for Microsoft.VisualStudio.Shell.Interop.SVsShell
[11:05:56.4989-UI-1] Package initialisation is complete. Running under VS2019
[11:05:56.4999-UI-1] NCrunch Package Initialisation time is 00:00:06.865 started at 11:05:49.6337
[11:05:56.5038-UI-1] GetServiceLocal for Microsoft.VisualStudio.Shell.Interop.SDTE
[11:05:56.5058-UI-1] Initialising automation integration for NCrunch
[11:05:56.5288-UI-1] Registering menu options
[11:05:56.5298-UI-1] GetServiceLocal for System.ComponentModel.Design.IMenuCommandService
[11:05:56.5318-UI-1] getWindow for nCrunch.VSIntegration2019.ComponentConfigToolWindowPane
[11:05:56.5776-UI-1] getWindow for nCrunch.VSIntegration2019.GridManagementToolWindowPane
[11:05:56.6235-UI-1] getWindow for nCrunch.VSIntegration2019.MetricsToolWindowPane
[11:05:56.6415-UI-1] getWindow for nCrunch.VSIntegration2019.ProcessingQueueToolWindowPane
[11:05:56.6644-UI-1] getWindow for nCrunch.VSIntegration2019.TestsToolWindowPane
[11:05:56.7402-UI-1] getWindow for nCrunch.VSIntegration2019.StatusIndicatorToolWindowPane
[11:05:56.7641-UI-1] Hooking up WPF integration
[11:05:56.7681-UI-1] ERROR (Internal): System.ArgumentOutOfRangeException: Specified index is out of range or child at index is null. Do not call this method if VisualChildrenCount returns zero, indicating that the Visual has no children.
Parameter name: index
Actual value was 1.
at System.Windows.Controls.Decorator.GetVisualChild(Int32 index)
at System.Windows.Media.Visual.InternalGet2DOr3DVisualChild(Int32 index)
at System.Windows.Media.VisualTreeHelper.GetChild(DependencyObject reference, Int32 childIndex)
at nCrunch.WpfUI.VsWpfUIIntegrator.EnsureWpfIntegrationIsHookedUp()
at nCrunch.VSAddIn.PackageIntegrator.OnStartupCompleted()
at nCrunch.VSAddIn.AutomationIntegrator.Initialise(DTE2 vsDTE)

[11:05:56.7681-UI-1] Total startup time including initialisation took: 0:00:07.1344262
[11:05:56.7681-UI-1] Switching to UI thread took: 00:00:06.4497798
[11:05:56.7681-UI-1] Cached Initialisation message at 2019-11-28T11:05:56, message: GetServiceLocal for Microsoft.VisualStudio.Shell.Interop.IVsSolutionBuildManager

I have tried:
* deleting all obj, bin folders
* removing ncrunch temp, cache, project files
* resetting VS settings
* uninstalling and reinstalling ncrunch

Would it be possible to get a patch for this, as we're currently tied to a license with a max version of V3.28.

Thanks!

Edited

Hi, thanks for sharing this problem.

This issue is caused by a breaking change introduced by Microsoft in an update to VS2019. We resolved it in NCrunch v3.31, with builds that were made available as soon as we became aware of the problem.

Please note that we do not release patches for old versions of the software as to do this would involve warranting future compatibility with all versions of Visual Studio (something we can't do), and it would completely break the licensing and release model.

You have the option of either upgrading your license or downgrading your version of VS2019 to a build released prior to the breaking change.
Thanks for your dizzyingly quick response!
Totally understand. Hopefully can get something sorted soon.

Post a reply

Log in to reply.