Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support of unmanaged-export for Executable Modules (.exe) #18

Closed
3F opened this issue Oct 29, 2016 · 0 comments
Closed

Support of unmanaged-export for Executable Modules (.exe) #18

3F opened this issue Oct 29, 2016 · 0 comments
Labels
origin support
Milestone
v1.5

Comments

@3F
Copy link
Owner

3F commented Oct 29, 2016

just a note:

Now I added support of unmanaged-export for Executable Modules (.exe)

Before this, you could see something like:

Unable to start program '<Your_Application>.exe'.
... is not a valid Win32 application.

Now should work as and for library modules.
But important note: to debug of this modified .exe inside Visual Studio you should disable Debug - Enable the Visual Studio hosting process
@3F 3F added this to the v1.5 milestone Oct 29, 2016
@3F 3F closed this as completed Oct 29, 2016
3F added a commit that referenced this issue Nov 4, 2016
@3F
public release v1.5
ab1c3e6 
    * FIXED: Fixed problem with white-space chars in path: `Cannot find path '<any full path with spaces>' because it does not exist ...`
    * FIXED: Fixed typo with fullseq (ddNS) - incorrect `0x30 0x30` ~0x007A7-0x007A8  /details in #14
    * FIXED: Possible problem with NullReferenceException when removing package.
    * FIXED: Fixed problem with old NS data when we try to install package for project A, then for project B
    * NEW: Implemented 'Generate .exp + .lib via MS Library Manager' #9
           GUI Configurator + MSBuild property: `DllExportGenExpLib`

    * NEW: Added support of unmanaged-export for Executable Modules (.exe) #18
    * NEW: Cecil variant for ddNS features /#14, #2
    * NEW: Added our custom IL Assembler as option to fix incorrect 0x13 / 0x11 opcodes. #17
           GUI Configurator + MSBuild property: `DllExportOurILAsm`
           It should help for users of Fody projects, etc.
           Fody/Fody#271

           IlAsm 4.5.1 https://github.com/3F/coreclr
           based on 4.5.22220.0 / coreclr 1.0.4
           changelog of our coreclr for this release: https://github.com/3F/coreclr/blob/master/changelog.txt

    * CHANGED: Updated scripts of installing/removing package for more correct loading of our assemblies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
origin support
Projects
None yet
Milestone
v1.5
Development

No branches or pull requests
1 participant
@3F