v-olzhan

@merriemcgaw This is not a regression issue. Earlier .Net framework versions all have this issue when setting SortMode as Programmatic.

@dkazennov Do we need to reactivate this issue?

@merriemcgaw we looked at this issue using provided sample application, and repro it in both .Net Framework and .Net Core applications. Didn't find any workaround or feedback ticket related it....

@Tanya-Solyanik this is a tracking issue in runfo, why I don't see this test failure in PR https://github.com/dotnet/winforms/pull/7421's Tests Summary in here: https://dev.azure.com/dnceng/public/_build/results?buildId=1886820&view=ms.vss-test-web.build-test-results-tab? And I checked in here: https://dev.azure.com/dnceng/public/_test/analytics?definitionId=267&contextType=build by...

@merriemcgaw can repro this issue in the latest .Net 5 build.

@Tanya-Solyanik I cannot repro this issue in Winforms .net framework application with 3rd party controls from DevExpress, build and run app successfully in VS 2022. @wangrd Could you please let...

> @Olina-Zhang do you know if this issue is already filed in the designer project? Yes, we have a designer issue in private repo: https://github.com/microsoft/winforms-designer/issues/2640 - closed, there has more...

@Tanya-Solyanik I cannot create a sample followed that document provided successfully. And test tabControls in Inspect by Navigation, it has same results in .Net 8.0 and .Net 6.0, TabItems under...

Thanks @LeafShi1. Verified it is regressed from .Net 6.0, cannot repro in .Net Core 3.1 and .Net 5.0. .Net 6.0 behavior:  .Net 5.0: 

> @Olina-Zhang: Can you check that? Thanks! Out-Of-Proc Designer works fine, we can change the Byte[] type property successfully.