Add migration guide for SharpRaven

We currently use the legacy SharpRaven nuget package, and are looking to migrate.

Some things that are not immediately obvious from reading the documentation (my apologies if I’ve missed this information):

• What is the replacement for SentryUserFactory?
• Is ASP.NET (Framework) integration supported?
• What is the replacement for LogScrubber?
• What is the recommended way to move away from RavenClient? Currently we create a global instance at application startup, and use this throughout. With SentrySdk.Init(), all the examples use a using statement - should we initialise whenever we log an exception, or continue using a global instance and disposing on application shutdown?

[bruno-garcia]

Lets finally tackle this, it’s been too long.

The task should:

• Add a sub page to the migration page: https://docs.sentry.io/platforms/dotnet/migration/ titled From SharpRaven
• To simplify, it can be a single file on the dotnet level and there we note migration for any integration like ASP.NET
• Add the items listed in this issue like UserFactory
• Capturing on the background vs async. Even if not awaited, no backpressure so in high error rate it would degrade performance of the app. If you await, latecy to sending events to Sentry would affect your user experience.
• First entry will be titled: Migrating from SharpRaven to Sentry and it should include:

• Note the minimum .NET Framework version required: SharpRaven can run on .NET Framework 3.5 or later. Sentry on the other hand only support .NET Framework 4.6.1 and later.
• How to Init the SDK. How to Init it for ASP.NET (install the package and AddAspNet).
• Events are sent in the background. The IDisposable returned from Init needs to be invoked before the problem exists. On ASP.NET classic, mention Sentry.AspNet must be installed to get HTTP related information.
• A series of: Before: await client.CaptureAsync(..) After: SentrySdk.CaptureEvent(..) (the event will be sent on a background thread and so it’ll not block the calling thread. The SharpRaven approach would not block the thread but only continue your code (i.e: return the HTTP request) once the SDK communicated with Sentry which was suboptimal.
• Before: client.Capture(..) After: SentrySdk.CaptureEvent(..)
• Before:

ravenClient.BeforeSend = requester =>
{
    // Here you can log data from the requester
    // or replace it entirely if you want.
    return requester;
};

After:

SentrySdk.Init(o => o.BeforeSend = e {
// Mutate the event or return null to drop it altogether
}

This should be a good start ^

List of features used used to announce to raven users: https://github.com/getsentry/raven-csharp/issues/281#issuecomment-565854063

[mrmonday]

Shall I open another issue for this?

Please feel free. Hasn’t been requested yet.

Done - #244

We have that scrubbing on the server.

This won’t cut it for cardholder data - for PCI-DSS compliance we cannot send Sentry cardholder data. There shouldn’t be any such data in exceptions anyway, but it needs to be filtered on our side just in case.

Again, thanks for your response.