This repository has been archived by the owner on Aug 30, 2023. It is now read-only.
Feature/add dotnet core project #163
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
August 29, 2016 17:50
|
@reflectiondm: Thanks! But can you please coordinate with @wakawaka54 who just created #161? |
|
@asbjornu oh, sure! I somehow missed that the work has been started on your side =) |
Closed
|
I hope #197 gives us the .NET Core / Standard support we need, so I'm closing this. Please |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Please look into this port of SharpRaven to dotnet Core. A new project has been created, most of the files are directly referenced from a regular .net project. The ones that are incopatible have been replaced with dotnet core implementation.
A nuget package is created upon build.
I've tested the package with our dotnet core project and it works. Known issues: stacktrace is not attached to a request and thus is not in the exception details in Sentry.
Your feedback and suggestions are welcome.
This change is