Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Application.EnableVisualStyles in single file publishing mode (servicing) #4177

Merged
merged 1 commit into from
Nov 10, 2020

Conversation

RussKie
Copy link
Member

@RussKie RussKie commented Oct 30, 2020

Fixes #4145
(cherry picked from commit 082cbf2)

Customer Impact

  • Application.EnableVisualStyles gives Windows a manifest that enables the v6 common controls. We normally pull this manifest from a native resource in System.Windows.Forms.dll. In single file mode there is no "dll" to load from so this feature was not working as intended.
    In the case where we can't get a Win32 HMODULE we now fall back to pulling the manifest from a managed resource and dumping it to the temp folder.
  • Make ACTCTXW blittable.

Regression?

  • No, but makes the feature 'Self-contained + Produce Single File' virtually unsuitable for Windows Forms apps.

Risk

  • Minimal
Microsoft Reviewers: Open in CodeFlow

…tnet#4149)

* Fix Application.EnableVisualStyles in single file publishing mode

Application.EnableVisualStyles gives Windows a manifest that enables the v6 common controls. We normally pull this manifest from a native resource in System.Windows.Forms.dll. In single file mode there is no "dll" to load from so this feature was not working as intended.

In the case where we can't get a Win32 HMODULE we now fall back to pulling the manifest from a managed resource and dumping it to the temp folder.

Make ACTCTXW blittable.

(cherry picked from commit 082cbf2)
@RussKie RussKie added the servicing-consider .NET Shiproom label indicating a PR seeks to enter into a branch under Tell-Mode criteria label Oct 30, 2020
@RussKie RussKie requested a review from JeremyKuhne October 30, 2020 01:40
@RussKie RussKie requested a review from a team as a code owner October 30, 2020 01:40
@ghost ghost assigned RussKie Oct 30, 2020
@RussKie RussKie added this to the 5.0.1 milestone Oct 30, 2020
@codecov
Copy link

codecov bot commented Oct 30, 2020

Codecov Report

Merging #4177 into release/5.0 will increase coverage by 30.04274%.
The diff coverage is 100.00000%.

@@                  Coverage Diff                   @@
##           release/5.0       #4177          +/-   ##
======================================================
+ Coverage     68.03138%   98.07412%   +30.04273%     
======================================================
  Files             1416         492         -924     
  Lines           509681      258687      -250994     
  Branches         41474        4476       -36998     
======================================================
- Hits            346743      253705       -93038     
+ Misses          156710        4225      -152485     
+ Partials          6228         757        -5471     
Flag Coverage Δ
#Debug 98.07412% <100.00000%> (+30.04273%) ⬆️
#production ?
#test 98.07412% <100.00000%> (+0.00776%) ⬆️

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

@leecow leecow added servicing-approved .NET Shiproom approved the PR for merge and removed servicing-consider .NET Shiproom label indicating a PR seeks to enter into a branch under Tell-Mode criteria labels Nov 3, 2020
@RussKie RussKie merged commit 5ad6863 into dotnet:release/5.0 Nov 10, 2020
@RussKie RussKie deleted the fix_4145 branch November 10, 2020 00:39
@ghost ghost locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
servicing-approved .NET Shiproom approved the PR for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants