sdk(dotnet): diagnostic logger pointer (#4143)

Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com>

Author: bruno-garcia

src/platforms/dotnet/configuration/diagnostic-logger.mdx renamed to src/includes/configuration/diagnostic-logger/dotnet.mdx

@@ -1,8 +1,3 @@
----
-title: Diagnostic Logger
-description: "Learn more about enabling SDK logging to help troubleshooting."
-sidebar_order: 20
----
 
 Sentry's SDK includes its own internal logger to report diagnostics that may be useful when troubleshooting your Sentry configuration. To enable logging, set the `Debug` option to `true`:
 
@@ -24,14 +19,14 @@ options =>
 
 By default, Sentry will write diagnostic messages to console. This may not be optimal in some circumstances; for example, when running applications that don't have a visible console window attached.
 
-To use a custom implementation of `IDiagnosticLogger`, you can pass it to the `DiagnosticLogger` option. Sentry comes with two implementations out of the box: `ConsoleDiagnosticLogger` and `DebugDiagnosticLogger`.
+To use a custom implementation of `IDiagnosticLogger`, you can pass it to the `DiagnosticLogger` option. Sentry comes with two implementations out of the box: `ConsoleDiagnosticLogger` and `TraceDiagnosticLogger`.
 
 ```csharp
 // Provide a custom logger
-options.DiagnosticLogger = new DebugDiagnosticLogger(SentryLevel.Debug);
+options.DiagnosticLogger = new TraceDiagnosticLogger(SentryLevel.Debug);
 ```
 
-The logger `DebugDiagnosticLogger` in the example uses the [.NET's Debug class](https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.debug). As a result, you can view the SDK logs inside Visual Studio's Debug log window, which is useful for technologies that don't have a Console to see the log messages, such as `WPF` and `ASP.NET`.
+The logger `TraceDiagnosticLogger` in the example uses the [.NET's Trace class](https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.trace). As a result, you can view the SDK logs inside Visual Studio's Debug log window, which is useful for technologies that don't have a Console to see the log messages, such as `WinForms`, `WPF` and `ASP.NET`.
 
 You can also create your own implementation of `IDiagnosticLogger` to fully customize logging behavior. For example, to naively append diagnostic messages to a file:
 

src/platforms/common/configuration/options.mdx

@@ -59,6 +59,12 @@ Enabling `debug` mode makes the SDK generate as much diagnostic data as possible
 
 </ConfigKey>
 
+<PlatformSection supported={["dotnet"]}>
+
+For app models that don't have a console to print to, you can <PlatformLink to="/configuration/diagnostic-logger/">customize the SDK's diagnostic logger</PlatformLink> to write to a file or to Visual Studio's debug window.
+
+</PlatformSection>
+
 <ConfigKey name="release">
 
 Sets the release. Some SDKs will try to automatically configure a release out of the box but it's a better idea to manually set it to guarantee that the release is in sync with your deploy integrations or source map uploads. Release names are strings, but some formats are detected by Sentry and might be rendered differently. Learn more about how to send release data so Sentry can tell you about regressions between releases and identify the potential source in [the releases documentation](/product/releases/).

src/platforms/common/enriching-events/attachments/index.mdx

@@ -9,6 +9,7 @@ supported:
   - java
   - javascript
   - dotnet
+  - unity
   - dart
   - flutter
 ---

src/platforms/dotnet/common/configuration/diagnostic-logger.mdx

@@ -0,0 +1,7 @@
+---
+title: Diagnostic Logger
+description: "Learn more about enabling SDK logging to help troubleshooting."
+sidebar_order: 20
+---
+
+<PlatformContent includePath="configuration/diagnostic-logger" />

src/platforms/dotnet/configuration/disable-integrations.mdx renamed to src/platforms/dotnet/common/configuration/disable-integrations.mdx

@@ -0,0 +1,7 @@
+---
+title: Diagnostic Logger
+description: "Learn more about enabling SDK logging to help troubleshooting."
+sidebar_order: 20
+---
+
+<PlatformContent includePath="configuration/diagnostic-logger" />