Talk:Microsoft XNA/Archive 1

Misc
This article reads like a marketing brochure, as though all statements on what XNA is or does were copied directly from Microsoft's promotional materials. I don't see how there can be any degree of neutrality this way.

Can't games targetting the XNA framework be developed in any .NET language? Jmacdonagh 18:14, 22 March 2006 (UTC)


 * Yes, XNA can be used iwth any .NET language, but it requires a bit of hacking, as the installer package integrates into C# Express. It has already been used with Chrome, F#, and Visual Basic.

The article needs an expansion, not just a copy edit. I wish I had enough knowledge to do it myself!!! --Soumyasch 10:18, 22 March 2006 (UTC)
 * Trying to edit. --Soumyasch 10:29, 22 March 2006 (UTC)
 * Done. Please review. --Soumyasch 13:54, 22 March 2006 (UTC)

This article still needs a lot of work. I'll contribute a little. 128.2.161.92 08:03, 15 February 2007 (UTC)

Latest release
Is a beta release, isn't it? --Soumyasch 12:24, 25 March 2006 (UTC)
 * Its March 2006 CTP, updated article accordingly. --Soumyasch 12:27, 25 March 2006 (UTC)


 * CTP? Controled Test Product? - I have NFI On what that means. EDIT - Never mind, I had a look on the wiki, and found what it means. --Amckern 03:59, 26 March 2006 (UTC)
 * For the record, Community Tech Preview for those not introduced in that lingo. ;-) -- Northgrove 21:47, 30 August 2006 (UTC)


 * The version released in December 2006 was officially called 1.0, and XNA exited beta then. There is not yet any official version number for the April 2007 release, but it might be 1.1.

Video support Isssue?
It is true that xna does not include a video support until vista release? ALoopingIcon 05:04, 30 March 2006 (UTC)


 * If I recall correctly, XNA uses Direct3D 10, which is specific to Vista due to the near-complete rewrite of the Windows graphics subsystem and underlying driver model, and is (or will be?) on the Xbox 360 as well. Warrens 17:33, 30 March 2006 (UTC)
 * "XNA Graphics has received a major API overhaul from MDX 1.1, but like MDX, XNA Framework
 * Graphics uses core Direct3D 9 graphics technology." from
 * http://msdn.microsoft.com/directx/xna/migration/ Here you can see what is missing from Beta 1.

Youtube
Youtube has some good links.

Software License Terms and Distribution Restrictions Must Be Transparent
Some users, I presume in an attempt to protect Microsoft or their own personal interest, continue to remove any criticism of the XNA framework. They are making it worse for Microsoft and for themselves. Now I have posted reviews in Amazon.com and reviews will follow. Microsoft's license agreements clearly states that you cannot distributed networked applications or XBox applications, pretty much the only profitable segments in the videogame industry today. Future attempts to hide this heinous licensing agreement will be met with a formal dispute and vandalism reports. here are the licensing agreements:

'''Your statement about Xbox or networked applications being the only profitable releases is quite biased and absolutely wrong. I suggest you do some research''' —Preceding unsigned comment added by 97.101.220.223 (talk) 05:35, 24 August 2008 (UTC)

Licening terms specifically prohibits the distribution of any networked videogame in any platform: "Commercial Networked Programs. In the absence of a specific agreement signed by both you and Microsoft which specifically grants you the rights to develop commercial programs that connect to any network, including Xbox Live and/or Games for Windows Live, you may not use the software to develop commercial programs that connect to any network, including Xbox Live and/or Games for Windows Live." In addition, you may not distribute games outside of the windows platform: "Distribution Restrictions:you may not...distribute Distributable Code to run on a platform other than the Windows platform"

In addition : Can I use the XNA Game Studio Express or XNA Framework to build a commercial Xbox 360 game? A: XNA Game Studio Express lets you create Windows and now Xbox 360 console games much more easily. These games are limited to non-commercial scenarios for 360 titles created with XNA Game Studio Express. However, XNA Game Studio Express may be used to create commercial games which target Windows. We plan to release XNA Game Studio Professional next year which will allow developers to create commercial games for the Xbox 360 in addition to Windows. From : http://msdn2.microsoft.com/fr-fr/directx/aa937793(en-us).aspx —Preceding unsigned comment added by Ml6868 (talk • contribs) 21:08, 7 January 2008 (UTC)

