Issue 12830 multi target demo console

[ricardobossan]

Fixes #12830

Proposed changes

• Updated DemoConsole.csproj and DesignSurfaceExt.csproj to support multiple target frameworks ($(NetCurrent)-windows;net481).
• Adjusted TargetFramework property to avoid over-building.
• Enabled SignAssembly and GenerateAssemblyInfo properties in the project files.
• Updated resource and reference handling in DemoConsole.csproj and DesignSurfaceExt.csproj to improve compatibility.
• Fixed Controls.AddRange usage to use the correct syntax in MainForm.MyUserControl.cs.
• Corrected Controls.AddRange call in MainForm.cs to Controls.Add.
• Suppressed IDE0057 warning and reverted to Substring method for compatibility in NameCreationServiceImp.cs.
• Changed StartsWith('_') check by directly accessing the first character in NameCreationServiceImp.cs for compatibility.
• Disabled error CA1824 for projects DemoConsole and DesignSurficeExt, because it would be triggered even though properly configured in those projects, according to the fix provided by the documentation.

Customer Impact

• None

Regression?

• No

Risk

• Minimal

Screenshots

Before

• DemoConsole would not run on net481.

After

Test methodology

• Manual

Test environment(s)

• 10.0.100-alpha.1.25077.2

[ricardobossan]

Drafted because:

• Need to address nullability warnings
• net481 compiles without errors but doesn't launch

[ricardobossan]

@Tanya-Solyanik @LeafShi1 @Epica3055 I was able to get the DemoConsole project to compile for multiple targets ($(NetCurrent)-windows and net481), but it doesn't launch on net481. There's no error message explaining why. It just fails silently. Do you have any idea what might be causing this?

I’m aware of the nullability warnings that I still need to address, but could they be related to this issue?

[Tanya-Solyanik]

Enable all CLR exceptions before starting to debug this project as 4.8.1. I guess immutable collection reference is not discovered.

[Tanya-Solyanik]

@ricardobossan - the reason the NET481 version does not run is that the dll is not strong-name signed, we should delay-sign it. Arcade should have tools for that. Maybe like this <SignAssembly>true</SignAssembly> https://github.com/dotnet/arcade/blob/ecdb2f499cb5f5c99b58fba1a14fdf977c56e1ac/Documentation/ArcadeSdk.md?plain=1#L953
Search arcade docs to see if they recommend any signing test keys to use. We should not use a production key.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.28720%. Comparing base (e00df8a) to head (8e31d0c).
Report is 4 commits behind head on main.

Additional details and impacted files

@@                 Coverage Diff                 @@
##                main      #12996         +/-   ##
===================================================
+ Coverage   61.03240%   61.28720%   +0.25479%     
===================================================
  Files           1539        1541          +2     
  Lines         158039      158281        +242     
  Branches       14721       14743         +22     
===================================================
+ Hits           96455       97006        +551     
+ Misses         60889       60577        -312     
- Partials         695         698          +3     

Flag	Coverage Δ
Debug	61.28720% <ø> (+0.25479%)	⬆️
integration	10.73249% <ø> (-0.00523%)	⬇️
production	39.15640% <ø> (+0.33021%)	⬆️
test	95.67280% <ø> (+0.00238%)	⬆️
unit	36.58217% <ø> (+0.33435%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[LeafShi1]

When using only net481 in the DemoConsole project, TabPage6 does not display properly. When enabling all CLR exceptions before starting to debug this project, I receive the following error

[ricardobossan]

@LeafShi1 I was able to run the project and navigate through the tabs on net481 with all CLR exceptions enabled, as shown in the GIF below:

Here’s how I set up and ran the project:

# From the runtime repo root folder:
gh pr checkout 12996
msbuild /t:Clean .\Winforms.sln
.\Restore.cmd
.\build.cmd
.\start-vs.cmd

Could you share the exact steps you're using to run the project? That might help pinpoint any differences that could explain the discrepancy in our results.

[LeafShi1]

Could you share the exact steps you're using to run the project? That might help pinpoint any differences that could explain the discrepancy in our results.

When using <TargetFrameworks>$(NetCurrent)-windows;net481</TargetFrameworks>, it shows up fine on my end。
I just tried changing the TargetFramework to net481, like this

But it doesn't seem to work, because it causes compilation to fail

So please ignore my comment

[LeafShi1]

When setting up Multi target in a project, we need to make sure it compiles and runs properly in a separate TargetFramework.
@Tanya-Solyanik Is that right?

[LeafShi1]

When the version order in TargetFrameworks is changed to put net481 first, the controls in ToolStripContainer cannot be displayed

<TargetFrameworks>net481;$(NetCurrent)-windows</TargetFrameworks>

[Epica3055]

When I started DemoConsole project, I got this error.

[LeafShi1]

The PR need to rebase main because the tests under src/System.Windows.Forms/tests/IntegrationTests/DesignSurface have been moved to path src\test\integration\DesignSurface.

[ricardobossan]

@LeafShi1 @Epica3055 Thanks for your comments! I investigated both issues in detail, and here are my findings:

On Leaf's Comment:

• The ToolStripContainer controls do not appear in the net481 build, regardless of the order of frameworks in the TargetFrameworks tag.
• On my 2025/02/25 comment, I initially observed that TabPage6 displayed correctly under net481 and provided a video demonstration:
  Issue 12830 multi target demo console #12996 (comment)
• However, I can now confirm that this issue occurs for me as well, as you described.
• I retraced my commits using a backup branch from before the rebase, testing each step, but the issue persists. This suggests that an external factor (outside my changes) might have affected the behavior.
• This needs further investigation.

On Epica's Comment:

• The "Object reference" error started appearing after the rebase I made to accommodate changes in new commits on the main branch but only affects the net481 build.
• Before rebasing, the backup branch did not show this error.
• I confirmed that my code was properly merged, yet this issue emerged post-rebase.
• This also requires further investigation to identify what changed upstream.

---

The net10.0-windows build runs flawlessly. However, in net481, debugging triggers the CLR error that Epica mentioned, and the controls inside ToolStripContainer do not appear.

Furthermore, in net481, whether debugging or not, the issue described in Leaf's comment persists: the ToolStripContainer tab stopped showing its controls. This behavior is unexpected since my current code changes previously worked correctly, as demonstrated in my 2025/02/25 video.

I'll look into these issues further after I'm back from my time OOP due to vacation.