Skip to content
This repository was archived by the owner on Mar 30, 2019. It is now read-only.

Coreclr#651

Closed
manu-st wants to merge 20 commits intosharpdx:masterfrom
manu-st:coreclr
Closed

Coreclr#651
manu-st wants to merge 20 commits intosharpdx:masterfrom
manu-st:coreclr

Conversation

@manu-st
Copy link
Copy Markdown
Contributor

@manu-st manu-st commented Sep 27, 2015

To make it compile and run against CoreCLR

Emmanuel Stapf added 20 commits August 23, 2015 22:22
…rsion since we should use the one defined in SharpDX.PreSettings.targets.
…l be used to compile SharpFX against CoreCLR.
…HandleRef is not present in CoreCLR/CoreFX.
…evice.cs where we do not have access to the Winform Application class, so we cannot use it. We also add to define our own version of IMessageFilter, Keys and Message normally define in Winforms.
…on. This is while we find a solution for implementing them in CoreCLR if we need it one day.
…andle instead of SafeWaitHandle. Unfortunately the extension method is only available in .NET Framework 4.6 so we still have to keep the old way of accessing SafeWaitHandle.
…andle instead of SafeWaitHandle. Unfortunately the extension method is only available in .NET Framework 4.6 so we still have to keep the old way of accessing SafeWaitHandle.
…or the time being we will assume that the argument is a valid handle of a Window in CoreCLR.
…own Is64BitProcess routine and are using it regardless of being running under the .NET Framework or CoreCLR.
…that are meaningful only when running under Winforms.
…and it might require hand modification to run against someone's checkout.
@xoofx
Copy link
Copy Markdown
Member

xoofx commented Mar 31, 2017

Hi @manu-silicon

Closing this issue as the PR #868 has partially solved the generation of compatible CoreCLR assemblies.

There could be some remaining issues related to some API that could be used on CoreCLR but are not compatible. We can address them later if it is necessary.

@xoofx xoofx closed this Mar 31, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants