Bug Report T995471
Visible to All Users

Refactoring - 'Sync Namespace with Folder Structure' incorrectly determines the default namespace for a project

created 4 years ago (modified 4 years ago)

Hi,

I have a web project that has a different assembly name to default namespace under the project settings and when I create a class, then move, and then use "sync namespace with folder structure" it is using the wrong namespace and seems to be based off the assembly name?

I have provided a project and a video to demonstrate the problem.

Comments (1)
DevExpress Support Team 4 years ago

    Thank you for the video file and the project.
    I have reproduced the problem on my side. We will try to fix it as soon as possible.
    Once we fix it, we will notify you in the current ticket.

    Answers approved by DevExpress Support

    created 4 years ago

    We have addressed the issue described in this ticket and will include a fix in our next maintenance update. Should you need to apply our fix prior to official release, you can request a hotfix here.

    Note: Hotfixes may be unavailable for betas/updates set for release within a week.

      Show previous comments (2)
      DevExpress Support Team 4 years ago

        Hi,

        I see that you already removed the video and marked the ticket as public. Thank you for your cooperation.

          I've had a chance to do a sync namespace using this build and I get this problem if I rename and then try to quit visual studio. I've had this before in the past with coderush. It does correctly do the namespace though but I have to quit visual studio to get it working correctly again.

          Clipboard-File-1.png

          DevExpress Support Team 4 years ago

            Hi,

            Thank you for informing us of your results and providing the screenshot.

            This issue has a different nature than the initial one, so I created a separate ticket for it on your behalf: T1004463: Refactoring - Applying 'Sync Namespace with Folder Structure' produces a dialog about blocking user input. Let's continue our discussion there.

            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.