<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Content Pipeline assemblies</title><link>http://blogs.msdn.com/shawnhar/archive/2008/11/24/content-pipeline-assemblies.aspx</link><description>One of the more confusing things for newcomers to the XNA Framework Content Pipeline is figuring out how (and why) to split your code across multiple assemblies. First off, let's examine the flow of data through the pipeline: My choice of colors is not</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Content Pipeline assemblies</title><link>http://blogs.msdn.com/shawnhar/archive/2008/11/24/content-pipeline-assemblies.aspx#9141216</link><pubDate>Tue, 25 Nov 2008 11:54:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9141216</guid><dc:creator>Metalov</dc:creator><description>&lt;p&gt;Hi Shawn,&lt;/p&gt;
&lt;p&gt;Just out of curiosity why did you (read XNA team,i realize I am just asking for an unofficial answer) choose fbx and not collada format?Is it because of commercial reasons or partnership?Or maybe because collada isn't really mature yet?&lt;/p&gt;
</description></item><item><title>re: Content Pipeline assemblies</title><link>http://blogs.msdn.com/shawnhar/archive/2008/11/24/content-pipeline-assemblies.aspx#9142390</link><pubDate>Tue, 25 Nov 2008 20:15:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9142390</guid><dc:creator>ShawnHargreaves</dc:creator><description>&lt;p&gt;We didn't exactly &amp;quot;not&amp;quot; choose Collada format: we understood that there are many interesting formats out there (imagine how cool it would be if you could import directly from .max or .mb files, for instance!) so it was important to design a system that could support many different formats. This is the main reason for the separate importer stage, as this lets people develop importers for many different file formats, but have them all use the same standard object model and processors.&lt;/p&gt;
&lt;p&gt;When it came to which importers we wrote ourselves to ship built in to the product, time was very limited, so we just had to pick whichever we thought would give us the biggest bang for our limited buck.&lt;/p&gt;
</description></item><item><title>re: Content Pipeline assemblies</title><link>http://blogs.msdn.com/shawnhar/archive/2008/11/24/content-pipeline-assemblies.aspx#9147997</link><pubDate>Thu, 27 Nov 2008 23:30:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9147997</guid><dc:creator>nuvem</dc:creator><description>&lt;p&gt;Shawn, is there any other solution to the shared data type problem other than creating duplicate projects? What conflict prevents one from creating a single Xbox project that is also imported into the Windows pipeline extension project?&lt;/p&gt;
</description></item><item><title>re: Content Pipeline assemblies</title><link>http://blogs.msdn.com/shawnhar/archive/2008/11/24/content-pipeline-assemblies.aspx#9148430</link><pubDate>Fri, 28 Nov 2008 01:27:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9148430</guid><dc:creator>ShawnHargreaves</dc:creator><description>&lt;p&gt;&amp;gt; What conflict prevents one from creating a single Xbox project that is also imported into the Windows pipeline extension project?&lt;/p&gt;
&lt;p&gt;You cannot load and use an Xbox project on Windows (or vice versa). Projects are specific to a platform, and can only be used on the platform they were built for.&lt;/p&gt;
&lt;p&gt;Fortunately, creating duplicate projects is trivially easy once you realize that you have to do this, thanks to the cross platform project management features in Game Studio.&lt;/p&gt;
</description></item><item><title>re: Content Pipeline assemblies</title><link>http://blogs.msdn.com/shawnhar/archive/2008/11/24/content-pipeline-assemblies.aspx#9917732</link><pubDate>Thu, 05 Nov 2009 04:26:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9917732</guid><dc:creator>Ari Velazquez</dc:creator><description>&lt;p&gt;Just wanted to say that this diagram and your bullet points have made this entire framework make sense INSTANTLY. You should convince the team to include that image in every new XNA project that Visual Studio builds so everyone can see it right away.&lt;/p&gt;</description></item></channel></rss>