Bug Report T722534
Visible to All Users

Naming Assistant – The Naming Assistant works incorrectly in Visual Studio 2019 Preview

created 6 years ago (modified 6 years ago)

Equals behavior since version 18.2.8

When I am using VS 2019 . (not seeing in VS 2017)

When I enter something like this:
checkBox1.Checked
Then a Space
When I type the Equals Sign it inserts "@checked" to this:

checkBox1.Checked @checked=

or if I type: "Form1.Owner =" I get "Form1.Owner owner="

etc.

Thank You,
Scott Snyder

P.S. Code Places is already a valuable asset and I see its potential to grow.

Comments (1)
PW PW
Przemyslaw Wlodarczak (DevExpress) 6 years ago

    Scott,

    I reproduced this incorrect behavior and passed this ticket to our developers for further investigation. You will be notified when we fix this issue.
    As a workaround for now, I suggest you disable the Naming Assistant feature when working with Visual Studio 2019. To do so, open the "Extensions->CodeRush->Options" window, navigate to the "Editor->C#->Naming Assistant" category and uncheck the "Enable Naming Assistant" checkbox.

    Answers approved by DevExpress Support

    created 6 years ago (modified 6 years ago)

    We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

    Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

      Show previous comments (1)
      DevExpress Support Team 6 years ago

        Hi Scott,

        I've created a separate ticket on your behalf (T726804: Color picker should remember "Sort by" settings.). It has been placed in our processing queue and will be answered shortly.

          It doesn't work in 18.2.9 VB even with disabled Naming Assistant.

          After entering " (double quote) CR inserts "String":

          Visual Basic
          dim ss as String=String"
          DevExpress Support Team 6 years ago

            Hi Kiryl,

            Thank you for pointing out the problem.
            We have already fixed a similar issue in the context of the IntelliRush does now allow inserting a lambda expression after a user types “=>” in Visual Studio 2019 ticket.
            Please install the build from the link below and let me know your results.

            DevExpress.CodeRush-18.2.9.19105.exe
            DevExpress.CodeRush-18.2.9.19105.vsix

            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.