<?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>Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx</link><description>Content pipeline importers and processors run inside Visual Studio as part of building your game. This means you can't just debug into them like you would for normal game code. Fortunately, the CLR provides a handy way of hooking a debugger up to any</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#1044153</link><pubDate>Thu, 09 Nov 2006 18:01:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1044153</guid><dc:creator>johnnylightbulb</dc:creator><description>&lt;p&gt;I havn't tried this yet, but will the standard attach-to-process debbuger also work in this case? (If we attach to devenv.exe?)&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#1594963</link><pubDate>Sun, 04 Feb 2007 08:35:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1594963</guid><dc:creator>mikeschuld</dc:creator><description>&lt;p&gt;I get a &amp;quot;No registered JIT debugger was specified.&amp;quot; error. Did I miss something in the setup somewhere?&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#1599149</link><pubDate>Sun, 04 Feb 2007 23:17:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1599149</guid><dc:creator>ShawnHargreaves</dc:creator><description>&lt;p&gt;Interesting - I though the CLR debugger was included with .NET, but I guess it must not be.&lt;/p&gt;
&lt;p&gt;Looks like you can download it from here though: &lt;a rel="nofollow" target="_new" href="http://msdn2.microsoft.com/en-us/library/7zxbks7z"&gt;http://msdn2.microsoft.com/en-us/library/7zxbks7z&lt;/a&gt;(vs.80).aspx&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#2343086</link><pubDate>Mon, 30 Apr 2007 22:09:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2343086</guid><dc:creator>dubbadee</dc:creator><description>&lt;p&gt;This doesn't appear to work with C# Express and the Game Studio. I'm trying to make some modifications to the shader code used in the XNA Animation Component Library at &lt;a rel="nofollow" target="_new" href="http://www.codeplex.com/animationcomponents"&gt;http://www.codeplex.com/animationcomponents&lt;/a&gt;. I've added the line&lt;/p&gt;
&lt;p&gt;System.Diagnostics.Debugger.Launch();&lt;/p&gt;
&lt;p&gt;to the Process() function of PaletteEffectContent.cs, which is part of the custom importer dll. When I rebuild my project which is set to reference that dll, it just builds as normal. Is that expected behavior?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;Derek Hauffe&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#2362317</link><pubDate>Tue, 01 May 2007 23:13:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2362317</guid><dc:creator>dubbadee</dc:creator><description>&lt;p&gt;I've figured out what I was doing wrong. Thanks for this tip, Shawn!&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#2495288</link><pubDate>Wed, 09 May 2007 08:03:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2495288</guid><dc:creator>DarylJReed@hotmail.com</dc:creator><description>&lt;p&gt;This also does not work for me. &amp;nbsp;I've done a clean build, removed then added the content file again, everything I could think of. &amp;nbsp;My debugger line is not getting hit...&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#2531927</link><pubDate>Fri, 11 May 2007 02:19:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2531927</guid><dc:creator>DarylJReed@hotmail.com</dc:creator><description>&lt;p&gt;Just to be complete, the answer was that I am running on Vista, and had elevated the priviledges of VC# Express (run as administrator). &amp;nbsp;If you do this, the JIT Debugger will not even attempt to attach to the process.&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#3114932</link><pubDate>Wed, 06 Jun 2007 14:14:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3114932</guid><dc:creator>duncanf</dc:creator><description>&lt;p&gt;I can't get the debugger to attach using Launch(), it just builds as normal and throws an exception during and outputs that exception in the error list. Am I missing something? Also, I'm trying to use a content processor to calculate normals and write them back into the data stream provided... is this allowed/sensible? This content pipeline stuff seems obscenely fiddly just to do something really simple like get access to mesh data and write out new normals...&lt;/p&gt;
</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#9835431</link><pubDate>Thu, 16 Jul 2009 13:32:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9835431</guid><dc:creator>jbsosch</dc:creator><description>&lt;p&gt;it does not work for me, with GS3.0 and VS2008&lt;/p&gt;</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#9917205</link><pubDate>Wed, 04 Nov 2009 08:20:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9917205</guid><dc:creator>locus</dc:creator><description>&lt;p&gt;does not work for express editions...&lt;/p&gt;</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#9922692</link><pubDate>Sun, 15 Nov 2009 20:29:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9922692</guid><dc:creator>Zakus</dc:creator><description>&lt;p&gt;GS 3.1 &amp;nbsp; VS2008 pro&lt;/p&gt;
&lt;p&gt;work perfectly &lt;/p&gt;</description></item><item><title>re: Debugging the content pipeline</title><link>http://blogs.msdn.com/shawnhar/archive/2006/11/08/debugging-the-content-pipeline.aspx#9928252</link><pubDate>Tue, 24 Nov 2009 21:56:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9928252</guid><dc:creator>Chris</dc:creator><description>&lt;p&gt;GS 3.1 VS2008 works, but Visual Studio always stops responding afterwards and I have to kill the process and restart.&lt;/p&gt;</description></item></channel></rss>