XNA is No More, as the Phoenix Rises from the Ashes
Join the DZone community and get the full member experience.Join For Free
i personally hate link-baity titles, however this one is completely justified.
we have finally reached the end of an era and the dawn of the next with the monogame project. the latest release has now broken its ties to the old xna framework and stands alone.
no longer is xna required to use monogame
this is an epic milestone as monogame finally realises its dream of journeying beyond the realms of what xna had to offer (some might argue it already did that with all the platforms that monogame supports) and is building capabilities that never existed before in xna. granted this is not a big rush forward but small baby steps inching forward.
everything that has come before
as it stands, monogame implements practically the full set of functionality that xna did, meaning that all your old xna 4.0 projects will be compatible with monogame. there may be one or two little hiccups (this baby is taking its first proud new steps in the world) along the way but it has a proud tradition of hardy developers backing up this project.
did i mention that no one on the monogame team is getting paid for this? it is completely funded by developers free time and effort! you have to respect that.
any contributions to the project go in to the project’s needs, like servers, websites and merchandise!
a brave new world
you might wonder what makes this announcement so special, why all the pomp and circumstance?
the answer is simple, the xna ties have been broken and with that developers can now develop their monogame projects on their platform of choice. with the 3.3 release the platforms you can fully develop on now include:
- windows 7 / 8 / 8.1 (but you knew that already)
- macos (using monodevelop)
now this part isn’t really new, you could do that before, however what you couldn’t do was build all the content needed for your project. prior to 3.3 you needed a windows host somewhere to compile your content. with 3.3 however, you can now do that on all the above platforms, windows is no longer required (but who wants to give up visual studio anyway?)
with the new monogame content builder tool, developers can build content on windows, macos or linux.
there are even new monodevelop (or xamarin studio if you prefer) plugins and templates (thanks to dean ellis of the mg team), so this is now fully supported.
the currently supported list of platforms maintained by monogame as of the 3.3 release include:
- ios (64bit metal only)
- macos (net4, net45, monomac and xamarin.mac)
- windows opengl
- windows directx
- windows 8 / 8.1
- windows phone 8 / 8.1
- windows universal apps (i’ll come back to this)
there is an experimental 3.3 pcl platform release, however this is still a work in progress. there are no issues using it, just be aware some classes / namespaces aren’t recognised. all this means is that some code can’t live in the pcl at the moment but we’re working on this.
monogame also supports most consoles (more in the future) but you need contracts with them before you can even start considering it!. chat to us if you have specific plans and the team can help.
i won’t go in to this too much here as i am planning a series of starter tutorials / videos to help you get going.
to get started you need to install the monogame development templates and tools from:
here you will find:
- monogame 3.3 for visualstudio
- monogame 3.3 binaries for mac
- monogame 3.3 pipeline gui tool package for mac
also (if you prefer) you can also find monogame 3.3 on nuget:
which of course you can also install on top of existing projects to keep up to date.
there are a few pointers about the nuget’s you need to be aware of before installing some of the nugets (any not mentioned are perfectly fine)
- windowsgl – with windowsgl you need to remove the “sdl.dll” from the project before installing the nuget. this is just a conflict that nuget cannot resolve. no worries through, the nuget installs a fresh one for you.
- windows phone 8.0 – because the project template ships with both x86 and arm dlls, nuget isn’t able to uninstall all the references. this causes reference duplication errors. to resolve this you will need to edit your projects .csproj file and remove referenced to monogame.framework before installing (you can do it afterwards, it just makes it more tricky!)
i’ll go over these in more detail in future posts.
an ode to xna
now just because monogame has moved on, cleaned out its room and left the home it once knew, venturing on a brave new adventure, doesn’t mean you still can’t use xna
xna still lives on in many universities across the globe and is still used quite aggressively by developers still publishing (and making money) on the xbox live gaming service for the xbox 360. in fact at a recent game jam (the hull university 3 word game jam http://www.robmiles.com/journal/2015/3/14/three-thing-game-finals ) there were many students building their projects in xna (the majority actually), a few adventurous champions were using monogame plus a few (what i can only call crazy) devs using opengl, matlab and one brave soul doing direct raster drawing.
i have to thank the visionaries at microsoft who dared to dream of a managed game development world, where devs could break their c++ shackles and actually have fun building games, i know i certainly did.
long live xna monogame
are we not dead yet?
i’ve heard various comments around the web thinking because xna is on its way out, so must monogame. or, i’ve not heard from monogame in a long while and there are no updates, are they dead yet?
i can attest to the fact that monogame is a very active project, with lots going on under the hood.
the team have noted that updates have been far and few, this will change following the new 3.3 release. releases will be out quicker, the nuget’s will be updated more frequently and so on.
keep watching this space (and the mg site), more updates should follow on a more regular basis.
where to find out more
there is lots more info out there for monogame and the 3.3 release, here are the highlights:
- monogame main website
- monogame 3.3 on github
- the monogame community site / forum
- the new monogame content builder tool (mgcb gui and mgcb commandline tool)
p.s. i did hear the number of projects that are now published on various stores with monogame recently and i was completely taken aback. the number was considerably larger than i had ever envisaged and i can dream quite big! (sadly ndas prevent me from just saying it ;-( but i wish i could)
i leave this post with a parting thought. you should have noticed that with the 3.3 release, the monogame team officially released a universal app template. this allows you to write one project targeting both windows phone 8.1 and windows 8.1. this was a tremendous achievement for the team to pull this one out of the bag.
you may have also have heard about another company and it’s universal project announcements, so think on that. i personally cannot confirm / deny or vouch for any plans for monogame’s future universal support, however tom spilman of sickhead games, one of the core coordinators of the monogame project, did have this to say recently:
tom spilman i am one of the maintainers of monogame. it does include a universal app template for win8/wp8, but we fully expect to support win10 universal apps as soon as the sdk is available.
so, the dream lives on?
Published at DZone with permission of Simon Jackson, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.