chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
I am getting the error below when I load any solution. It appears in the Output window under the Typemock category in the drop down. I think it is because I disabled the "Typemock Auto-Runner" add-in via the Extension Manager.

IntelliRunner has encountered an unexpected error.
Castle.MicroKernel.ComponentNotFoundException: No component for supporting the service Typemock.AutoRunner.Core.Coverage.CoverageLoading.DAL was found
   at Castle.MicroKernel.DefaultKernel.Resolve(Type service)
   at Castle.Windsor.WindsorContainer.Resolve[T]()
   at Typemock.AutoRunner.Addin.Dte.DALService.OnBeforeSolutionClosed()
   at System.Action.Invoke()
   at Typemock.VSCommon.SolutionEventsListener.Microsoft.VisualStudio.Shell.Interop.IVsSolutionEvents.OnBeforeCloseSolution(Object pUnkReserved)
IntelliRunner has encountered an unexpected error.
Castle.MicroKernel.Handlers.HandlerException: Can't create component 'Typemock.AutoRun.Adorners.ViewModel.MethodsSummaryWindowViewModel' as it has dependencies to be satisfied. 
Typemock.AutoRun.Adorners.ViewModel.MethodsSummaryWindowViewModel is waiting for the following dependencies: 

Services: 
- Typemock.Common.Core.Runner.IScenarioRunner which was not registered. 
- Typemock.Common.Core.Pause.IPauseState which was not registered. 
- Typemock.AutoRunner.Core.Failures.ITestsState which was registered but is also waiting for dependencies. 

   at Castle.MicroKernel.Handlers.DefaultHandler.AssertNotWaitingForDependency()
   at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired)
   at Castle.MicroKernel.Handlers.AbstractHandler.Resolve(CreationContext context, Boolean instanceRequired)
   at Castle.MicroKernel.Handlers.AbstractHandler.Resolve(CreationContext context)
   at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments)
   at Castle.MicroKernel.DefaultKernel.Resolve(Type service)
   at Castle.Windsor.WindsorContainer.Resolve[T]()
   at Typemock.AutoRun.Adorners.MethodSummaryAdornmentFactory.ShouldRefreshAdorner()
   at Typemock.AutoRun.Adorners.MethodSummaryAdornmentFactory.RefreshAdornerIfNeeded()
   at Typemock.AutoRun.Adorners.MethodSummaryAdornmentFactory.TextViewCreated(IWpfTextView textView)
IntelliRunner has encountered an unexpected error.
Castle.MicroKernel.Handlers.HandlerException: Can't create component 'Typemock.AutoRun.Adorners.ViewModel.MethodContextViewModelRepository' as it has dependencies to be satisfied. 
Typemock.AutoRun.Adorners.ViewModel.MethodContextViewModelRepository is waiting for the following dependencies: 

Services: 
- Typemock.AutoRunner.Core.Coverage.CoverageLoading.TestsRepository which was not registered. 
- Typemock.Common.Core.IFailuresState which was registered but is also waiting for dependencies. 

Typemock.AutoRunner.Core.FailuresState is waiting for the following dependencies: 

Services: 
- Typemock.AutoRunner.Core.Coverage.CoverageLoading.TestsRepository which was not registered. 
- Typemock.Common.Core.Runner.IScenarioRunner which was not registered. 
- Typemock.AutoRunner.Core.Failures.FailuresMatcher which was registered but is also waiting for dependencies. 

Typemock.AutoRunner.Core.Failures.FailuresMatcher is waiting for the following dependencies: 

Services: 
- Typemock.AutoRunner.Core.ChangedMethodsRepsitory which was registered but is also waiting for dependencies. 

Typemock.AutoRunner.Core.ChangedMethodsRepsitory is waiting for the following dependencies: 

Services: 
- Typemock.AutoRunner.Core.Coverage.CoverageLoading.MethodsCoverage which was not registered. 
- Typemock.Common.Core.Runner.IScenarioRunner which was not registered. 

   at Castle.MicroKernel.Handlers.DefaultHandler.AssertNotWaitingForDependency()
   at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired)
   at Castle.MicroKernel.Handlers.AbstractHandler.Resolve(CreationContext context, Boolean instanceRequired)
   at Castle.MicroKernel.Handlers.AbstractHandler.Resolve(CreationContext context)
   at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments)
   at Castle.MicroKernel.DefaultKernel.Resolve(Type service)
   at Castle.Windsor.WindsorContainer.Resolve[T]()
   at Typemock.AutoRun.Adorners.MethodContextAdornmentFactory.TextViewCreated(IWpfTextView textView)
asked by allon.guralnek (10.6k points)

2 Answers

0 votes
I found out this error occurred on instances of Visual Studio that haven't been restarted since the Test Runner was disabled on a different instance. On an instance that has been restarted, this error does not occur. So this is a rather insignificant edge case. Perhaps the only thing that needs to be done is to suppress that error when such a case is detected.
answered by allon.guralnek (10.6k points)
0 votes
Hi Allon,

Thank you for informing us about this bug, we will look into it.
answered by alex (18k points)
...