Criticism Section very POV
The criticism section cites nothing and uses weasel words. Once one corrects for these things, there is really nothing of merit left to it. XNA is a system in production, to complain about XNA is to complain about a construction crew not having put walls on the house yet. Give it some freaking time. Although already adopted by a large number of developers worldwide, XNA has not become widely used for its main purpose ; it was supposed to make game programming simpler. It has made game programming simpler. Additionally, this statement is a non sequitur, as it does not elaborate on "XNA's main purpose" or how XNA has failed to acheived it. Perhaps if we had a citation, we would know what the original author intended by this sentence. As it stands, the first portion of the sentence (adoption) is unverifiable, and the second and third portions are vacuously empty. Deleting. However, because it lacks features such as Skeletal animation, code which would seem complicated for a beginner is still required to get things moving. No mention is made of the possible reason for this exlcusion, i.e., the early production status of XNA. If developers express a desire to have a skeletal animation system in XNA, then it's pretty likely Microsoft will include it. This sentence needs to be changed to indicate that lack of features are simply a function of lack of maturity, not some greater flaw in XNA's design itself. Another problem with XNA is that some people say it takes too much control away from the developer, which is why many large game developers choose to directly access the DirectX APIs through a language such as C++. Weasel words (some people say...), and probably untrue. Established developers use C++ because of A) a mature toolchain for work in C++, B) mature assets, including 3D engines that are coded in C++, C) proliferation of C++ knowledge amongst game developlers in general, and D) fear, uncertainty, and doubt of new, untested technologies. Ten years ago, game developers railed against switching to C++ from C, ten years before that they railed against C in favor of to-the-metal assembly coding. There is no loss of control, it is a trading of control from that of the hardware to that of the expression of the game.

Given the cost savings one can have through the rapid application development principles brought to game development by XNA, if more developers had confidence in .NET and C#, XNA would see higher adaption. It's not because of a "lack of control." Control has no meaning, it's bottom dollar profit, and getting games done on time and under-budget increases profits.

Finally, if one were to develop a game in C++/DX that did everything a .NET/XNA game did under-the-hood, they would have similar runtime profiles. C++ is not magically several orders faster than JIT compiled .NET code. Equivalent operations take equivalent processing time, no matter in what language the program was originally written. The problem comes from a misinterpretation of what constitutes an equivalent operation. Garbage Collection and Managed Types are features, features that sometimes get hacked into systems when attempting to compensate for their lack of inclusion in C++. You'll be hard-pressed to find anyone that can code a more performant implementation of GC than what is in .NET.capnmidnight 21:27, 7 March 2007 (UTC)

Good riddance to that section. I didn't like it very much anyway.

Managed DirectX 2.0 Beta Controversy

 * Companies have developed for Managed DirectX.Net 1.0 and 1.1 for years.
 * Near the end of 2005, a beta for 2.0 (2.0 from now on) was released, with no warranties, as usual.
 * This did not stop several companies from starting to develop for 2.0.
 * Six months later, Microsoft declared that they would never release 2.0, but merge much of it into XNA instead.
 * The companies which were developing for 2.0 got the advice to rewrite six months of coding for 1.1, and legally release their program, then rewrite it again for XNA once Microsoft was finished with their new API.

As Managed Directx wasnt going to anywhere, they decided to revitalize it in the form of XNA. Commercial games mostly use Assembly and C/C++, so this decision maybe only affected some "student" or "hobbyist" projects, big deal.

Yes, big deal. Ifor OOP from the ground-up, which (the non-proprietary) C# was. Even uber-coder Carmack has given up on C, and the OOP shows when you play DOOM III.

I guess you mean "professionals in their own eyes"? Not to mention, that significant parts of MDX 2.0 Beta were only "implemented" as stub objects and functions. Those projects, if they existed at all, must have been "close" to completion.

I mean professionals as in people who work full-time on a commercial product. Is there any other kind? I don't know if your use of quotation marks around "close" symbolizes sarcasm, or not, but it doesn't matter much, because I don't see your point anyway. How close they were to completion was irrelevant. What did matter, to them, was that they had just spent several man-years on a deprecated API. I'm not saying those developers are not partially to blame themselves for using a beta API. I'm not saying I dislike Microsoft. In fact, I love MS, and XNA is awesome. In the end, the conversion from DX2beta to XNA that they had to make was much less prohibitive than they anticipated, which was kind of the whole point of rushing the release of XNA. That doesn't mean they weren't miffed at the time, when MS had not yet released the beta of XNA.

Incorrect citation
"XNA Game Studio Express is the IDE for homebrew developers that will be available free of charge during the 2006 Christmas period"

This has nothing to do with the linked article:

Nothing is said about a release date in the cited press release (though I believe this information to be accurate).

Timbatron 04:48, 21 September 2006 (UTC)

y what it stands for?
Microsoft has a history of naming things just because it sounds cool... "Xbox"? What the hell? "Xbox360" What the hell-er. But I like it :D

The [XNA Faq http://msdn.microsoft.com/directx/xna/faq/] just states :
 * Q: What does XNA stand for?
 * A: XNA’s Not Acronymed

Does that really mean XNA expands to XNA’s Not Acronymed, or it was just to say that there was no expansion for XNA? -- soum সৌমো yasch  08:59, 1 December 2006 (UTC)


 * I like the self-referencing acronym explanation better than the latter. Since it's capitalized: "XNA’s Not Acronymed", I would assume it's the former.  Otherwise the answer would be "XNA’s not acronymed." &mdash; Frecklefoot | Talk 15:46, 1 December 2006 (UTC)


 * I believe I heard that it was Cross Platform Next generation Architecture in Looking at XNA Part 1 from Channel 9. Amnesiasoft 01:43, 2 December 2006 (UTC)


 * [Link to Channel 9 vid http://channel9.msdn.com/Showpost.aspx?postid=257928]. Explains that the acronym came first. I suspect the answer XNA's Not Acronymed can be taken as meaning both it is not a valid acronym and it could stand for "XNA's Not Acronymed" on purpose. Sort of a double entendre.(124.152.38.104 06:41, 12 December 2006 (UTC))


 * That's not what Microsoft's web site says. See above. &mdash; Frecklefoot | Talk 10:00, 3 December 2006 (UTC)


 * I too like the self-referencing acronym, but can anyone say "Rip on GNU?" As with most things in the Microsoft world, it's not original. David Mitchell 00:07, 6 December 2006 (UTC)


 * GNU wasn't the first to do it by a long shot. If you're really going to argue "lack of originality" here, you're going to have to date it back further than GNU. --Steven Fisher 01:39, 6 December 2006 (UTC)


 * Just for the record, the name "Xbox" wasn't random. Originally, it was called the DirectXbox ('cause it ran DirectX and this was right after they decided to ditch OpenGL in Win95). This article explains the whole thing a lot better than I can.


 * As far as the acronym goes, I wouldn't be suprised if it orginally was "Cross Platform Next generation Architecture" and then changed it. I can't pick out "indie game development framework" out of that. Why doesn't someone post on the MSDN forums and ask? « S CHLAGWERK  Talk to me! 00:16, 9 December 2006 (UTC)


 * I may be missing the point, but isn't it supposed to be humerous? Since XNA is an acronym that expands "XNA’s Not Acronymed", there is the contridiction that it is both an acronym and not an acronym. It seems to be more of a homage or parody of GNU, HURD, WINE, and LAME, and other "backronyms" common in software. -Hyad 07:55, 22 January 2007 (UTC)

The first thing that springs to mind is, ironically, "Microsoft has sold out". Microsoft's using recursive acronyms now? Gee, before you know it Windows will be open source. :-) Sounds like a cheap way to add some genuine hacker flavor to a Microsoft product. 82.92.119.11 20:45, 4 February 2007 (UTC)

Could not agree more, that bit and the whole article make me wanna puke. Microsoft are quite sly and seem to use wikipedia for free advertising a lot 60.241.89.195 10:55, 15 February 2007 (UTC)

Um, I think that "XNA's Not Acronymed" is a joke (yes, Microsoft make jokes). I believe (though I can't verify) that XNA is a contraction of XBOX and DNA -- sort of the building blocks for XBOX games. To be honest, I think expanding the "acronym" in the introduction to the article looks silly... DeanHarding 08:32, 20 May 2007 (UTC)

Short name history:
 * Direct X = An API that gives Direct Access to the hardware, without using the Windows API as an intermediate. There were complaints of how slow games ran on Windows 95 compared to DOS, and Microsoft had to move game development "with the times" into Windows, to drop DOS.
 * Xbox = Game box using the Direct X API. During development its was called the Direct X Box, but that was too cumbersome to pronounce when release time came.
 * XNA = A Direct X managed wrapper API, to bring game development to managed programming. It is based on a Component model, and the original intent was to make it possible to drag and drop components (building blocks) to create a game, hence the DNA reference seen in early logos. Once released, they came up with a funny explanation, XNA's Not Acronymed.

Oh, and much of Windows has been released as open source, in the form of .Net source code. —Preceding unsigned comment added by 183.89.184.121 (talk) 02:27, 27 May 2010 (UTC)


 * Seems the question isn't in the faq anymore. -- 85.146.52.115 (talk) 09:25, 16 June 2010 (UTC)

No 3D Sound
On a technical note, the lack of 3d sound support in XNA v1.0 and the uselessness of "XACT" make the whole thing a joke. Once you get past the hype (like this article) and try to use this XNA for a real game you start to see what a hack job it is. 60.241.89.195 10:55, 15 February 2007 (UTC)


 * 3D sound will be added in the April 2007 release.

XACT (the audio tool for use in the development of Xbox 360 games) works just fine. Although it requires a small amount of rethinking for seasoned developers, it creates a good way of managing audio within a game. I have used XNA for a while now and it works very well for my purposes. XACT, while required for the Xbox 360 and Zune platforms, is not a requirement. Any other .NET supporting framework may be used in an XNA game for the Windows platform. —Preceding unsigned comment added by 75.70.243.109 (talk) 05:29, 16 November 2008 (UTC)

Advert
I removed the  tag from this article, which was placed by User:204.50.199.4 without comment on 2/12. Looking at the number of different contributors to this article and the content, I do not believe this reads like an advertisement (though it may need cleanup). If you disagree, please comment here before reverting my edit. -- J  Morgan (talk) 14:44, 15 February 2007 (UTC)

Please make certain the XNA page remains factual, and remains free of personal opinions. For instance, statements about XNA not being useful is based on personal experience, opinion and even bias, not fact, since there are people such as myself who do find it useful. Simply state what the XNA Framework can and cannot do. Let the reader reach their own opinion. Instead of a Critisim section, there should be a Pro and Con section for better factual balance.


 * Perhaps the article is not quite an advert, but...it does pretty much exclusively cite Microsoft sources, and some of the language appears to be copied from advertisements. I'm referring specifically to the second sentence of the article, 'XNA does this by freeing game designers from writing "repetitive boilerplate code,"', citing a Microsoft press release. While not exactly advertising, things like these, in my mind, draw the article's neutrality into question. It's rather one-sided, to be frank - it would be good to have a larger variety of sources. I'm not entirely certain how to achieve neutrality, though - with as controversial a company as Microsoft, there will be an abundance of trolling and very little information paydirt. 84.131.135.250 19:44, 3 September 2007 (UTC)

I have gone through this article and removed the sections which were unreferenced and almost certainly advertising. "These tools can ... model characters with life-like dynamism." Sounds more like a buzzword than something worthy of an encyclopedia. "...with minimal effort, and many more. All together, XNA Game Studio 3.0 improves on experiences for both developers and gamers." Says who?

Initial Community Focus Section
The section provides nothing more than the results of a google search, and the phrase "XNA Game Studio Express exited beta status first" makes no sense as there is no context. —Preceding unsigned comment added by 75.82.189.227 (talk • contribs)


 * The phrase does make sense, in the context that the Express version is for the hobbyist community, and it has already been released, as opposed to the Pro version, which is not yet out there. No matter, the entire section is just link spam anyway, so I see no need to reinstate it. In similar spirit, I'm removing the link to 'George's XNA Programming', as is also link spam. I will continue to monitor this page and remove link spam every now and then. —Preceding unsigned comment added by 124.120.188.146 (talk • contribs)

Reason for excluding skeletal animation is wrong
An MS employee has stated that skeletal animation will never be included in the framework because of negative feedback from the directx animation framework. I'll dig up the reference sometime and post it. Also, an official skinning sample has been released, as well as a community animation library, so that incorrect statement should be removed. People should know better than to give their own, unresearched opinions on topics in an encyclopedia.

Mobile
Is there any hint that this sort of thing is being worked on for the .NET Mobile Profile? Mathiastck 05:57, 24 May 2007 (UTC)
 * Yeah, I came here expecting to learn something about how XNA is suppposed to have something to do with Windows Phone 7 Series development (and Zune?), but I am still left in the dark. Jason404 (talk) 03:32, 9 March 2010 (UTC)

C# and Visual Studio only? Not so much
Despite what the XNA FAQ says, it is very possible to build an XNA game using languages other than C#, and IDEs other than Visual Studio, to make XNA games. I'm currently working on a game in the Boo language, and using SharpDevelop. It has taken a bit of work but it absolutely will build and run. I suspect any .NET based language and any IDE or compiler will work.


 * I agree the sentance under XNA Framework that says "Currently, games that run on the framework must be written in C# using the XNA Game Studio Express IDE." should probably be removed. It's certainly not true (as you say) and it's not really implied by the linked FAQ, either. The FAQ mentions C# with regards to the framework, and Game Studio Express is built around C# but there's nothing there that says you need to use Game Studio Express to write games against the framework. If no one has objections, I'll update the text to reflect this. DeanHarding 05:07, 19 June 2007 (UTC)
 * Technically, as long as the libraries are available for linking, any .NET compliant compiler and IDE will work by C# and Game Studio is the only officially supported way. --soum talk 07:44, 19 June 2007 (UTC)
 * But where does it say C# + Game Studio are the only offically supported way? Of course they encourage you to use them, but the citation after that sentence certainly doesn't imply that C# + Game Studio is the only supported to write games. Besides, the way that sentence is worded, it says that C# + Game Studio are the only way, not the only supported way. I'm going to rewrite the sentence a little but I think I'll need some actual citation that says C# + Game Studio is the only officially supported way to write games using XNA. DeanHarding 23:25, 20 June 2007 (UTC)

Microsoft Surface Computer
XNA is also used for much of the software written for Microsofts new Surface computer coming out soon —Preceding unsigned comment added by 208.124.36.198 (talk) 02:00, 2 October 2007 (UTC)

==

XNA vx XNA Framework vs XNA Game Studio Express
This whole article is perpetuating the myth that XNA is mostly about XNA Game Studio/Framework. Microsoft did a pretty bad job of explaining everything but Microsoft XNA is the brand that covers all of the game development technologies from Microsoft including DirectX.

I would like to propose that most of this article is moved to a new article called XNA Game Studio (the next release of game studio drops the 'express' tag. Then redirects from XNA Framework and XNA Game Studio Express will point to the XNA Game Studio article. This article will explain the overall marketing name and link out to the products that are part of it - well those big enough or established enough to have their own entries. XNA Build and XNA Team System were proposed or rumoured products which never released so will stay with the header article. --Thezbuffer 23:42, 24 October 2007 (UTC)
 * XNA might have been conceived as an umbrella brand for everything graphics related. But of late I have not seen anything but xna framework/game studio referred to by this brand. So, how about mentioning the historical perspective in a history section? How about this layout:


 * 1) Intro
 * 2) Overview (for explanation of the focus of the brand)
 * 3) Components
 * 4) XNA Framework
 * 5) XNA Game Studio
 * 6) XNA Content Pipeline
 * 7) Creator's Club (or whatever it is)
 * 8) History
 * 9) Criticism


 * Since the xna fs/game studio sections doesn't currently have much content, there is no need to split out right now. Once it grows, we can fork out any time. --soum talk 04:40, 25 October 2007 (UTC)
 * XNA GS/Framework gets the majority of publicity becuase of the fact that its targetting mass market developers whereas DirectX, XBLA, XBox etc are in general used by professional game developers only. So this gives the skewed view that GSE is all that XNA is about. Plus there has been so much misinformation that google searches and magazines are using the wrong names to refer to the products. Most of the teams within Microsoft gaming group are now called XNA {something} even if they are not to do with XNA Framework. Here's an example - the XNA Live server team http://www.randyrants.com/2007/10/xna_live_server.html.
 * But I see your point on a lack of content - at least not enough to split it out. I'll wait for your response and then have a shot at reorganizing the page.--Thezbuffer 20:48, 25 October 2007 (UTC)
 * Cool. But I would suggest a monolithic article, for now. With sections for all current known components and promotions (framework, game studio, creator's club, this live server thingy et al). The overall brand may be explained in the overview section and historical perspective in history section. Once this is in place, forking out large sections (if needed) wouldn't be too hard. All the best with the rewrite. --soum talk 05:15, 26 October 2007 (UTC)

I feel this issue should be revisited. It's been years later and this really should be corrected to have accuracy. Since this discussion, Microsoft has released XNA branded Xbox dev kits which are intended for native, C++ XDK developers. While Microsoft may not be doing a good job of publicizing and separating "XNA" from "XNA Game Studio", they are using the XNA brand on products other than XNA Game Studio and the XNA Creator's Club. If nothing else, having the page explain that XNA is an umbrella brand before diving into each individual topic, but I feel that moving all XNA Game Studio content to a new XNA Game Studio page would benefit readers, leaving the XNA page to explain the branding and include brief overviews of the components of XNA - of which the primary ones are DirectX, the Xbox XDK, and XNA Game Studio. —Preceding unsigned comment added by 67.183.143.213 (talk) 03:27, 26 July 2009 (UTC)

Should this article mention???
Should there be a mention of the fact that XNA's EULA says that unless you pay a licensing fee, Microsoft owns anything you create with XNA and you have to distribute the source with the game? This is not me having a moan, I don't think that Microsoft are being that unreasonable - it costs money for any company to buy dev tools for a console. I just think this fact should be in the article somewhere. I'm not sure whether or not this is the same as the Creator's Club mentioned, which doesn't say anything about distribution of source. 123.243.99.2 07:40, 11 November 2007 (UTC)

I was just reading the EULA for XNA 2.0 and can't find anything to do with having to distribute your source. I think you misread it; they seem to be saying they own XNA, not anything you make with it. In addition, is seems the licensing fee applies only to deploying your games on an Xbox360. Elkenny (talk) 21:33, 18 December 2007 (UTC)

Licensing conditions aren't necessarily notable, so that section shouldn't be in the article. I'm sure the infobar has a parameter for license type anyway. L337 kybldmstr (talk) 00:31, 27 March 2008 (UTC)

Fair use rationale for Image:Xnalogo.PNG
Image:Xnalogo.PNG is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.

BetacommandBot (talk) 08:34, 15 January 2008 (UTC)

XNA GS 3.0 and XNA Live Community Games
The article needs to be updated now. --soum talk 06:47, 21 February 2008 (UTC)

I've made a quick update, but there's much more to do. 72.253.129.13 (talk) 05:15, 26 July 2008 (UTC)

List of released games using this toolkit
As per the list of WPF apps, would it be possible to have a sample list of released games that use this toolkit? Naelphin (talk) 13:29, 28 February 2008 (UTC)

Bloody trapland is a game that uses XNA, seen in the files of the game and a beta video of the game clearly stating that it uses XNA Rando339 (talk) 18:17, 21 June 2022 (UTC)

Starter kits
"...for rapid development of specific genres of games, such as platform, real-time strategy, and first-person shooters."

In the XNA content catalog I see an RPG, a 2D multiplayer space shooter, a tunnel shooter, a racing game and a puzzle game. No real-time strategy, platform or first-person shooters whatsoever. And that blows. I've been looking for good platform game boilerplate. --Kawachan (talk) 18:41, 20 May 2008 (UTC)

Bot report : Found duplicate references !
In the last revision I edited, I found duplicate named references, i.e. references sharing the same name, but not having the same content. Please check them, as I am not able to fix them automatically :) DumZiBoT (talk) 09:29, 9 August 2008 (UTC)
 * "xnafaq" :
 * Microsoft XNA Frequently Asked Questions
 * Microsoft XNA Frequently Asked Questions

