Skip to content
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.

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

Build warning for Microsoft.AspNet.TelemetryCorrelation in .NET 6 Project #89

Open
hedronn opened this issue May 26, 2022 · 3 comments
Open

Comments

@hedronn
Copy link

hedronn commented May 26, 2022

Package 'Microsoft.AspNet.TelemetryCorrelation 1.0.8' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework 'net6.0'. This package may not be fully compatible with your project

Is there plans to support .NET 6 for this package??

@knilecrack
Copy link

I have same issue, I don't know if I did something wrong setting up Appinsight or something.

@BobWarren
Copy link

This is also an issue for me with a 6-tier application stack built using Net 5.0.17 ("net50" or "net50-windows"). I get this warning once each time this is built in Azure DevOps build pipelines, for each Razor Class Library and Web application project in our stack. We are not including "Microsoft.AspNet.TelemetryCorrelation" NuGet package anywhere in our app stack so I have to assume this is some other NuGet package that pulls this in as a dependency??
(Also, we cannot upgrade our full environment to Net 6.0 until Microsoft releases the SSIS tools for VS2022, but we did test cloning and updating one group of several projects to Net 6.0 and saw the same warning.)

@knilecrack
Copy link

@BobWarren If those warning are not a problem for you, you can suppress 1701 and 1702 in project settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants