Steve Cadwallader

My comment was intended only to say that we do not intentionally (explicitly) re-order modifiers, that's not to say there can't be an unintentional effect or a combination of settings/extensions...

Thanks for the information. While it wouldn't explain the original report, since then there is a new issue introduced with the SDK releases at the launch of VS2022 that has...

Thanks for reporting the issue. I have been able to reproduce it. This looks to be fitting into a series of issues related to a breaking change in an underlying...

I've confirmed this issue happens in both VS2019 and VS2022. I've sent an email to Microsoft to try and get some help digging down into the API.

While looking in that area, there is also room for improvement in that `CodeElementHelper` doesn't recognize some syntax patterns (e.g. method arrow definitions) as well as `GetTextToFirstMatch` which was recently...

Hi @WeihanLi , the latest update is I'm waiting for feedback from Microsoft on this issue if you would like to look/comment over there: https://github.com/dotnet/roslyn/issues/58315

Thank you for providing the additional situation. It looks like it may be awhile before the SDK is resolved so I am considering disabling the explicit access modifier logic for...

Thanks for opening the PR, I appreciate it. The code changes look pretty straight forward and good to me. May I ask what kind of testing you did with these...

@anshulahuja98 This feature request is still dependent on Roslyn APIs which we have not implemented.

Thanks for reporting the issue, I am unable to reproduce it. A couple things to check: 1. Have you double checked that your settings are still set so that automatic...