XNA With GNU?!
It seems that XNA is using the GNU method of naming. Does anyone notice these similarities?
 * GNU = GNU's Not Unix
 * XNA = XNA's Not Acronymed
 * Bwoah, they do it all the time -- EINE Is Not Emacs, ZWEI Was Eine Initially, PHP Hypertext Preprocessor... it's just that until now, "they" did not include Microsoft. Guess they just wanted to "be like the cool kids". --Kawachan (talk) 13:07, 4 September 2008 (UTC)
 * They are called recursive acronyms. TWAIN- "Technology Without An Interesting Name", is another good one (although not recursive). Jason404 (talk) 03:37, 9 March 2010 (UTC)

List of games
I think it is desirable to list all the games made using this computer language. —Preceding unsigned comment added by 81.106.37.243 (talk) 00:46, 25 August 2008 (UTC)

XNA acronym
Wasn't the real acronym - a recursive acronym: XNA's not acronym? Or did they change it? —Preceding unsigned comment added by 77.127.204.98 (talk) 15:39, 27 August 2008 (UTC)

75.152.128.207 (talk) 06:05, 24 August 2008 (UTC)
 * XNA’s Not Acronymed. Says so right there. --Kawachan (talk) 13:09, 4 September 2008 (UTC)

I always assumed the acronym XNA was a combination of X (from DirectX/XBox) and DNA a precursor to .Net. (I think Microsoft chose the name for DNA for the obvious connotations but said it stood for something like Distributed Network Architecture.) —Preceding unsigned comment added by 203.206.172.126 (talk) 02:42, 20 January 2010 (UTC)

Prices
I know that the Express version is free, but what about 3.0? Could someone add in the price for the other versions? 65.2.40.49 (talk) 16:38, 25 February 2009 (UTC)


 * There all free. --72.39.60.67 (talk) 12:53, 30 March 2009 (UTC)

XNA Framework Content Pipeline
As of September 2009, this paragraph is the most clueless, random thing I have read on Wikipedia. It doesn't say what is the Content Pipeline. No, it's not a set of tools. I suggest someone knowing what he's writing about redo that whole section, which is by far the worst of this article. Meanwhile I'm removing the section as what it says is, for anyone one knowing the XNA framework and what is the content pipeline, utter randomness. Here's a copy of what is was:

"XNA Framework Content Pipeline The XNA Framework Content Pipeline is a set of tools that allows Visual Studio and XNA Studio "as the key design point around organizing and consuming 3D content". [6][13] This means that XNA Game Studio can still be used to develop commercial games and other programs for the Windows platform, although Microsoft's networking support code for Xbox/Windows Live cannot be used. Self-developed network code can still be used inside your XNA project. Games created using XNA Game studio may now be distributed via Xbox Live Community Games. The software may also be used to create commercial games which target Windows."

While reading this, if you didn't laugh out loud, I suspect you don't know more about the Content Pipeline more than the original author of this section. I give the benefice of the doubt and will guess that it was written at a time where Microsoft marketing department itself wasn't even sure what was the Content Pipeline. --WhereIsMarty (talk) 19:02, 3 September 2009 (UTC)

