This avoids need for a workaround in VMR builds and reduces friction for stable builds. When building non-win-x64 verticals, we end up having to set the x64 runtime pack and x64 VS redist pack properties (stable and non-stable properties) based on other values in the VMR orchestrator. Instead, use MicrosoftNEtCoreAppRef as the stable version property, and MicrosoftNETCOrePlatforms as the non-stable one.
Related #13388
## Proposed changes
- Unifies `DesignSurfaceExt` and `DemoConsole` namespaces under the
latter.
- Renames class names where appropriate to reflect the shared project
identity, in preparation for relocating all files into the `DemoConsole`
folder in a follow-up PR.
## Customer Impact
- None or succinct description
## Regression?
- No
## Risk
- Minimal
## Test environment(s)
- 10.0.100-preview.3.25201.16
Co-authored-by: Ricardo Bossan (BEYONDSOFT CONSULTING INC) <v-rbossan@microsoft.com>
* There are situations when AccessibilityObject is not available, for example when the corresponding control is not displayed or not parented, thus changing nullability on this property. We were already guarding against accessing objects for "invisible" groups in the parent ListViewAccessibleObject when enumerating children.
We should not attempt to create accessible object for unparented ListView groups, for example when a group is removed from the control.
This fix is based on this call stack:
System.InvalidOperationException: ListView
at System.Windows.Forms.ListViewGroup.ListViewGroupAccessibleObject..ctor(ListViewGroup owningGroup, Boolean owningGroupIsDefault)
at System.Windows.Forms.ListViewGroup.get_AccessibilityObject()
at System.Windows.Forms.ListView.OnGotFocus(EventArgs e)
This is a follow up on #10910 (comment)
Related to #4019
CMake now comes with the VS
Added path to the latest SDK build
Co-authored-by: Jeremy Kuhne <jkuhne@microsoft.com>
---------
Co-authored-by: Jeremy Kuhne <jkuhne@microsoft.com>
* Add Framework folder from multitarget repository to the new multi-target version of DemoConsole
Fixes#13372
## Proposed changes
- Add Framework folder from https://github.com/JeremyKuhne/multitarget
to the new multi-target version of `DemoConsole`.
- Adapts namespaces in order to avoid type collisions with assemblies
from other target frameworks.
## Customer Impact
- Hints on how to add compatibility files to versions of .NET that might
require it (In this case, `net472`, as in the [multitarget
repository](https://github.com/JeremyKuhne/multitarget)).
## Regression?
- No
## Risk
- Minimal
## Test methodology
- Manual
## Test environment(s)
- 10.0.100-preview.3.25201.16
* Add the Framework folder to be excluded when target is not net481
* Adds configuration regarding visibility of the Framewrk folder
* Move Framework folder from DemoConsole to DesignSurfaceExt
* Adjust namespaces
* Fixes residual namespace, removes conditional compilation and fixes comments
* Handle feedbacks
---------
Co-authored-by: Ricardo Bossan (BEYONDSOFT CONSULTING INC) <v-rbossan@microsoft.com>
All of the removed dependencies and properties in this PR aren't necessary. They were needed previously for coherency but that isn't necessary anymore now that winforms flows directly into the VMR.
* Makes the DemoConsole application multitarget
Fixes#12830
- 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](https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1824#fix-violations).
- None
- No
- Minimal
- `DemoConsole` would not run on `net481`.
- Manual
- 10.0.100-preview.3.25125.5
* Moves back from net472 to net481
* Modifies README.md file for DemoConsole and moves it one folder above, while also showing it in VS's Solution Explorer
* Add comment to address #13248
* Unwrap long comment and reindent for better auto formatting
* Removes leftover code from early attempt to fix#13234
* 1 removed references rto Framework folder - it will be added in the next PR
2. set main form name so that it reflects the target framework.
3. show readme.md in the solution explorer.
4. removed a default constructor, it will be generated for us.
5. it's ok to have lines almost 120 chars long
---------
Co-authored-by: Ricardo Bossan (BEYONDSOFT CONSULTING INC) (from Dev Box) <v-rbossan@microsoft.com>
Co-authored-by: Tanya Solyanik <tanyaso@microsoft.com>
* fix#13071 Changing properties with RefreshProperties.All does not requery the property list in the PropertyGrid in .net 9 (worked in .net 8) : revert PR#12431 , use another approach.
* add unit test
Matt Mitchell