Skip to content

Remove .NET Framework isms#1139

Merged
RussKie merged 10 commits intomasterfrom
dev/igveliko/fix_485_remove_NET_Framework_isms
Aug 15, 2019
Merged

Remove .NET Framework isms#1139
RussKie merged 10 commits intomasterfrom
dev/igveliko/fix_485_remove_NET_Framework_isms

Conversation

@RussKie
Copy link
Copy Markdown
Contributor

@RussKie RussKie commented Jun 18, 2019

Closes #485

Proposed changes

  • Fixed a number of xml-docs that referenced ".NET Framework" (i.e. Windows-only .NET Framework) in favour of ".NET framework" (i.e. The .NET framework that we all have starting in .NET 5).
  • Remove redundant test plumbing
  • Deprecate Switch.System.Windows.Forms.DoNotSupportSelectAllShortcutInMultilineTextBox
  • Deprecate Switch.System.Windows.Forms.DoNotLoadLatestRichEditControl and remove RichEdit references prior to version 4.1
  • Deprecate Switch.System.Windows.Forms.UseLegacyImages
  • Deprecate Switch.System.Windows.Forms.UseLegacyContextMenuStripSourceControlValue
  • Deprecate Switch.System.Windows.Forms.DomainUpDown.UseLegacyScrolling
  • Deprecate Switch.System.Windows.Forms.AllowUpdateChildControlIndexForTabControls
  • Deprecate Switch.System.Windows.Forms.DontSupportReentrantFilterMessage
  • Deprecate Switch.System.Windows.Forms.EnableVisualStyleValidation
  • Remove LocalAppContext and LocalAppContextSwitches as obsolete and redundant.

Customer Impact

  • Customer who may have relied on these quirks may need to update their apps porting from .NET Fx to .NET Core

Regression?

  • No

Risk

  • Likely low

@RussKie RussKie requested review from M-Lipin and dreddy-work June 18, 2019 05:10
@RussKie RussKie changed the title Remove .NET Framework isms WIP: Remove .NET Framework isms Jun 18, 2019
@danmoseley
Copy link
Copy Markdown
Member

@RussKie I think you can merge this

@dreddy-work
Copy link
Copy Markdown
Member

dreddy-work commented Jul 9, 2019

Are we not removing the word "framework" and just keep .NET? Also, there was a bigger PR #1267 that needs to be merged as well.

@RussKie RussKie force-pushed the dev/igveliko/fix_485_remove_NET_Framework_isms branch from bc0003f to 182f9e1 Compare July 26, 2019 12:21
@RussKie
Copy link
Copy Markdown
Contributor Author

RussKie commented Jul 26, 2019

What should we do with LocalAppContextSwitches - there are few "legacy" switches

internal const string DontSupportReentrantFilterMessageSwitchName = @"Switch.System.Windows.Forms.DontSupportReentrantFilterMessage";
internal const string DoNotSupportSelectAllShortcutInMultilineTextBoxSwitchName = @"Switch.System.Windows.Forms.DoNotSupportSelectAllShortcutInMultilineTextBox";
internal const string DoNotLoadLatestRichEditControlSwitchName = @"Switch.System.Windows.Forms.DoNotLoadLatestRichEditControl";
internal const string UseLegacyContextMenuStripSourceControlValueSwitchName = @"Switch.System.Windows.Forms.UseLegacyContextMenuStripSourceControlValue";
internal const string DomainUpDownUseLegacyScrollingSwitchName = @"Switch.System.Windows.Forms.DomainUpDown.UseLegacyScrolling";
internal const string AllowUpdateChildControlIndexForTabControlsSwitchName = @"Switch.System.Windows.Forms.AllowUpdateChildControlIndexForTabControls";
internal const string UseLegacyImagesSwitchName = @"Switch.System.Windows.Forms.UseLegacyImages";
internal const string EnableVisualStyleValidationSwitchName = @"Switch.System.Windows.Forms.EnableVisualStyleValidation";

@codecov

This comment has been minimized.