I realized that the Licensing section was weirdly merged with the Content pipeline section because of a badly formed tag. I fixed it and now the Content pipeline is only abstract, not worth deleting. --WhereIsMarty (talk) 19:14, 3 September 2009 (UTC)

XNA's Not Acronymed - WINE Is Not An Emulator
Doesn't this hint at WINE actually being an emulator?--129.13.72.197 (talk) 21:56, 17 November 2009 (UTC)
 * No; recursive acronyms have always been a running joke in the programming community (eg, LAME Ain't an MP3 Encoder, PHP: Hypertext Processor, etc) 121.223.243.95 (talk) 15:20, 4 January 2010 (UTC)

Windows mobile and new site instead of creators.xna.org
wikipedia hasn't caught up with new marketplace and developer site for XNA games (xbox+windows mobile) at MSDN? —Preceding unsigned comment added by 79.103.21.158 (talk) 23:24, 18 October 2010 (UTC)
 * It just came out so it's currently in progress. Washington Irving Esquire (talk) 23:55, 18 October 2010 (UTC)

XNA Means....
XNA = Xbox Networking Access — Preceding unsigned comment added by 74.99.64.251 (talk) 01:34, 12 July 2011 (UTC)

NOPE, the XNA team had written in blog post in the past that XNA is not an acronym — Preceding unsigned comment added by 150.140.47.63 (talk) 15:24, 11 October 2014 (UTC)