-
Notifications
You must be signed in to change notification settings - Fork 84
Fixed most of the Portability Report issues #229
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
Conversation
…Trace still not working.
| using System; | ||
| using System.Runtime.Serialization; | ||
|
|
||
| [Serializable] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could polyfill this if you wanted. Removing for everyone means you can no longer take exception across appdomains
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By polyfill, do you mean #if statements?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Create an attribute in your code in the right namespace. Does nothing but don't need ifs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I see what you mean. But then I would still need an #if for the serializable constructor?
…iling for reports. Also removed the resx as I was having issues loading it. Possibly related to aspnet/Tooling#532
First pass at making coreclr compatible
Fixed stack overflow issue in the tests
Took dependency on Json.Net which is hopefully only temporary.
Outstanding issues are AppDomain unload and StackTrace.