Don't introduce root namespace "Platform"

[c-s-n]

Background
Adding Microsoft.Azure.Amqp NuGet package to an existing project.

Problem
The package introduces a root namespace "Platform" (essentially only Platform.System.Text), which results in some name clashes for us.

Expected behavior
No such root namespace, especially since it feels unneeded.

Either place the System.Text.Encoding wrapping that is done in PlatformSupport.cs somewhere in the Microsoft.Azure.Amqp namespace, or directly use System.Text.Encoding with the corresponding directives.

[virtualcca]

when i reference this nuget
It made An enum or type called platform is incorrect

[Identifier]

This is still causing a problem as of the latest published NuGet package which is still v2.5.12 as of November 10 2022. Specifically, it causes a conflict when importing the package into Unity since Unity's render pipeline has their own enum type named Platform and it conflicts with the Platform.System.Text namespace defined in v2.5.12 of Microsoft.Azure.Amqp. See this Unity issue for reference.

I see this was fixed 4 years ago on November 8 2018 when the PlatformSupport.cs file was removed, but the change doesn't seem to have made it to NuGet yet.

@xinchen10 any idea when the current code will make its way to NuGet?

[MSDNAndi]

I have the same problem. Blocking issue.

[SimonStHilaire]

Same here. I have been able to make it work by building it myself and allowing unsafe code in my project: https://github.com/Azure/azure-amqp

[JT-Bruch]

This is also blocking us as well, our whole codebase is prefixed "Platform" which is going to be a nightmare to unravel.

[taizoon]

Checking to see if there's a release date for this fix. Running into similar namespace conflicts. Thanks.