Anand Gaurav

Just checking if this is still an issue and being actively looked into? We have been documenting this as a known issue in all our release notes for NuGet releases.

We have been referring this as a known issue in NuGet release notes right from [4.0.0 RTM](https://docs.microsoft.com/en-us/nuget/release-notes/nuget-4.0-rtm) till the last release [4.5.0 RTM](https://docs.microsoft.com/en-us/nuget/release-notes/nuget-4.5-rtm) Do you think we can remove this...

@dtivel @baronfel @clairernovotny please take a look at prior art here: https://youtu.be/FRrslz_AHzE?list=PLdo4fOcmZ0oWiK8r9OkJM3MUUL7_bOT9z&t=460 This is Microsoft owned dotnet tool [Upgrade Assistant](https://learn.microsoft.com/en-us/dotnet/core/porting/upgrade-assistant-overview?WT.mc_id=dotnet-35129-website#upgrade-with-the-cli-tool)

It’s more like the current 95 %ile number for publishing packages till it’s available, should hold. 10 mins is the number I assumed.

Linked the [spec](https://github.com/NuGet/Home/wiki/Flag-vulnerable-packages) from the [Home issue](https://github.com/NuGet/Home/issues/8087), as well.

IMO, the ideal solution would be the first one that means implementing the TFM switcher with the default to all/any TFM. This should be followed by any NuGet work required....

I am not positive. @mishra14 can confirm. If not, how difficult is it to remove TFM filter for NuGet warning suppression (2nd option)? For 15.5?

@davkean, Is this on track for 15.6?

Why does globalpackagesfolder show up here? My understanding was the contents of the contentfiles folder show up in the solution explorer.

I guessed so but this makes the screenshot confusing. Can you clarify the following in the description? - the content file in this case - the layout of the this...