Issue with starting and stopping a process with the profiler running in same process

[AnthonyDewhirst]

This looks like a reoccurrence of #186

To Reproduce Here is the code for a simple repo:

namespace ProfilerIssue;

public class Tests
{
    [Test]
    public async Task Test1()
    {
        var source = new CancellationTokenSource(TimeSpan.FromSeconds(2));
        await RunTestAsync(source.Token);
    }

    [Test]
    public async Task Test2()
    {
        var source = new CancellationTokenSource(TimeSpan.FromSeconds(2));
        await RunTestAsync(source.Token);
    }

    public async Task RunTestAsync(CancellationToken cancellationToken)
    {
        await Host.CreateDefaultBuilder()
            .ConfigureWebHostDefaults(webBuilder =>
            {
                webBuilder.UseStartup<Startup>();
            })
            .Build()
            .RunAsync(cancellationToken);
    }
}

public class Startup(IConfiguration configuration, IHostEnvironment hostEnvironment)
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddServiceProfiler();
    }

    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
    }
}

<Project Sdk="[Microsoft.NET](http://microsoft.net/).Sdk.Web">
  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <IsPackable>false</IsPackable>
    <IsTestProject>true</IsTestProject>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.ApplicationInsights.Profiler.AspNetCore" Version="2.7.1" />
    <PackageReference Include="Microsoft.Extensions.Hosting" Version="8.0.0" />
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.8.0" />
    <PackageReference Include="NUnit" Version="3.14.0" />
    <PackageReference Include="NUnit3TestAdapter" Version="4.5.0" />
  </ItemGroup>
  <ItemGroup>
    <Using Include="NUnit.Framework" />
  </ItemGroup>
</Project>

one tests passes then the other fails.

Expected behavior Both tests should pass

*Additional details Granted, this is not a normal usage - but we have gotten here because we are using Grpc test fixtures which boils down to doing the above using steps similar to here microsoft guide

My guess right now is that the static instance behaviour of Microsoft.ServiceProfiler.Utilities.CurrentProcessProvider in Assembly: Microsoft.ServiceProfiler.Common.Utilities, Version=2.6.2403.1501, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a captures the process once in the Lazy. And then when the services are configured for the second time, the process is no longer correct.

For now in the test code I have a dirty hack to inject a dispatch proxy in there instead which just returns 1 for the process id on all calls. Had to go this way as the interface is internal :-(

On a complete side note, Checkmarx is warning of a transitive dependency to Microsoft.IdentityModel.Tokens 6.11.1

[xiaomi7732]

Hey @AnthonyDewhirst, I'll take a look at this. Just curious, what is the reason for you to enable the Service Profiler during a test?

[AnthonyDewhirst]

Hey,

If you look at the linked code, it's for a grpc test, so you link to the web project and reference the real c# Startup code. So you get the service as you normally would. As in, you are pretty much testing the real set up.

Hopefully that makes sense?