Sergey

Well I could give my boss' usual answer to such questions, "all of them".

My own priorities would be -
Must haves:
  1.     XSLTc (Compiler for XSLT stylesheets, that generates .NET 
assemblies)
  5.     XSLT 2.0 in the XslCompiledTransform
  7.     XPath 2.0 in the Select() methods of XPathNavigator/XmlDocument

Should haves:
  2.     Performance improvements in the XslCompiledTransform
  6.     XSLT 2.0 in the MSXML (Plus signature support and an announcement 
of support etc. for COM XML development)
  8.     XQuery processor in .NET Framework
  11.   Profiling (Ability to profile XSLT execution with VS tools)

Could haves:
  3.     Compilation XSLT to JScript (like AjaXslt)
  4.     Compilation XSLT to C++
  12.   XPath Visualizer/Search (Ability to use XPath in the Find/Replace 
dialog in the XmlEditor) Currently using DonXML's gadget
  14.   Intellisense in XPath expressions in the XmlEditor

Would like:
  9.     Current Node Highlighting (in the source document on each 
XsltDebugger step)
  10.   Data Breakpoints
  13.   Extend expression evaluator in the XsltDebugger with support to XSLT 
functions (document(), key(), :) and script functions
  15.   Stepping through match patterns while evaluating xsl:apply-templates

But ask me tomorrow and my priories may have changed :)

-- 

Joe Fawcett (MVP - XML)

http://joe.fawcett.name


"Sergey Dubinets" <sdub@N...> wrote in message 
news:%23ok9eBouGHA.3364@T......
> In effort to prioritize our goals we composed the list of random features 
> each of them may add value to set of XSLT tools offered from Microsoft.
>
>
>
> 1.       XSLTc (Compiler for XSLT stylesheets, that generates .NET 
> assemblies)
>
> 2.       Performance improvements in the XslCompiledTransform
>
> 3.       Compilation XSLT to JScript (like AjaXslt)
>
> 4.       Compilation XSLT to C++
>
> 5.       XSLT 2.0 in the XslCompiledTransform
>
> 6.       XSLT 2.0 in the MSXML
>
> 7.       XPath 2.0 in the Select() methods of XPathNavigator/XmlDocument
>
> 8.       XQuery processor in .NET Framework
>
>
>
> 9.       Current Node Highlighting (in the source document on each 
> XsltDebugger step)
>
> 10.   Data Breakpoints (Ability to put breakpoints in the source document 
> to break when this node becomes current for any 
> xsl:for-each/xsl:apply-templates instruction)
>
> 11.   Profiling (Ability to profile XSLT execution with VS tools)
>
> 12.   XPath Visualizer/Search (Ability to use XPath in the Find/Replace 
> dialog in the XmlEditor)
>
> 13.   Extend expression evaluator in the XsltDebugger with support to XSLT 
> functions (document(), key(), :) and script functions
>
> 14.   Intellisense in XPath expressions in the XmlEditor
>
> 15.   Stepping through match patterns while evaluating xsl:apply-templates
>
> 16.   Other _________________________
>
>
>
> We'd be happy to hear your opinion. I'll post back the results in two 
> weeks.
>
> Please send your wishes and suggestions to sdub.xslt@m....
>
>
>
> Thanks.
>
> Sergey Dubinets
>
>