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 62.58708%. Comparing base (1d61434) to head (6f9ae8f).
Report is 52 commits behind head on main.

Additional details and impacted files

@@                 Coverage Diff                 @@
##                main      #12996         +/-   ##
===================================================
+ Coverage   62.19645%   62.58708%   +0.39063%     
===================================================
  Files           1556        1560          +4     
  Lines         159366      159763        +397     
  Branches       14854       14915         +61     
===================================================
+ Hits           99120       99991        +871     
+ Misses         59495       58996        -499     
- Partials         751         776         +25     

Flag	Coverage Δ
Debug	62.58708% <ø> (+0.39063%)	⬆️
integration	11.32797% <ø> (+0.02738%)	⬆️
production	40.77070% <ø> (+0.43419%)	⬆️
test	95.69342% <ø> (+0.02618%)	⬆️
unit	38.15082% <ø> (+0.45840%)	⬆️

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

[Tanya-Solyanik]

@ricardobossan - if System.Runtime.CompilerServices.Unsafe is not available, it's ok to keep targeting 481. I'm curious, what version of compiler services is 481 using?

[ricardobossan]

@ricardobossan - if System.Runtime.CompilerServices.Unsafe is not available, it's ok to keep targeting 481. I'm curious, what version of compiler services is 481 using?

Looks like it's pulling in version 6.1.0-preview.1.24511.1.

From eng/Versions.props:

<SystemRuntimeCompilerServicesUnsafePackageVersion>6.1.0-preview.1.24511.1</SystemRuntimeCompilerServicesUnsafePackageVersion>

And confirmed in DemoConsole's project.assets.json, line 3091:

"System.Runtime.CompilerServices.Unsafe": "6.1.0-preview.1.24511.1"

[Tanya-Solyanik]

build failure is a dupe of #13291

[LeafShi1]

LGTM with a few comment

[Tanya-Solyanik]

@LeafShi1 @ricardobossan - I had experimented with the solution explorer view a little and pushed by feedback into this branch as a commit, please review it and if it looks ok, merge this PR. Test team can test it after it's merged.

[Tanya-Solyanik]

@ricardobossan - please move these exclusions to the next PR