You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remove C# bindings from windows-build submodule #746
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.
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.
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?
Activity
joeyaiello commentedon Apr 14, 2016
Keep me honest, I need to get more context on this one.
andyleejordan commentedon Apr 27, 2016
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-resgentool does not yet support it. It is a major blocker for moving the Windows PowerShell teams to PowerShell repo.Update resources.md doc, partialy fix #746
andyleejordan commentedon Jun 15, 2016
sergei (@vors) while
dotnet-resgenisn't doing this for us, we've successfully worked around it, without the hacky submodule trick. So let's keep this closed?vors commentedon Jun 15, 2016
Andy Jordan (@andschwa) yes, we have enough open issues :P
Update resources.md doc, partialy fix PowerShell#746