TFM should be dotnet5.0 instead of net5.0

[TanvirArjel]

We see TFM for .NET 5.0 projects has been updated from netcoreapp5.0 to .net5.0 in preview 3 release but we think TFM dotnet5.0 would be more readable and meaningful which is neither too long nor too short.

.NET Team can consider it.

Thank you.

[huoyaoyuan]

This may be ambiguous with deprecated dotnet50 TFM, which is used by the early development of ASP.NET Core. See https://docs.microsoft.com/en-us/dotnet/standard/frameworks#deprecated-target-frameworks

[jkotas]

This was considered and rejected:

dotnet/designs#92 (comment)
dotnet/designs#92 (comment)

cc @terrajobst

[TanvirArjel]

@jkotas and @huoyaoyuan Thank you so much for the provided links. But I am still not convinced as I have checked the whole list of deprecated TFMs and I found none of them is conflicting dotnet5.0 and so on.

[jpactor]

@jkotas and @huoyaoyuan Thank you so much for the provided links. But I am still not convinced as I have checked the whole list of deprecated TFMs and I found none of them is conflicting dotnet5.0 and so on.

"dotnet5.0" doesn't directly conflict, but there was a TFM, now deprecated, which was "dotnet50". This could lead to confusion as people may leave off the "."