-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
dotnet-resgen #4334
Comments
I'm going to put something temporary together for the sake of dnu parity but we need to think about the responsibilities of each of the tools. The steps are:
|
Does this (or will it one day) provide the second feature of ResGen, that is, to create the strongly typed classes (either generating the .cs files or just emit the code) ? (Desperately to know :) ) |
This tool needs to be renamed dotnet-resgen until it's at parity with resgen. It's clashing on paths. |
@davidfowl what's left here for Beta milestone? |
@davidfowl @piotrpMSFT Will strongly typed classes be part of the beta milestone? |
Beta is basically done. We will be branching soon. |
@davidfowl What's the status on strongly typed class generation? I thought we were tracking that here, shall I make a new issue? |
Yes, make a new one. |
I think dotnet/cli#819 is it. |
https://msdn.microsoft.com/en-us/library/ccec7sz1(v=vs.110).aspx
We're going to need to either port resgen to coreclr or just write a new command that replicates some of the functionality. Today in the DNX we replicate some of it and pass data to the roslyn APIs. I'd imagine compile would work like this:
dotnet-compile /foo/project.json
dotnet-resgen /foo/project.json
resgen /foo/Resources.resx
resgen /foo/Resources2.resx
dotnet-compile-csc /foo/bin/dnxcore50/dotnet-compile.csc.rsp
I ran into this while trying to compile nuget with
dotnet compile
The text was updated successfully, but these errors were encountered: