<?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>Stylesheet import tree in the XSLT Debugger</title><link>http://blogs.msdn.com/xmlteam/archive/2009/05/19/stylesheet-import-tree-in-the-xslt-debugger.aspx</link><description>Complex XSLT stylesheets often contain several include and/or imports instructions. VS XML Editor has very limited support for such scenarios. (Most noticeable it lacks the concept of "primary stylesheet".) In the XSLT Debugging session you may need to</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Stylesheet import tree in the XSLT Debugger | ASP NET Hosting</title><link>http://blogs.msdn.com/xmlteam/archive/2009/05/19/stylesheet-import-tree-in-the-xslt-debugger.aspx#9631739</link><pubDate>Wed, 20 May 2009 10:16:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9631739</guid><dc:creator>Stylesheet import tree in the XSLT Debugger | ASP NET Hosting</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://asp-net-hosting.simplynetdev.com/stylesheet-import-tree-in-the-xslt-debugger/"&gt;http://asp-net-hosting.simplynetdev.com/stylesheet-import-tree-in-the-xslt-debugger/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Stylesheet import tree in the XSLT Debugger</title><link>http://blogs.msdn.com/xmlteam/archive/2009/05/19/stylesheet-import-tree-in-the-xslt-debugger.aspx#9632422</link><pubDate>Wed, 20 May 2009 18:56:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9632422</guid><dc:creator>Johannes Hansen</dc:creator><description>&lt;p&gt;Hi Sergey,&lt;/p&gt;
&lt;p&gt;Do you know of any reason why this behavior isn't enabled by default. I mean there must be a reason even though it might *just* be, lack of testing.&lt;/p&gt;
</description></item><item><title>re: Stylesheet import tree in the XSLT Debugger</title><link>http://blogs.msdn.com/xmlteam/archive/2009/05/19/stylesheet-import-tree-in-the-xslt-debugger.aspx#9632565</link><pubDate>Wed, 20 May 2009 20:45:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9632565</guid><dc:creator>Sergey Dubinets - MSFT</dc:creator><description>&lt;p&gt;The official reason is luck of time to test the feature. &lt;/p&gt;
&lt;p&gt;Technically there is not a lot to test there. Hierarchy is created with every XSLT Debugger session no matter what. Its primary use resolve paths of locally cached http stylesheets to the original URIs. (PDB doesn’t allow http/ftp paths). The only thing reg key controls is flag __VSADDVPFLAGS.ADDVP_AddToProjectWindow when the hierarchy is added to solution by AddVirtualProject(). &lt;/p&gt;
&lt;p&gt;The same time this is not fully backed feature. We didn’t spend any time thinking about UI (Icons, title, …). The big open question is what to do at design time? We need an analog of Schema Explorer aka XSLT Explorer.&lt;/p&gt;
&lt;p&gt;So don’t afraid to use it.&lt;/p&gt;
</description></item></channel></rss>