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
changed the title [-]Removed namedResource section when dotnet-resgen can produce C# bindings and resources [Blocked][/-][+]Removed namedResource section when dotnet-resgen can produce C# bindings and resources[/+]on Jan 23, 2016
changed the title [-]Removed namedResource section when dotnet-resgen can produce C# bindings and resources[/-][+]Cross-platform resgen[/+]on Mar 15, 2016
Activity
andyleejordan commentedon Jan 23, 2016
This is utterly blocked and a major kink in the build process until resgen supports generating strongly typed classes.
andyleejordan commentedon Jan 23, 2016
It is also what requires windows-build to be a submodule, as we need access to things we can only generate on Windows. It's very ugly.
[-]Removed namedResource section when dotnet-resgen can produce C# bindings and resources [Blocked][/-][+]Removed namedResource section when dotnet-resgen can produce C# bindings and resources[/+]andyleejordan commentedon Feb 16, 2016
This is now blocked on dotnet/cli#819
[-]Removed namedResource section when dotnet-resgen can produce C# bindings and resources[/-][+]Cross-platform resgen[/+]andyleejordan commentedon Mar 28, 2016
We're now using
dotnet-resgen, but still need C# bindings. Opening separate issue.