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.

Sign up for GitHub

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

Jump to bottom

LocBaml tool is incompatible with .NET 6 Core #1695

Closed
ipizhenko opened this issue Sep 7, 2023 · 4 comments · Fixed by #1727
Closed

LocBaml tool is incompatible with .NET 6 Core #1695

ipizhenko opened this issue Sep 7, 2023 · 4 comments · Fixed by #1727
Assignees
@adegeo
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-framework/svc Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Label to indicate an item has been imported. wpf/subsvc

Comments

@ipizhenko
Copy link

ipizhenko commented Sep 7, 2023 •
edited by github-actions bot
Loading

The LocBaml tool doesn't compile for .NET Core 6. Compiled as is for .NET Framework 4.7.2 it can't work with applications compiled for .NET Core 6. Please update the tool. Please also describe how to achieve the same result WITHOUT using this tool.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Associated WorkItem - 157252
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Sep 7, 2023
@issues-automation issues-automation bot added dotnet-framework/svc wpf/subsvc Pri1 High priority, do before Pri2 and Pri3 labels Sep 7, 2023
@adegeo adegeo added doc-enhancement Improve the current content [org][type][category] and removed ⌚ Not Triaged Not triaged labels Sep 7, 2023
@adegeo adegeo self-assigned this Sep 7, 2023
@adegeo
Copy link
Contributor

adegeo commented Sep 7, 2023 •
edited
Loading

Correct. I saw that you posted in the dotnet/wpf repo, which is where the owner of that tool would be, I assume. I'll add investigating updating this article for .NET 6/7/8 this to the Oct sprint. Personally I don't really know anything about it so there's going to be some learning on my end. If you figure anything out, please keep me informed in this issue.

@adegeo adegeo added the 🗺️ reQUEST Trigger label to import an issue into Quest label Sep 7, 2023
@github-actions github-actions bot added 📌 seQUESTered Label to indicate an item has been imported. and removed 🗺️ reQUEST Trigger label to import an issue into Quest labels Sep 8, 2023
@adegeo
Copy link
Contributor

adegeo commented Sep 26, 2023

@dotnet/wpf-developers Is there guidance on how to localize content for WPF with LocBaml being dead?

@adegeo
Copy link
Contributor

adegeo commented Oct 26, 2023

Pinged some internal folks. Waiting for an answer...

@adegeo
Copy link
Contributor

adegeo commented Oct 27, 2023

It doesn't seem like this is going to be fixed soon. 😢 dotnet/wpf#7245 I'll at least add a note to the article page.

@adegeo adegeo mentioned this issue Oct 31, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adegeo adegeo

Labels
doc-enhancement Improve the current content [org][type][category] dotnet-framework/svc Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Label to indicate an item has been imported. wpf/subsvc
Projects
No open projects
dotnet/docs October 2023 sprint
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update wpf-globalization-and-localization-overview.md dotnet/docs-desktop
3 participants
@dotnet-bot @ipizhenko @adegeo