Adding to the Mongame Namespace?

Hello,

Was wondering what are the “rules” of using the Monogame Namespace for your project? For instance Monogame.Extended? Is it okay to use Monogame.YourProjectNamespace?

[Edit]
Perhaps I wasn’t clear on what my question was about.
Say I want to make a Utility framework specifically for developers using MonoGame. My Question:

using MonoGame.UtilityFramework;

^ is something like this okay to do?

You will create a library (YourGame.exe) and it will more than likely call from other libraries/assemblies (YourGameEngine.dll).

Inside the code you will see many other Namespaces.

///


///
/// Systems
///
///

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

// // // using System.Diagnostics;

// // // using System.Threading;

// // // using System.IO;
// // // using System.IO.IsolatedStorage;

// // // using System.Xml;
// // // using System.Xml.Linq;
// // // using System.Xml.Serialization;

// // // using System.Net;
// // // using System.Web;

///


///
/// XNA
///
///

using Microsoft.Xna.Framework;
using Microsoft.Xna.Framework.Audio;
using Microsoft.Xna.Framework.Content;
// // // using Microsoft.Xna.Framework.Design;
using Microsoft.Xna.Framework.GamerServices;
using Microsoft.Xna.Framework.Graphics;
// // // using Microsoft.Xna.Framework.Graphics.PackedVector;
using Microsoft.Xna.Framework.Input;
using Microsoft.Xna.Framework.Input.Touch;
using Microsoft.Xna.Framework.Media;
// // // using Microsoft.Xna.Framework.Net;
// // // using Microsoft.Xna.Framework.Storage;

///


///
/// Namespaces
///
///

namespace YourNamespace
{
///
///
/// Class_Basics
///
///

public class Class_Basics
{

///


///
/// Constructors
///
///

public Class_Basics()
{
}

///


///
/// Loads_Values
///
///

public void Loads_Values()
{
}

///


///
/// Loads_Assets
///
///

public void Loads_Assets()
{
}

///


///
/// Updates
///
///

public void Updates()
{
}

///


///
/// Draws
///
///

public void Draws()
{
}
}
}

Yes I understand. My question was more about creating a project using the MonoGame namespace. For instance say I am making a Utility Framework for people using MonoGame to use. And for convince I do not want them to have to add weird using statements. There for putting my Utility Framework Namespace inside the MonoGame namespace.

using MonoGame.UtilityFramework

^ something akin to that

An example of something that already does this is MonoGame.Extended. However, the Extended name tells you that it’s not part of the MonoGame framework itself.

You shouldn’t have a problem doing what you want, but I recommend against using the name unless you make it explicit that your project is not part of the base MonoGame framework. Changing

using MonoGame.UtilityFramework

to

using MonoGame.SpoolUtilityFramework

tells me that the framework isn’t a utility framework part of MonoGame, but an extension.

1 Like

Yes I agree with this. And as of yesterday I decided to not extend the MonoGame namespace for that reason. I think even if I put something in to clearly show that its not a part of MonoGame itself that the possibility of people assuming it is, is not something I would like to do. I decided on a short namespace instead. Just wanted to make sure. Thank you for the input.