-
-
Notifications
You must be signed in to change notification settings - Fork 610
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
Missing support to manipulate win32 resources in modules. #3
Comments
JB, if you're still planning to implement this, perhaps you could adapt the code from ResourceLib (http://resourcelib.codeplex.com/). It's an MIT-licensed project for manipulating Win32 resources in an assembly. |
Hey. Thanks for the suggestion, it's definitely a planned feature for 1.0. @carlokok also has some code for that in his fork. Now I only need to take the time to take care of it :) |
With a MIT license and the code now on Github, I have to agree with @jack-pappas in that ResourceLib looks like an excellent contender for solving this. As far as I understand the licensing, the code can just be copied from ResourceLib and into Cecil; no references required (although I wouldn't necessarily oppose a NuGet dependency). |
@asbjornu except that the code is full of pinvokes and apparently reads directly from the file on disk by doing a win32 LoadLibrary. Not quite the approach we want :) |
That's not a very crossplatform way to do it, no. 😄 Please let me know if there's anything I can do to help get this implemented. |
Allow upstream consumers to override build settings
…ns_tests2 Added tests for windows runtime projections.
Cecil can round-trip an assembly containing win32 resources, and will preserve them, but doesn't offer a way to add / modify / remove win32 resources.
The text was updated successfully, but these errors were encountered: