Skip to content

fix(dotnet): onboarding install package #14335

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Jul 22, 2025
+11 −12
Merged

fix(dotnet): onboarding install package #14335

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
99262b4
fix(dotnet): onboarding install package
bruno-garcia Jul 11, 2025
687f6c4
add pkg dependency for profiling
bruno-garcia Jul 11, 2025
ee3727e
Apply suggestions from code review
bruno-garcia Jul 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 11 additions & 12 deletions docs/platforms/dotnet/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,35 +38,34 @@ Sentry captures data by using an SDK within your application's runtime. These ar

Install the **NuGet** package to add the Sentry dependency:

<OnboardingOption optionId="profiling">
<OnboardingOption optionId="error-monitoring">

```shell {tabTitle:.NET Core CLI}
dotnet add package Sentry -v {{@inject packages.version('sentry.dotnet') }}
```

<Alert>
```powershell {tabTitle:Package Manager}
Install-Package Sentry. -Version {{@inject packages.version('sentry.dotnet') }}
```

Sentry profiling for .NET is available in Alpha on .NET 8.0 and newer.
</OnboardingOption>

</Alert>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I get what's going on here. The file name of this mdx file indicates it's for the default docs for dotnet right (nothing to do with profiling). The only place I see this alert in the current live docs is here though:

Presumably that's because of the OnboardingOption optionId="profiling" in the code.

However, in the preview for this PR, I'm still seeing this alert:
image

Copy link
Member

@Flash0ver Flash0ver Jul 14, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that's similar, yet different <Alert>, isn't it?
From:

sentry-docs/docs/platforms/dotnet/common/profiling/index.mdx

Lines 12 to 22 in 80735a5

<Alert>
Sentry profiling for .NET is available in _Alpha_ on .NET 8.0+ for:
- Windows
- Linux
- macOS
- iOS
- Mac Catalyst
</Alert>

Do we want to remove the Alert from the profiling page too?

<OnboardingOption optionId="profiling">

```shell {tabTitle:.NET Core CLI}
dotnet add package Sentry -v {{@inject packages.version('sentry.dotnet') }}
dotnet add package Sentry.Profiling -v {{@inject packages.version('sentry.dotnet.profiling') }}
```

```powershell {tabTitle:Package Manager}
Install-Package Sentry -Version {{@inject packages.version('sentry.dotnet') }}
Install-Package Sentry.Profiling -Version {{@inject packages.version('sentry.dotnet.profiling') }}
```

```shell {tabTitle:Paket CLI}
paket add Sentry --version {{@inject packages.version('sentry.dotnet') }}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed for simplicity, dotnet is used by 90% of people at this point

paket add Sentry.Profiling --version {{@inject packages.version('sentry.dotnet.profiling') }}
```
</OnboardingOption>

## Configure

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
SentrySdk.Init(options =>
{
Expand All @@ -89,4 +88,4 @@ SentrySdk.Init(options =>

This snippet includes an intentional error, so you can test that everything is working as soon as you set it up.

<PlatformContent includePath="getting-started-verify" />
<PlatformContent includePath="getting-started-verify" />