Using "MonoGame." namespace in nuget id?

If I’m making a NuGet lib for MonoGame projects, should I start the package ID with “MonoGame.” namespace?

On one hand it makes sense, but on the other this is what the official MonoGame releases use, and I don’t want to be misleading. I looked at some non official libs and some do it and some don’t (

So what do you think is the preferred way?

I’d say no because it makes the package seem like an official MG thing.

1 Like

As a compromise I ended up using MonoGame. in the identifier, but with package title of “MonoGame Sprites” (with space, unlike official packages) + I added an icon that is not the MG icon. Looking at it from the gallery, I think its crystal clear that its not an official release.

If there’s any MG team member here that still feel disturb by it, please let me know.

Thanks :slight_smile:

Simply add tags for MonoGame in the NuGet and that should be fine, others like “DeltaEngine” do the same thing.

You can put MonoGame.something in the name if you wish (like MonoGame.Extended :D), however you cannot use the MG logo, which is the MonoGame Branding.

1 Like