Exception on launching CodedUITest Builder

5 posts, 0 answers
  1. Gajan
    Gajan avatar
    13 posts
    Member since:
    Mar 2012

    Posted 07 Aug 2013 Link to this post

    Hi,

    I followed the instructions on the Telerik web page 'http://www.telerik.com/help/wpf/coded-ui-support.html' and copied the assembly Telerik.VisualStudio.TestTools.UITest.Extension.ExtensionsCore into the folder C:\Program Files (x86)\Common Files\Microsoft Shared\VSTT\11.0\UITestExtensionPackages. Then installed the assembley into GAC.

    I am using VS 2012. When I try to use Coded UI Test Builder, it terminates with the following exception.

    Application: CodedUITestBuilder.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: Microsoft.VisualStudio.TestTools.UITest.Extension.InvalidUITestExtensionPackageException
    Stack:
       at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestExtensionPackageManager.LoadAssemblies(System.String[])
       at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestExtensionPackageManager..ctor()
       at Microsoft.VisualStudio.TestTools.UITest.Framework.UITestService.Initialize()
       at Microsoft.VisualStudio.TestTools.CodedUITest.Controls.CodedUITestBuilder.UITestBuilder.InitializeExtensions()
       at Microsoft.VisualStudio.TestTools.CodedUITest.Controls.CodedUITestBuilder.UITestBuilder.WindowActivated(System.Object, System.EventArgs)
       at System.Windows.Window.OnActivated(System.EventArgs)
       at System.Windows.Window.HandleActivate(Boolean)
       at System.Windows.Window.WmActivate(IntPtr)
       at System.Windows.Window.WindowFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.ShowWindow(System.Runtime.InteropServices.HandleRef, Int32)
       at System.Windows.Window.ShowHelper(System.Object)
       at System.Windows.Window.Show()
       at System.Windows.Application.<RunInternal>b__f(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
       at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
       at System.Windows.Threading.Dispatcher.Run()
       at System.Windows.Application.RunDispatcher(System.Object)
       at System.Windows.Application.RunInternal(System.Windows.Window)
       at System.Windows.Application.Run(System.Windows.Window)
       at Microsoft.VisualStudio.TestTools.UITest.CodedUITest.CodedUITestBuilder.Program.Main(System.String[])

    If I remove the assembly from the folder, Coded UI Test Builder lauches without error but it does not record actions on Telerik controls as expected.

    Is there anything I can do to avoid this error?

    Thank you,

    Gajan
     

  2. Maya
    Admin
    Maya avatar
    4062 posts

    Posted 07 Aug 2013 Link to this post

    Hello Gajan,

    Will it be possible to clarify which version you are working with ? Do you use our current official release - Q2 SP 2013 ?  

    Regards,
    Maya
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  3. UI for WPF is Visual Studio 2017 Ready
  4. Gajan
    Gajan avatar
    13 posts
    Member since:
    Mar 2012

    Posted 07 Aug 2013 Link to this post

    Yes, I am using Q2 2013 (2013.2.617.45).

    Thank you for getting back quickly.

    Gajan
  5. Maya
    Admin
    Maya avatar
    4062 posts

    Posted 07 Aug 2013 Link to this post

    Hi Gajan,

    We used to have issues with Visual Studio 2012 with our Q2 2013, but they were fixed with our SP. Will it be possible to test your application with it ?  

    Regards,
    Maya
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  6. Gajan
    Gajan avatar
    13 posts
    Member since:
    Mar 2012

    Posted 08 Aug 2013 Link to this post

    Hi,

    After updating with the hot fix (version 2013.2.805.45) I am not getting the exception any more.

    Thanks,

    Gajan
     
Back to Top
UI for WPF is Visual Studio 2017 Ready