From 37a4467602c5475819deb0a797d7012b0ae876e5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20P=C3=B6lz?= <38893694+Flash0ver@users.noreply.github.com> Date: Mon, 2 Feb 2026 18:47:25 +0100 Subject: [PATCH 1/2] Add reproduction for sentry-dotnet#4819 Reproduces the bug where Sentry removes structured logging properties from scopes when the same parameter name is used in both BeginScope() and in a log message parameter. The reproduction demonstrates: - Setting up a BeginScope with structured data (e.g., Queue.HandlerName) - Logging messages within that scope using the same parameter name - The bug: Sentry incorrectly removes the scope property entirely This prevents filtering/searching logs by structured data properties. Co-Authored-By: Claude Sonnet 4.5 --- sentry-dotnet/.gitignore | 482 ++++++++++++++++++ sentry-dotnet/4819/Program.cs | 127 +++++ .../4819/Properties/launchSettings.json | 23 + sentry-dotnet/4819/README.md | 96 ++++ sentry-dotnet/4819/SentryLoggingRepro.csproj | 17 + sentry-dotnet/4819/SentryLoggingRepro.http | 11 + sentry-dotnet/4819/SentryLoggingRepro.slnx | 3 + .../4819/appsettings.Development.json | 8 + sentry-dotnet/4819/appsettings.json | 9 + 9 files changed, 776 insertions(+) create mode 100644 sentry-dotnet/.gitignore create mode 100644 sentry-dotnet/4819/Program.cs create mode 100644 sentry-dotnet/4819/Properties/launchSettings.json create mode 100644 sentry-dotnet/4819/README.md create mode 100644 sentry-dotnet/4819/SentryLoggingRepro.csproj create mode 100644 sentry-dotnet/4819/SentryLoggingRepro.http create mode 100644 sentry-dotnet/4819/SentryLoggingRepro.slnx create mode 100644 sentry-dotnet/4819/appsettings.Development.json create mode 100644 sentry-dotnet/4819/appsettings.json diff --git a/sentry-dotnet/.gitignore b/sentry-dotnet/.gitignore new file mode 100644 index 0000000..0808c4a --- /dev/null +++ b/sentry-dotnet/.gitignore @@ -0,0 +1,482 @@ +## Ignore Visual Studio temporary files, build results, and +## files generated by popular Visual Studio add-ons. +## +## Get latest from `dotnet new gitignore` + +# dotenv files +.env + +# User-specific files +*.rsuser +*.suo +*.user +*.userosscache +*.sln.docstates + +# User-specific files (MonoDevelop/Xamarin Studio) +*.userprefs + +# Mono auto generated files +mono_crash.* + +# Build results +[Dd]ebug/ +[Dd]ebugPublic/ +[Rr]elease/ +[Rr]eleases/ +x64/ +x86/ +[Ww][Ii][Nn]32/ +[Aa][Rr][Mm]/ +[Aa][Rr][Mm]64/ +bld/ +[Bb]in/ +[Oo]bj/ +[Ll]og/ +[Ll]ogs/ + +# Visual Studio 2015/2017 cache/options directory +.vs/ +# Uncomment if you have tasks that create the project's static files in wwwroot +#wwwroot/ + +# Visual Studio 2017 auto generated files +Generated\ Files/ + +# MSTest test Results +[Tt]est[Rr]esult*/ +[Bb]uild[Ll]og.* + +# NUnit +*.VisualState.xml +TestResult.xml +nunit-*.xml + +# Build Results of an ATL Project +[Dd]ebugPS/ +[Rr]eleasePS/ +dlldata.c + +# Benchmark Results +BenchmarkDotNet.Artifacts/ + +# .NET +project.lock.json +project.fragment.lock.json +artifacts/ + +# Tye +.tye/ + +# ASP.NET Scaffolding +ScaffoldingReadMe.txt + +# StyleCop +StyleCopReport.xml + +# Files built by Visual Studio +*_i.c +*_p.c +*_h.h +*.ilk +*.meta +*.obj +*.iobj +*.pch +*.pdb +*.ipdb +*.pgc +*.pgd +*.rsp +# but not Directory.Build.rsp, as it configures directory-level build defaults +!Directory.Build.rsp +*.sbr +*.tlb +*.tli +*.tlh +*.tmp +*.tmp_proj +*_wpftmp.csproj +*.log +*.tlog +*.vspscc +*.vssscc +.builds +*.pidb +*.svclog +*.scc + +# Chutzpah Test files +_Chutzpah* + +# Visual C++ cache files +ipch/ +*.aps +*.ncb +*.opendb +*.opensdf +*.sdf +*.cachefile +*.VC.db +*.VC.VC.opendb + +# Visual Studio profiler +*.psess +*.vsp +*.vspx +*.sap + +# Visual Studio Trace Files +*.e2e + +# TFS 2012 Local Workspace +$tf/ + +# Guidance Automation Toolkit +*.gpState + +# ReSharper is a .NET coding add-in +_ReSharper*/ +*.[Rr]e[Ss]harper +*.DotSettings.user + +# TeamCity is a build add-in +_TeamCity* + +# DotCover is a Code Coverage Tool +*.dotCover + +# AxoCover is a Code Coverage Tool +.axoCover/* +!.axoCover/settings.json + +# Coverlet is a free, cross platform Code Coverage Tool +coverage*.json +coverage*.xml +coverage*.info + +# Visual Studio code coverage results +*.coverage +*.coveragexml + +# NCrunch +_NCrunch_* +.*crunch*.local.xml +nCrunchTemp_* + +# MightyMoose +*.mm.* +AutoTest.Net/ + +# Web workbench (sass) +.sass-cache/ + +# Installshield output folder +[Ee]xpress/ + +# DocProject is a documentation generator add-in +DocProject/buildhelp/ +DocProject/Help/*.HxT +DocProject/Help/*.HxC +DocProject/Help/*.hhc +DocProject/Help/*.hhk +DocProject/Help/*.hhp +DocProject/Help/Html2 +DocProject/Help/html + +# Click-Once directory +publish/ + +# Publish Web Output +*.[Pp]ublish.xml +*.azurePubxml +# Note: Comment the next line if you want to checkin your web deploy settings, +# but database connection strings (with potential passwords) will be unencrypted +*.pubxml +*.publishproj + +# Microsoft Azure Web App publish settings. Comment the next line if you want to +# checkin your Azure Web App publish settings, but sensitive information contained +# in these scripts will be unencrypted +PublishScripts/ + +# NuGet Packages +*.nupkg +# NuGet Symbol Packages +*.snupkg +# The packages folder can be ignored because of Package Restore +**/[Pp]ackages/* +# except build/, which is used as an MSBuild target. +!**/[Pp]ackages/build/ +# Uncomment if necessary however generally it will be regenerated when needed +#!**/[Pp]ackages/repositories.config +# NuGet v3's project.json files produces more ignorable files +*.nuget.props +*.nuget.targets + +# Microsoft Azure Build Output +csx/ +*.build.csdef + +# Microsoft Azure Emulator +ecf/ +rcf/ + +# Windows Store app package directories and files +AppPackages/ +BundleArtifacts/ +Package.StoreAssociation.xml +_pkginfo.txt +*.appx +*.appxbundle +*.appxupload + +# Visual Studio cache files +# files ending in .cache can be ignored +*.[Cc]ache +# but keep track of directories ending in .cache +!?*.[Cc]ache/ + +# Others +ClientBin/ +~$* +*~ +*.dbmdl +*.dbproj.schemaview +*.jfm +*.pfx +*.publishsettings +orleans.codegen.cs + +# Including strong name files can present a security risk +# (https://github.com/github/gitignore/pull/2483#issue-259490424) +#*.snk + +# Since there are multiple workflows, uncomment next line to ignore bower_components +# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) +#bower_components/ + +# RIA/Silverlight projects +Generated_Code/ + +# Backup & report files from converting an old project file +# to a newer Visual Studio version. Backup files are not needed, +# because we have git ;-) +_UpgradeReport_Files/ +Backup*/ +UpgradeLog*.XML +UpgradeLog*.htm +ServiceFabricBackup/ +*.rptproj.bak + +# SQL Server files +*.mdf +*.ldf +*.ndf + +# Business Intelligence projects +*.rdl.data +*.bim.layout +*.bim_*.settings +*.rptproj.rsuser +*- [Bb]ackup.rdl +*- [Bb]ackup ([0-9]).rdl +*- [Bb]ackup ([0-9][0-9]).rdl + +# Microsoft Fakes +FakesAssemblies/ + +# GhostDoc plugin setting file +*.GhostDoc.xml + +# Node.js Tools for Visual Studio +.ntvs_analysis.dat +node_modules/ + +# Visual Studio 6 build log +*.plg + +# Visual Studio 6 workspace options file +*.opt + +# Visual Studio 6 auto-generated workspace file (contains which files were open etc.) +*.vbw + +# Visual Studio 6 auto-generated project file (contains which files were open etc.) +*.vbp + +# Visual Studio 6 workspace and project file (working project files containing files to include in project) +*.dsw +*.dsp + +# Visual Studio 6 technical files +*.ncb +*.aps + +# Visual Studio LightSwitch build output +**/*.HTMLClient/GeneratedArtifacts +**/*.DesktopClient/GeneratedArtifacts +**/*.DesktopClient/ModelManifest.xml +**/*.Server/GeneratedArtifacts +**/*.Server/ModelManifest.xml +_Pvt_Extensions + +# Paket dependency manager +.paket/paket.exe +paket-files/ + +# FAKE - F# Make +.fake/ + +# CodeRush personal settings +.cr/personal + +# Python Tools for Visual Studio (PTVS) +__pycache__/ +*.pyc + +# Cake - Uncomment if you are using it +# tools/** +# !tools/packages.config + +# Tabs Studio +*.tss + +# Telerik's JustMock configuration file +*.jmconfig + +# BizTalk build output +*.btp.cs +*.btm.cs +*.odx.cs +*.xsd.cs + +# OpenCover UI analysis results +OpenCover/ + +# Azure Stream Analytics local run output +ASALocalRun/ + +# MSBuild Binary and Structured Log +*.binlog + +# NVidia Nsight GPU debugger configuration file +*.nvuser + +# MFractors (Xamarin productivity tool) working folder +.mfractor/ + +# Local History for Visual Studio +.localhistory/ + +# Visual Studio History (VSHistory) files +.vshistory/ + +# BeatPulse healthcheck temp database +healthchecksdb + +# Backup folder for Package Reference Convert tool in Visual Studio 2017 +MigrationBackup/ + +# Ionide (cross platform F# VS Code tools) working folder +.ionide/ + +# Fody - auto-generated XML schema +FodyWeavers.xsd + +# VS Code files for those working on multiple tools +.vscode/* +!.vscode/settings.json +!.vscode/tasks.json +!.vscode/launch.json +!.vscode/extensions.json +*.code-workspace + +# Local History for Visual Studio Code +.history/ + +# Windows Installer files from build outputs +*.cab +*.msi +*.msix +*.msm +*.msp + +# JetBrains Rider +*.sln.iml +.idea/ + +## +## Visual studio for Mac +## + + +# globs +Makefile.in +*.userprefs +*.usertasks +config.make +config.status +aclocal.m4 +install-sh +autom4te.cache/ +*.tar.gz +tarballs/ +test-results/ + +# content below from: https://github.com/github/gitignore/blob/main/Global/macOS.gitignore +# General +.DS_Store +.AppleDouble +.LSOverride + +# Icon must end with two \r +Icon + + +# Thumbnails +._* + +# Files that might appear in the root of a volume +.DocumentRevisions-V100 +.fseventsd +.Spotlight-V100 +.TemporaryItems +.Trashes +.VolumeIcon.icns +.com.apple.timemachine.donotpresent + +# Directories potentially created on remote AFP share +.AppleDB +.AppleDesktop +Network Trash Folder +Temporary Items +.apdisk + +# content below from: https://github.com/github/gitignore/blob/main/Global/Windows.gitignore +# Windows thumbnail cache files +Thumbs.db +ehthumbs.db +ehthumbs_vista.db + +# Dump file +*.stackdump + +# Folder config file +[Dd]esktop.ini + +# Recycle Bin used on file shares +$RECYCLE.BIN/ + +# Windows Installer files +*.cab +*.msi +*.msix +*.msm +*.msp + +# Windows shortcuts +*.lnk + +# Vim temporary swap files +*.swp diff --git a/sentry-dotnet/4819/Program.cs b/sentry-dotnet/4819/Program.cs new file mode 100644 index 0000000..5ca0d61 --- /dev/null +++ b/sentry-dotnet/4819/Program.cs @@ -0,0 +1,127 @@ +using Sentry; +using Sentry.Serilog; +using Serilog; +using Serilog.Events; + +// Configure Serilog with Sentry sink +Log.Logger = new LoggerConfiguration() + .MinimumLevel.Debug() + .WriteTo.Console() + .WriteTo.Sentry(o => + { + o.Dsn = Environment.GetEnvironmentVariable("SENTRY_DSN"); + o.Debug = true; + o.MinimumBreadcrumbLevel = LogEventLevel.Debug; + o.MinimumEventLevel = LogEventLevel.Information; + }) + .CreateLogger(); + +var builder = WebApplication.CreateBuilder(args); + +// Configure Serilog for ASP.NET Core +builder.Host.UseSerilog(); + +// Configure Sentry for ASP.NET Core +builder.WebHost.UseSentry(options => +{ + options.Dsn = Environment.GetEnvironmentVariable("SENTRY_DSN"); + options.Debug = true; + options.TracesSampleRate = 1.0d; + options.Environment = "development"; + + // Enable logs + options.EnableLogs = true; + + // Add a no-op SetBeforeSendLog callback for debugging + options.SetBeforeSendLog((log) => + { + // Breakpoint here to inspect the log before it's sent to Sentry + return log; + }); +}); + +var app = builder.Build(); + +// Add test endpoint that demonstrates the bug +app.MapGet("/test", (ILogger logger) => +{ + var queueHandlerForScope = "JobProcessorFromScope"; + var queueHandlerForLogs = "JobProcessor"; + + // Log 1: Before using scope, with the parameter + logger.LogInformation("Testing some log before using with the handlerName {Queue.HandlerName}", queueHandlerForLogs); + + // Create a scope with both simple and dot-separated parameter names + using (logger.BeginScope(new Dictionary + { + { "Queue.HandlerName", queueHandlerForScope }, + { "SimpleParam", "SimpleValue" } + })) + { + // Log 2: After using scope, with the same parameter name + // BUG: This causes the property.Queue.HandlerName to be removed from Sentry + logger.LogInformation("Testing some log after using with the handlerName {Queue.HandlerName}", queueHandlerForLogs); + + // Log 3: After using scope, without providing the parameter again + // This should have the scope property present + logger.LogInformation("Testing some log after using with no handlerName"); + + // Log 4: Using simple parameter name with scope + logger.LogInformation("Testing with simple param {SimpleParam}", "DifferentValue"); + } + + return Results.Ok(new + { + Message = "Logs sent to Sentry. Check Sentry dashboard to see the bug.", + ExpectedBehavior = "Log 2 should have property.Queue.HandlerName set to 'JobProcessorFromScope'", + ActualBehavior = "Log 2 has property.Queue.HandlerName removed by Sentry SDK", + Impact = "Cannot filter/search logs by structured data properties when the same parameter name is used in both scope and log message" + }); +}); + +// Add another endpoint with more examples +app.MapGet("/test-detailed", (ILogger logger) => +{ + logger.LogInformation("=== Starting detailed test ==="); + + // Scenario 1: Simple parameter name + using (logger.BeginScope(new Dictionary + { + { "UserId", "user-from-scope" } + })) + { + logger.LogInformation("Logging with UserId {UserId}", "user-from-log"); + logger.LogInformation("Logging without providing UserId"); + } + + logger.LogInformation("=== Scenario 1 complete ==="); + + // Scenario 2: Dot-separated parameter name (from issue) + using (logger.BeginScope(new Dictionary + { + { "Queue.HandlerName", "ScopeHandler" } + })) + { + logger.LogInformation("Handler is {Queue.HandlerName}", "LogHandler"); + logger.LogInformation("Handler from scope only"); + } + + logger.LogInformation("=== Scenario 2 complete ==="); + + // Scenario 3: Multiple dot-separated parameters + using (logger.BeginScope(new Dictionary + { + { "Request.Id", "req-123-scope" }, + { "Request.Method", "GET" } + })) + { + logger.LogInformation("Processing request {Request.Id} with method {Request.Method}", + "req-456-log", "POST"); + } + + logger.LogInformation("=== Test complete ==="); + + return Results.Ok("Check Sentry for logged events"); +}); + +app.Run(); diff --git a/sentry-dotnet/4819/Properties/launchSettings.json b/sentry-dotnet/4819/Properties/launchSettings.json new file mode 100644 index 0000000..b9e77ff --- /dev/null +++ b/sentry-dotnet/4819/Properties/launchSettings.json @@ -0,0 +1,23 @@ +{ + "$schema": "https://json.schemastore.org/launchsettings.json", + "profiles": { + "http": { + "commandName": "Project", + "dotnetRunMessages": true, + "launchBrowser": false, + "applicationUrl": "http://localhost:4819", + "environmentVariables": { + "ASPNETCORE_ENVIRONMENT": "Development" + } + }, + "https": { + "commandName": "Project", + "dotnetRunMessages": true, + "launchBrowser": false, + "applicationUrl": "https://localhost:4820;http://localhost:4819", + "environmentVariables": { + "ASPNETCORE_ENVIRONMENT": "Development" + } + } + } +} diff --git a/sentry-dotnet/4819/README.md b/sentry-dotnet/4819/README.md new file mode 100644 index 0000000..e5339ea --- /dev/null +++ b/sentry-dotnet/4819/README.md @@ -0,0 +1,96 @@ +# Reproduction for sentry-dotnet#4819 + +**Issue:** https://github.com/getsentry/sentry-dotnet/issues/4819 + +## Description + +This reproduction demonstrates a bug where Sentry removes structured logging properties from scopes when the same parameter name is used in both `BeginScope()` and in a log message parameter. + +When using `ILogger.BeginScope()` to define structured data properties (e.g., `Queue.HandlerName`) and then logging a message with the same parameter name, Sentry incorrectly removes the property from the scope data. This breaks the ability to filter and search logs by these structured data properties. + +## The Bug + +**What should happen:** +- Scope property `Queue.HandlerName` should remain in `property.Queue.HandlerName` +- Log message parameter `{Queue.HandlerName}` should appear in `message.parameters.Queue.HandlerName` +- Both values should be preserved + +**What actually happens:** +- When a log message uses the same parameter name as a scope property, Sentry removes the property from the scope data entirely +- Only the message parameter is preserved +- This breaks searching/filtering by structured data properties + +## Steps to Reproduce + +### 1. Set up Sentry DSN (optional) + +If you want to see the logs in Sentry: +```bash +export SENTRY_DSN="your-dsn-here" +``` + +If you leave it empty, the logs will still be visible in the console output showing the bug behavior. + +### 2. Build and run the application + +```bash +cd SentryLoggingRepro +dotnet build +dotnet run +``` + +The application will start on http://localhost:5000 (or check the console output for the actual port). + +### 3. Trigger the reproduction + +Open your browser or use curl to hit the test endpoints: + +```bash +# Basic test (matches the original issue) +curl http://localhost:5000/test + +# Detailed test with multiple scenarios +curl http://localhost:5000/test-detailed +``` + +### 4. Observe the bug + +Check the console output or your Sentry dashboard. You'll see that: + +- **Log 1** (before scope): `property.Queue.HandlerName` is NOT present (expected, no scope yet) +- **Log 2** (inside scope with same param name): `property.Queue.HandlerName` is MISSING (BUG! Should be "JobProcessorFromScope") +- **Log 3** (inside scope without param): `property.Queue.HandlerName` is present with "JobProcessorFromScope" (correct) + +The bug is in Log 2 - when you log with a parameter that has the same name as a scope property, Sentry removes the scope property entirely. + +## Expected Behavior + +All logs within the scope should have `property.Queue.HandlerName` set to `"JobProcessorFromScope"`, regardless of whether the log message also uses `{Queue.HandlerName}` as a parameter. + +The scope properties should be used for filtering and searching, while message parameters are for the rendered message template. + +## Actual Behavior + +Sentry's deduplication logic incorrectly removes scope properties when a log message parameter has the same name. This breaks the structured logging workflow where: +1. You set up a scope with contextual properties (e.g., handler name, request ID) +2. You log messages that may reference those same properties + +## Environment + +- **.NET SDK:** 10.0.102 +- **Sentry.AspNetCore:** 6.0.0 +- **Sentry.Serilog:** 6.0.0 +- **Serilog.AspNetCore:** 10.0.0 +- **OS:** macOS (should reproduce on any OS) + +## Impact + +This bug prevents using structured logging properties from scopes for filtering/searching in Sentry when the log message parameters happen to use the same names. This is a common pattern where: +- Scopes define contextual data for a block of code (e.g., `Queue.HandlerName`) +- Individual log messages reference that context in their message templates + +Users expect scope properties to always be available for filtering, regardless of message parameters. + +## Related Issue Comments + +The reproduction steps are based on this comment: https://github.com/getsentry/sentry-dotnet/issues/4819#issuecomment-3834832076 diff --git a/sentry-dotnet/4819/SentryLoggingRepro.csproj b/sentry-dotnet/4819/SentryLoggingRepro.csproj new file mode 100644 index 0000000..f12cb1b --- /dev/null +++ b/sentry-dotnet/4819/SentryLoggingRepro.csproj @@ -0,0 +1,17 @@ + + + + net10.0 + enable + enable + + + + + + + + + + + diff --git a/sentry-dotnet/4819/SentryLoggingRepro.http b/sentry-dotnet/4819/SentryLoggingRepro.http new file mode 100644 index 0000000..6d42f8c --- /dev/null +++ b/sentry-dotnet/4819/SentryLoggingRepro.http @@ -0,0 +1,11 @@ +@SentryLoggingRepro_HostAddress = http://localhost:4819 + +GET {{SentryLoggingRepro_HostAddress}}/test/ +Accept: application/json + +### + +GET {{SentryLoggingRepro_HostAddress}}/test-detailed/ +Accept: application/json + +### diff --git a/sentry-dotnet/4819/SentryLoggingRepro.slnx b/sentry-dotnet/4819/SentryLoggingRepro.slnx new file mode 100644 index 0000000..9c8cb2d --- /dev/null +++ b/sentry-dotnet/4819/SentryLoggingRepro.slnx @@ -0,0 +1,3 @@ + + + diff --git a/sentry-dotnet/4819/appsettings.Development.json b/sentry-dotnet/4819/appsettings.Development.json new file mode 100644 index 0000000..0c208ae --- /dev/null +++ b/sentry-dotnet/4819/appsettings.Development.json @@ -0,0 +1,8 @@ +{ + "Logging": { + "LogLevel": { + "Default": "Information", + "Microsoft.AspNetCore": "Warning" + } + } +} diff --git a/sentry-dotnet/4819/appsettings.json b/sentry-dotnet/4819/appsettings.json new file mode 100644 index 0000000..10f68b8 --- /dev/null +++ b/sentry-dotnet/4819/appsettings.json @@ -0,0 +1,9 @@ +{ + "Logging": { + "LogLevel": { + "Default": "Information", + "Microsoft.AspNetCore": "Warning" + } + }, + "AllowedHosts": "*" +} From 82be6a2085d9625937f41365ee03e8e659e322ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20P=C3=B6lz?= <38893694+Flash0ver@users.noreply.github.com> Date: Mon, 9 Feb 2026 17:42:37 +0100 Subject: [PATCH 2/2] stop multi-level merging for all .NET repro projects --- sentry-dotnet/Directory.Build.props | 3 +++ sentry-dotnet/Directory.Build.targets | 3 +++ sentry-dotnet/Directory.Packages.props | 8 ++++++++ 3 files changed, 14 insertions(+) create mode 100644 sentry-dotnet/Directory.Build.props create mode 100644 sentry-dotnet/Directory.Build.targets create mode 100644 sentry-dotnet/Directory.Packages.props diff --git a/sentry-dotnet/Directory.Build.props b/sentry-dotnet/Directory.Build.props new file mode 100644 index 0000000..eed962e --- /dev/null +++ b/sentry-dotnet/Directory.Build.props @@ -0,0 +1,3 @@ + + + diff --git a/sentry-dotnet/Directory.Build.targets b/sentry-dotnet/Directory.Build.targets new file mode 100644 index 0000000..eed962e --- /dev/null +++ b/sentry-dotnet/Directory.Build.targets @@ -0,0 +1,3 @@ + + + diff --git a/sentry-dotnet/Directory.Packages.props b/sentry-dotnet/Directory.Packages.props new file mode 100644 index 0000000..f4e75ac --- /dev/null +++ b/sentry-dotnet/Directory.Packages.props @@ -0,0 +1,8 @@ + + + + false + + + +