Sync namespaces doesn't work in .NET MAUI project

_This issue has been moved from [a ticket on Developer Community](https://developercommunity.visualstudio.com/t/Sync-namespaces-doesnt-work-in-NET-MAU/10311359)._

---
\[severity:It bothers me. A fix would be nice\]
I am trying to change project name and with it change namespace name.
When I changed the project name, some kind of synchronization process was visible in Visual Studio but the namespaces did not chage.
When I clicked Sync Namespaces first time, a process of changing namespaces was running for a few seconds.
When I clicked Sync Namespaces after that, I get dialog “No namespaces needed updating”.
In either case, the namespaces haven’t been changed and I haven’t found any way how to change namespaces in a .NET MAUI Project.
Note: I tried removing all target platforms except Android and it still doesn’t work.


I am attaching sample project as .zip archive
Edit: I discovered that `<RootNamespace>TheProjectNamespace</RootNamespace>` in .csproj has to be manually changed. After that, sync namespaces works.

---
### Original Comments

#### Feedback Bot on 3/15/2023, 08:25 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

#### Feedback Bot on 4/21/2023, 07:37 AM:

Thank you for sharing your feedback! Our teams prioritize action on product issues with broad customer impact. See details at: https://docs.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2019#faq. In case you need answers to common questions or need assisted support, be sure to use https://visualstudio.microsoft.com/vs/support/. We’ll keep you posted on any updates to this feedback.

#### Feedback Bot on 7/2/2023, 07:54 PM:

I detected that this issue hasn’t received a lot of activity, votes, or comments in the past 90 days. Based on this, the issues severity and affected area, it’s my experience that this issue is unlikely to get fixed. To improve the situation, consider following best practices for quality problem reports, and giving us more details on how this issue is impacting you.

#### Anonymized GDPR on 5/23/2024, 07:47 PM:

Thanks for your sharing the detail steps, I can reproduce this issue through your shared steps and this issue has been escalated for further investigation, if there is any process, I will inform you immediately.

#### Feedback Bot on 6/24/2025, 04:11 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

#### Feedback Bot on 7/4/2025, 08:19 AM:

This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.