Rename package

[blowdart]

Your package name uses the same naming convention as the official ASP.NET packages. This is already causing confusion on stack overflow.

Please rename everything so they are not under the Microsoft namespace and republish the packages.

[guardrex]

MS Legal is going to have a field day with that one. 😄

[blowdart]

Oh goodness I have no intention of even involving them. I hope for a voluntary rename because if the obvious risk of confusion.

[guardrex]

I was just kidding around. Eventually tho ... eventually ... they'll see it and freak. You've done them a big favor by noting it here. Best to pro-actively fix it before the 🔪 start flying. lol

[SharePointRadi]

Hey guys, no problems, I will get this sorted out.

[blowdart]

Thanks :) I've already seen confusion on stack overflow, which is what lead me here, hehe.

[mxmissile]

2019... package still exists under bad name.

[guardrex]

@mxmissile I'll reach out to the NuGet cats to see about removing (over merely unlisting, which is what everyone normally does).

[0xced]

Hello from 2024. 😂

In the meantime an (official) Microsoft.AspNetCore.Authentication.Negotiate package was released and Configure Windows Authentication in ASP.NET Core explains how to use it.