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.

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

Port Mono.Cecil to .NET Standard 2.0. #542

Closed
wants to merge 1 commit into from
Closed

Port Mono.Cecil to .NET Standard 2.0. #542

wants to merge 1 commit into from

Conversation

alexdrl
Copy link

@alexdrl alexdrl commented Sep 26, 2018

Changed the target runtime to .NET Standard 2.0.

Removed some conditional compilation ifs that were
removing the ability to strong name code.
Bring back code in BaseAssemblyResolver that builds on
.NET Standard 2.0, enabling the search of assemblies in the
GAC, allowing the code to find assemblies in the GAC, even when
referenced from a net461 DLL in .NET Framework full.

I am not sure if the .NET Standard 2.0 DLL assemblies referenced in the nuspec file needs to be updated or not.

I ran the tests in .NET Standard 2.0 and all worked.

This PR is motivated by dsplaisted/strongnamer#31, in an effort to make it available on Linux. Sadly, this is not fully possible as of https://github.com/dotnet/corefx/issues/11225.

Changed the target runtime to .NET Standard 2.0.
Removed some conditional compilation ifs that were
removing the ability to strong name code.
Bring back code in BaseAssemblyResolver that builds on
.NET Standard 2.0, enabling the search of assemblies in the
GAC, allowing the code to find assemblies in the GAC, even when
referenced from a net461 DLL in .NET Framework full.
@alexdrl
Copy link
Author

alexdrl commented Sep 26, 2018

After creating this PR, I noticed that this PR #527 seems to do the same, but a lot more (changing the whole SDK and files, a more complete solution). Feel free to close this PR if the other solution is better or more suitable for the Project.

@jbevain
Copy link
Owner

jbevain commented Mar 5, 2019

Thank you for your contribution! We landed a different set of changes to move to the new SDK and to .NET Standard 2.0.

@jbevain jbevain closed this Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants