Skip to content

Commit a4303b0

Browse files
committed
remove duplicate tabs in dotnet docs, fix links
1 parent 1e6f8ec commit a4303b0

File tree

2 files changed

+1
-56
lines changed

2 files changed

+1
-56
lines changed

content/en/tracing/setup/dotnet-core.md

Lines changed: 1 addition & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -226,30 +226,6 @@ There are multiple ways to configure the .NET Tracer:
226226
* creating a `datadog.json` file
227227

228228
{{< tabs >}}
229-
{{% tab "Code" %}}
230-
231-
To configure the Tracer in application code, create a `TracerSettings` from the default configuration sources. Set properties on this `TracerSettings` instance before passing it to a `Tracer` constructor. For example:
232-
233-
```csharp
234-
using Datadog.Trace;
235-
236-
// read default configuration sources (env vars, web.config, datadog.json)
237-
var settings = TracerSettings.FromDefaultSources();
238-
239-
// change some settings
240-
settings.ServiceName = "MyService";
241-
settings.AgentUri = new Uri("http://localhost:8126/");
242-
243-
// create a new Tracer using these settings
244-
var tracer = new Tracer(settings);
245-
246-
// set the global tracer
247-
Tracer.Instance = tracer;
248-
```
249-
250-
**Note:** Settings must be set on `TracerSettings` _before_ creating the `Tracer`. Changes made to `TracerSettings` properies after the `Tracer` is created are ignored.
251-
252-
{{% /tab %}}
253229

254230
{{% tab "Environment variables" %}}
255231

@@ -382,18 +358,6 @@ The following table lists configuration variables that are available only when u
382358

383359
{{< partial name="whats-next/whats-next.html" >}}
384360

385-
<<<<<<< HEAD
386-
[1]: /tracing/send_traces/
387-
[2]: /tracing/setup/dotnet-framework/
388-
[3]: https://dotnet.microsoft.com/platform/support/policy/dotnet-core
389-
[4]: https://github.com/DataDog/dd-trace-dotnet/issues/302#issuecomment-603269367
390-
[5]: /help/
391-
[6]: https://www.nuget.org/packages/Datadog.Trace
392-
[7]: /tracing/manual_instrumentation/dotnet/
393-
[8]: /tracing/guide/setting_primary_tags_to_scope/#environment
394-
[9]: /tagging/unified_service_tagging
395-
=======
396-
397361
[1]: https://app.datadoghq.com/apm/install
398362
[2]: /tracing/send_traces/
399363
[3]: /tracing/setup/dotnet-framework/
@@ -402,4 +366,4 @@ The following table lists configuration variables that are available only when u
402366
[6]: /help/
403367
[7]: /tracing/manual_instrumentation/dotnet
404368
[8]: /tracing/guide/setting_primary_tags_to_scope/#environment
405-
>>>>>>> master
369+
[9]: /tagging/unified_service_tagging

content/en/tracing/setup/dotnet-framework.md

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -167,25 +167,6 @@ Tracer.Instance = tracer;
167167

168168
{{% /tab %}}
169169

170-
{{% tab "Environment variables" %}}
171-
172-
To configure the Tracer using environment variables, set the variables before launching the instrumented application.
173-
174-
For example:
175-
176-
```cmd
177-
rem Set environment variables
178-
SET DD_TRACE_AGENT_URL=http://localhost:8126
179-
SET DD_SERVICE_NAME=MyService
180-
181-
rem Launch application
182-
example.exe
183-
```
184-
185-
**Note:** To set environment variables for a Windows Service, use the multi-string key `HKLM\System\CurrentControlSet\Services\{service name}\Environment` in the Windows Registry.
186-
187-
{{% /tab %}}
188-
189170
{{% tab "web.config" %}}
190171

191172
To configure the Tracer using an `app.config` or `web.config` file, use the `<appSettings>` section. For example:

0 commit comments

Comments
 (0)