Skip to content

Remove C# bindings from windows-build submodule #746

Closed

Description

Until dotnet/cli#819 is resolved, we cannot regenerate the C# bindings for the resources. While the resources themselves are automatically regenerated thanks to #743, if a string is added or removed, the C# bindings will still need to be manually updated.

Activity

  1. joeyaiello commented on Apr 14, 2016

    @joeyaiello
    Contributor

    Keep me honest, I need to get more context on this one.

  2. modified the milestone: on Apr 20, 2016
  3. andyleejordan commented on Apr 27, 2016

    @andyleejordan
    MemberAuthor

    Joey Aiello (@joeyaiello) The context is that PowerShell depends on the ability to auto-generate strongly typed C# classes used for accessing resource strings, and the dotnet-resgen tool does not yet support it. It is a major blocker for moving the Windows PowerShell teams to PowerShell repo.

  4. added and removed
    Blockedblocked on something external to this repo
    on Jun 15, 2016
  5. added a commit that references this issue on Jun 15, 2016
    94e3be2
  6. andyleejordan commented on Jun 15, 2016

    @andyleejordan
    MemberAuthor

    sergei (@vors) while dotnet-resgen isn't doing this for us, we've successfully worked around it, without the hacky submodule trick. So let's keep this closed?

  7. vors commented on Jun 15, 2016

    @vors
    Collaborator

    Andy Jordan (@andschwa) yes, we have enough open issues :P

  8. added a commit that references this issue on Aug 6, 2026
    31eb27d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions