nano Portable Executable (nPE) file format
From nf-interpreter created by cw2 : nanoframework/nf-interpreter#40
Based on NETMF's PE, but without its obsolete/unused features. Planned modifications:
- Follows ECMA-335 specification for metadata tables,
- Extending metadata tables is needed to support generics
- No padding information, always aligned to 32-bit boundary (even on the disk),
- No endianness information - handled on the PC side (?)
https://github.com/dotnet/corefx/tree/master/src/System.Reflection.Metadata/src/System/Reflection/Metadata/Ecma335
- [x] Does Roslyn provide extensibility point for a custom assembly emitter?
- [ ] If yes, implement Roslyn extension to produce nPE files
- [x] If not, implement managed tool to transform .NET dll into nPE (with MSBuild task wrapper?)
- [x] Update assembly loader C++ structures and functionality
- [x] Unit tests
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Still active
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
still active
Jose,
I’m still active. I haven’t had much time lately but plan on getting back to nF soon. The hard part will be to convince Christophe to become enthused again.
From: José Simões [email protected] Sent: Friday, October 11, 2019 9:15 AM To: nanoframework/Home [email protected] Cc: Subscribed [email protected] Subject: Re: [nanoframework/Home] nano Portable Executable (nPE) file format (#105)
still active
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nanoframework/Home/issues/105?email_source=notifications&email_token=ACB4QX7CWSRMOEI6GG3ZSP3QOB36LA5CNFSM4DY5DZZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA76V4Q#issuecomment-541059826 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACB4QX7HBHLI3HP2D6LIRR3QOB36LANCNFSM4DY5DZZA . https://github.com/notifications/beacon/ACB4QX6SIB47JA3RQLGINK3QOB36LA5CNFSM4DY5DZZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA76V4Q.gif
@josesimoes and @StephenCardinale looking at old issues to clean a bit things. Is this one still active? It's 3.5 years old ;-)
Yes. Most of this will be cleared with the ongoing work so hopefully we'll be able to close this soon.