@RussKie RussKie force-pushed the dev/igveliko/fix_485_remove_NET_Framework_isms branch from 182f9e1 to b1a8111 Compare July 26, 2019 13:27
@RussKie
Copy link
Copy Markdown
Contributor Author

RussKie commented Jul 29, 2019

@danmosemsft @dreddy-work @merriemcgaw any thoughts? ^^^

@merriemcgaw
Copy link
Copy Markdown
Member

These are quirks so that customers could disable features/fixes done in Framework updates. Our plan was to turn everything on for Core because customers that are porting to Core have to test all of this anyway. If there is no reference to them in code we can remove them. If there is, we should consider whether to remove the reference and the quirk both. Each one is different.

@RussKie RussKie force-pushed the dev/igveliko/fix_485_remove_NET_Framework_isms branch from b1a8111 to 49d6c7a Compare August 1, 2019 10:57
@RussKie RussKie changed the title WIP: Remove .NET Framework isms Remove .NET Framework isms Aug 1, 2019
@RussKie RussKie marked this pull request as ready for review August 1, 2019 12:25
@RussKie RussKie requested a review from a team as a code owner August 1, 2019 12:25
@RussKie
Copy link
Copy Markdown
Contributor Author

RussKie commented Aug 1, 2019

Ready for review.

I have removed a bunch of legacy quirks, please have a look

@ghost ghost added this to the 3.0.0-Preview9 milestone Aug 1, 2019
@RussKie RussKie force-pushed the dev/igveliko/fix_485_remove_NET_Framework_isms branch from e386fb8 to d03785d Compare August 1, 2019 12:49
Copy link
Copy Markdown
Contributor

@Tanya-Solyanik Tanya-Solyanik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@RussKie RussKie added the 📖 documentation: breaking please open a breaking change issue https://github.com/dotnet/docs/issues/new?assignees=gewarren label Aug 2, 2019
@RussKie RussKie force-pushed the dev/igveliko/fix_485_remove_NET_Framework_isms branch 2 times, most recently from 3fad577 to 83f8feb Compare August 2, 2019 19:40
@RussKie RussKie force-pushed the dev/igveliko/fix_485_remove_NET_Framework_isms branch from 0bfb6e1 to f5745ff Compare August 12, 2019 14:04
@RussKie RussKie added 🚫 * NO-MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) and removed 🚫 * NO-MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) tell-mode labels Aug 13, 2019
@RussKie RussKie assigned zsd4yr and unassigned RussKie and M-Lipin Aug 15, 2019
@RussKie RussKie added ask-mode and removed 📖 documentation: breaking please open a breaking change issue https://github.com/dotnet/docs/issues/new?assignees=gewarren waiting-for-testing The PR is awaiting manual testing by the primary team; no action is yet required from the author(s) labels Aug 15, 2019
@zsd4yr
Copy link
Copy Markdown
Contributor

zsd4yr commented Aug 15, 2019

approved by Steve.

@RussKie please cleanup your last commit message and merge at your leisure.

@RussKie
Copy link
Copy Markdown
Contributor Author

RussKie commented Aug 15, 2019

Thank you.

@RussKie RussKie merged commit d989476 into master Aug 15, 2019
@RussKie RussKie deleted the dev/igveliko/fix_485_remove_NET_Framework_isms branch August 15, 2019 20:00
@RussKie RussKie added the 📖 documentation: breaking please open a breaking change issue https://github.com/dotnet/docs/issues/new?assignees=gewarren label Aug 15, 2019
RussKie added a commit to RussKie/winforms that referenced this pull request Sep 3, 2019
The newer RichEdit controls (v4.1+) in specific cases had troubles
detecting "friendly named" hyperlinks as the `Text` property was
reportig less characters than the rage of the actual hyperlink.

Fixes dotnet#1631
Relates to dotnet#1139
@ghost ghost locked as resolved and limited conversation to collaborators Feb 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

📖 documentation: breaking please open a breaking change issue https://github.com/dotnet/docs/issues/new?assignees=gewarren

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove .NET Framework isms

7 participants