BuyLog In
Ticket T382962
Visible to All Users

Coded UI Test Extension FAQ - Removing extensions

created 9 years ago

[DevExpress Support Team: CLONED FROM KA18720: Coded UI Test Extension FAQ]
I have a question that doesn't seem to be addressed in the above post…

Let's say I have a DXperience subscription (allowing me access to the CUIT extension in demo mode) and I want to deregister the demo (since my organization is not wanting to upgrade to the Ultimate subscription for our entire development shop). I would imagine that the following mechanisms would be sufficient to prevent the Coded UI Test Builder from attempting to use the extension:

- Removing the UITestExtensionPackage entries from the registry
- Removing any DevExpress specific entries from the following directories:
"%CommonProgramFiles%\Microsoft Shared\VSTT{Version}\UITestExtensionPackages\.*"
"%CommonProgramFiles**(x86)** %\Microsoft Shared\VSTT{Version}\UITestExtensionPackages\.*"

I would be wrong…

In certain machines, even after ensuring that the CUIT extensions have been deregistered, the CodedUITestBuilder still attempts to use them and ends up adding the CUIT references to our projects.

Do you have any advice as to alternate methods to ensure that the CUIT extension demo is NOT used when recording interactions against DevExpress controls?

Sign in to comment on this post

Answers approved by DevExpress Support

created 9 years ago

Hi Annet,

Thank you for your message.

As far as I understand, you are removing CUIT Extensions manually by deleting related folders on a local disc. Since the process of registering CUIT Extensions is a little complicated and some other operations are required to be done besides copying assemblies to the local disc, we do not recommend removing extensions manually. For this purpose, customers with an appropriate subscription can use a separate installation file that is located on the Download Manager page. For those customers who do not have access to a separate installation file, we will gladly share a direct link to download it on demand. Please clarify what version of DevExpress components you are using, so I can provide you with a link.
I hope to hear from you soon.

    Comments (3)
    ZA ZA
    Zach Annett 9 years ago

      You are partially correct in your understanding of the situation, but hopefully I can provide some clarification.

      Firstly, the mechanisms specified by Microsoft for registering new technology types with Coded UI are to do one of two things:

      - Add registry entries to the following location:
      "HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio{Version}\TeamTest\UITest\ UITestExtensionPackage"

      - Copy dlls to one of the following locations:
      "%CommonProgramFiles%\Microsoft Shared\VSTT{Version}\UITestExtensionPackages\*.* "
      "%CommonProgramFiles(x86) %\Microsoft Shared\VSTT{Version}\UITestExtensionPackages\*.* "

      It appears that the DevExpress Coded UI extensions register themselves via the first mechanism, and we have removed those registry entries on all of our development machines. This seems to work for MOST people in our organization, as they are no longer recording controls through the DevExpress technology type but rather the MSAA technology type.

      The issue is that there a few machines that still attempt to use the Coded UI extension when the CodedUITestBuilder is launched.

      To simplify my question: Are there any other mechanisms in addition to what I have listed that allow your extension to be registered with Visual Studio for use in recording Coded UI tests?

      ZA ZA
      Zach Annett 9 years ago

        I forgot to answer your question in the response above…

        We are currently have a WinForms Subscription license (although it appears my subscription just recently expired).

        Alisher (DevExpress Support) 9 years ago

          Hi Annet,

          Thank you for the clarification.

          In addition to registering assemblies in the system registry, we place our assemblies to the %installation_folder%\Components\Tools\Windows Forms folder and GAC. That is why, we recommend using the installation file in order to remove assemblies from all places to which we copy them. If certain machines still use our CodedUI Extensions when a test is recorded, please download and install our CodedUI Extensions first and then uninstall them. Use the following links to download installation files for CodedUI Extensions of versions 15.2.5 and 14.2.8:
          1. DevExpressCodedUIExtensionsWin-15.2.5.exe
          2. DevExpressCodedUIExtensionsWin-14.2.8.exe

          Keep me posted.

          Sign in to comment on this post

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.