Fix SDK getting started pages (onboarding options) (#12960)

* fix(elixir): code block formatting

* fix(.net): onboarding options

* fix(php): onboarding options

* fix(js): angular onboarding options

* fix(js): astro onboarding options

* fix(js): aws lambda onboarding options

* fix(js): azure functions onboarding options

* fix(js): bun onboarding options

* fix(js): capacitor onboarding options

* fix(js): cloudflare onboarding options

* fix(js): connect onboarding options

* fix(js): cordova onboarding options

* fix(js): deno onboarding options

* fix(js): electron onboarding options

* fix(js): ember onboarding options

* fix(js): deno code snippet for npm

* fix(js): express onboarding options

* fix(js): fastify onboarding options

* fix(js): gatsby onboarding options

* fix(js): gcp functions onboarding options

* fix(js): hapi onboarding options

* fix(js): hono onboarding options

* fix(js): koa onboarding options

* fix(js): nest.js onboarding options

* fix(js): next.js onboarding options

* fix(js): nuxt onboarding options

* fix(js): react onboarding options

* fix(js): react-router onboarding options

* fix(js): remix onboarding options

* fix(js): solid onboarding options

* fix(js): solidstart onboarding options

* fix(js): svelte onboarding options

* fix(js): sveltekit onboarding options

* fix(js): vue onboarding options

* fix(js): wasm onboarding options

Author: stephanie-anderson

docs/platforms/dotnet/guides/aspnet/index.mdx

@@ -34,7 +34,7 @@ as well as your logs as breadcrumbs. The logging integrations also capture event
 You configure the SDK in the `Global.asax.cs`:
 
 
-```csharp {"onboardingOptions": {"performance": "21-24, 34-43"}}
+```csharp {"onboardingOptions": {"performance": "20-23, 33-42"}}
 using System;
 using System.Web;
 using Sentry.AspNet;

docs/platforms/dotnet/guides/aws-lambda/index.mdx

@@ -35,7 +35,7 @@ All `ASP.NET Core` configurations are valid here. But one configuration in parti
 `FlushOnCompletedRequest` ensures all events are flushed out. This is because the general ASP.NET Core hooks for when the process is exiting are not guaranteed to run in a serverless environment. This setting ensures that no event is lost if AWS recycles the process.
 
 
-```csharp {"onboardingOptions": {"performance": "12-14"}}
+```csharp {"onboardingOptions": {"performance": "12-15"}}
 public class LambdaEntryPoint : Amazon.Lambda.AspNetCoreServer.APIGatewayProxyFunction
 {
     protected override void Init(IWebHostBuilder builder)

docs/platforms/dotnet/guides/azure-functions-worker/index.mdx

@@ -33,7 +33,7 @@ This package extends [Sentry.Extensions.Logging](/platforms/dotnet/guides/extens
 
 Sentry integration with Azure Functions is done by calling `.UseSentry()` and specifying the options, for example:
 
-```csharp {"onboardingOptions": {"performance": "11-13"}}
+```csharp {"onboardingOptions": {"performance": "10-12"}}
 using Sentry.Azure.Functions.Worker;
 
 var builder = FunctionsApplication.CreateBuilder(args);
@@ -57,7 +57,7 @@ If using the ASP.NET Core integration add `UseSentry` to the `ConfigureFunctions
 
 </Alert>
 
-```csharp 
+```csharp {"onboardingOptions": {"performance": "11-13"}}
 using Sentry.Azure.Functions.Worker;
 
 var host = new HostBuilder()

docs/platforms/dotnet/guides/blazor-webassembly/index.mdx

@@ -8,6 +8,8 @@ Sentry provides an integration with Blazor WebAssembly through the [Sentry.AspNe
 
 ## Install
 
+<OnboardingOptionButtons options={['error-monitoring', 'performance']}/>
+
 Add the Sentry dependency to your Blazor WebAssembly application:
 
 ```shell {tabTitle:.NET Core CLI}
@@ -26,16 +28,14 @@ Sentry integration with Blazor WebAssembly is done by calling `.UseSentry()` and
 
 
 
-```csharp
+```csharp {"onboardingOptions": {"performance": "5"}}
 var builder = WebAssemblyHostBuilder.CreateDefault(args);
 builder.UseSentry(options =>
 {
-        options.Dsn = "___PUBLIC_DSN___";
-        options.TracesSampleRate = 0.1;
-        // When configuring for the first time, to see what the SDK is doing:
-        // options.Debug = true;
-
-
+    options.Dsn = "___PUBLIC_DSN___";
+    options.TracesSampleRate = 0.1;
+    // When configuring for the first time, to see what the SDK is doing:
+    // options.Debug = true;
 });
 
 // Captures logError and higher as events

docs/platforms/dotnet/guides/entityframework/index.mdx

@@ -45,7 +45,7 @@ Add the Entity Framework 6 support to your project in one step:
 
 For example, configuring an ASP.NET app with _global.asax_:
 
-```csharp {filename:global.asax} {"onboardingOptions": {"performance": "16-18, 27-36"}}
+```csharp {filename:global.asax} {"onboardingOptions": {"performance": "15-17, 26-35"}}
 using System;
 using System.Configuration;
 using Sentry.AspNet;

docs/platforms/dotnet/guides/uwp/index.mdx

@@ -28,7 +28,7 @@ The SDK should be initialized in the constructor of your application class (usua
 </Alert>
 
 
-```csharp {"onboardingOptions": {"performance": "18-21"}}
+```csharp {"onboardingOptions": {"performance": "17-20"}}
 using Sentry.Protocol;
 using UnhandledExceptionEventArgs = Windows.UI.Xaml.UnhandledExceptionEventArgs;
 

docs/platforms/dotnet/guides/winforms/index.mdx

@@ -30,7 +30,7 @@ You should also set `Application.SetUnhandledExceptionMode(UnhandledExceptionMod
 A complete example of the recommended startup is as follows:
 
 
-```csharp {"onboardingOptions": {"performance": "32-35"}}
+```csharp {"onboardingOptions": {"performance": "31-34"}}
 using System;
 using System.Windows.Forms;
 

docs/platforms/dotnet/guides/winui/index.mdx

@@ -32,9 +32,7 @@ In addition to capturing errors, you can monitor interactions between multiple s
 
 Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.
 
-<OnboardingOptionButtons options={['error-monitoring', 'performance']}/>
-
-```csharp {"onboardingOptions": {"performance": "17-20"}}
+```csharp {"onboardingOptions": {"performance": "16-19"}}
 using Sentry.Protocol;
 
 sealed partial class App : Application
@@ -50,7 +48,7 @@ sealed partial class App : Application
             // When configuring for the first time, to see what the SDK is doing:
             options.Debug = true;
 
-            // Set traces_sample_rate to 1.0 to capture 100% of transactions for tracing.
+            // Set TracesSampleRate to 1.0 to capture 100% of transactions for tracing.
             // We recommend adjusting this value in production.
             options.TracesSampleRate = 1.0;
 
@@ -79,7 +77,7 @@ Do not initialize the SDK in the `OnLaunched` event of the application or the `H
 </Alert>
 
 
-```csharp
+```csharp {"onboardingOptions": {"performance": "18-21"}}
 // Add these to your existing using statements.
 using Sentry.Protocol;
 using UnhandledExceptionEventArgs = Microsoft.UI.Xaml.UnhandledExceptionEventArgs;
@@ -97,7 +95,7 @@ sealed partial class App : Application
             // When configuring for the first time, to see what the SDK is doing:
             o.Debug = true;
 
-            // Set traces_sample_rate to 1.0 to capture 100% of transactions for tracing.
+            // Set TracesSampleRate to 1.0 to capture 100% of transactions for tracing.
             // We recommend adjusting this value in production.
             o.TracesSampleRate = 1.0;
 

docs/platforms/dotnet/guides/xamarin/index.mdx

@@ -21,7 +21,27 @@ The SDK is compatible with the following versions or higher:
 
 After you’ve completed setting up a project in Sentry, Sentry will give you a value which we call a DSN or Data Source Name. It looks a lot like a standard URL, but it’s just a representation of the configuration required by the Sentry SDKs. It consists of a few pieces, including the protocol, public key, the server address, and the project identifier.
 
-<PlatformContent includePath="getting-started-config" />
+<OnboardingOptionButtons options={['error-monitoring', 'performance']}/>
+
+You should initialize the SDK as early as possible, for an example, the start of OnCreate
+on MainActivity for Android, and, the top of FinishedLaunching on AppDelegate for iOS).
+
+```csharp {"onboardingOptions": {"performance": "8-11"}}
+SentryXamarin.Init(options =>
+{
+    options.AddXamarinFormsIntegration();
+    // Tells which project in Sentry to send events to:
+    options.Dsn = "___PUBLIC_DSN___";
+    // When configuring for the first time, to see what the SDK is doing:
+    options.Debug = true;
+    // Set TracesSampleRate to 1.0 to capture 100%
+    // of transactions for tracing.
+    // We recommend adjusting this value in production
+    options.TracesSampleRate = 1.0;
+});
+// App code
+
+```
 
 ## Verify
 

docs/platforms/dotnet/index.mdx

@@ -81,7 +81,7 @@ Install the **NuGet** package to add the Sentry dependency:
 To capture all errors, even the one during the startup of your application, you should initialize the Sentry .NET SDK as soon as possible.
 
 
-```csharp {"onboardingOptions": {"performance": "6-7", "profiling": "8-9"}}
+```csharp {"onboardingOptions": {"performance": "5-6", "profiling": "7-8"}}
 SentrySdk.Init(options =>
 {
     options.Dsn = "https://[email protected]/5428537";