Skip to content

FileLocksmith: Fix context menu items are not localized - #49606

Open
Umoxfo wants to merge 1 commit into
microsoft:mainfrom
Umoxfo:patch-1
Open

FileLocksmith: Fix context menu items are not localized#49606
Umoxfo wants to merge 1 commit into
microsoft:mainfrom
Umoxfo:patch-1

Conversation

@Umoxfo

@Umoxfo Umoxfo commented Aug 1, 2026

Copy link
Copy Markdown

Summary of the Pull Request

Fixing the issue where Windows 11 context menu items are not localized.

PR Checklist

  • Communication: I've discussed this with core contributors already. If the work hasn't been agreed, this work might be rejected
  • Tests: Added/updated and all pass
  • Localization: All end-user-facing strings can be localized
  • Dev docs: No documentation changes are required for project configuration fixes
  • New binaries: No new binaries are added
  • Documentation updated: No user documentation changes are required

Detailed Description of the Pull Request / Additional comments

Reorganize resource items for the FileLocksmithContextMenu project

  • Mark resource.base.h as a non-compiled None
  • Add Generated Files/resource.h as a ClInclude
  • Mark FileLocksmithContextMenu.base.rcas a non-compiled None
  • Add Generated Files/FileLocksmithContextMenu.rc as a ResourceCompile

Update the .vcxproj.filters accordingly to reflect the new locations and filters for header and resource files.

before Before after After

Validation Steps Performed

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the FileLocksmith Windows 11 context menu project’s resource-file wiring so localized strings generated from Resources.resx are actually compiled into the DLL (instead of compiling the non-localized “base” resources), addressing the issue where the context menu label remained English.

Changes:

  • Switch the project to compile the generated RC (Generated Files/FileLocksmithContextMenu.rc) rather than the base RC (FileLocksmithContextMenu.base.rc).
  • Treat resource.base.h and FileLocksmithContextMenu.base.rc as non-compiled inputs (None) while adding the generated resource.h as a header include for the project.
  • Update .vcxproj.filters to reflect the new generated vs. base resource file organization in Solution Explorer.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/modules/FileLocksmith/FileLocksmithContextMenu/FileLocksmithContextMenu.vcxproj.filters Re-categorizes base vs. generated resource/header files to match the new build inputs/outputs.
src/modules/FileLocksmith/FileLocksmithContextMenu/FileLocksmithContextMenu.vcxproj Compiles the generated .rc (from resx conversion) and demotes base .rc/.h files to non-compiled inputs so localization takes effect.

@Umoxfo
Umoxfo marked this pull request as ready for review August 1, 2026 19:21
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Reorganize resource items for the `FileLocksmithContextMenu` project
 - Mark `resource.base.h` as a non-compiled `None`
 - Add `Generated Files/resource.h` as a `ClInclude`
 - Mark `FileLocksmithContextMenu.base.rc`as a non-compiled `None`
 - Add `Generated Files/FileLocksmithContextMenu.rc` as a `ResourceCompile`

Update the `.vcxproj.filters` accordingly to reflect the new locations and filters for header and resource files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bugs On Windows 11 New Context Menu

2 participants