Xslt 1.0 has a number of issues that can make the life of an Xml developer frustrating. A lot of them are addressed by Xslt 2.0. Unfortunately the .NET Framework does not have an Xslt 2.0 compliant processor. Fortunately most of the biggest Xslt 1.0 pain...

There is a few Xml APIs you should not be using. In some cases the complier makes this obvious – the API is marked as obsolete and you will get a warning when compiling an application that uses any of these APIs. All the obsolete APIs have their replacements...

So, your application is crashing and it is crashing in the bad way. After spending hours of debugging and trying different things you figured out that this is this Xslt stylesheet that causes all the problems. How come? XslCompiledTransform is a compiler...

Xml is ubiquitous. No doubt about it. It is being used almost everywhere and almost by everyone. This includes places where huge amounts of data are being processed. This means xml files (or streams) used there are also huge. And the bigger the Xml file...

“XslCompiledTransform is fast.” “Really?” “Yeah, XslCompiledTransform is fast… if used correctly.” Indeed, depending on how you use XslCompiledTransform API your transformations can be really fast or not-that-fast (to say the least). The key to understanding...

XPath expressions are pretty flexible. This flexibility allows for very creative ways of using XPath. Unfortunately some of them are suboptimal and cause bad performance of apps. This is especially visible in Xslt transformations where stylesheets contains...

This is the first part of a mini-series of blog posts about using Xml on .NET Framework platform in an effective way. Although I will be focusing on .NET Framework platform I hope that at least some of the information will be general enough to apply to...

Windows 7 Windows Server 2008 R2 Windows Vista (All SPs) Windows Server 2008 (All SPs) Windows XP SP3 Windows XP SP2 Windows Server 2003 (All Versions) In-Band In-Band In-Band In-Band In-Band OOB 07/13/2010: End-of-Support OOB   (Update - This blog...

This document gives an overview of how the Visual Studio editor choosing system works, and as an example discusses the XML Editor’s choosing system. Visual Studio has the ability to associate multiple editors with a single a file extension. For instance, .xaml files have multiple editor implementations associated with them. This raises the question of how Visual Studio chooses a specific editor implementation when asked to open a file. his document gives an overview of how the Visual Studio editor choosing system works. Below, we discuss how Visual Studio decides which editor to open for a file extension; we review the IVsEditorFactoryChooser interface that further advances the choosing mechanism, and the Visual Studio XML Editor’s implementation of this interface: XmlChooser....

This is a friendly reminder that MSXML4.0 SP2 is going out-of-support on 4/13/2010. Applications using MSXML4.0 should be either migrated to MSXML6.0 or upgraded to MSXML 4.0 SP3 . For more information about the Microsoft Support Lifecycle Policy, please...

We have recently blogged about the new XML Schema Designer and the various views over schemas offered by it. We visit here the concept of schema sets, which are actually the central organizing concept around what is shown in the designer for a buffer...

We are happy to announce that we are releasing the sources for LINQ to XSD on CodePlex at http://linqtoxsd.codeplex.com . LINQ to XSD allows you to program with strongly-typed classes based on an XSD schema and was previously released on MSDN as an alpha...

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...

I've written in the past about XML and languages, and why you might be interested in being aware of the language associated with text. Text with no language is just not quite there Impact of text language on WPF Text, language and sorting For dealing...

Here's a good word of warning: even if an object "feels" read-only because you're not calling code to modify it, if it's not documented as safe for use from multiple threads, then you shouldn't risk it. As an example, let’s look at XmlSchema and XmlSchemaSet...

Converting from XmlDocument to XDocument has a number of benefits, including the ability to use LINQ to XML, use a much cleaner object model, get better name handling with XName and being able to use functional constructors. However, there are a lot of...

Under certain conditions opening Web projects from remote sites may become very slow. We've seen quite a few 'hang' reports submitted via 'Send Information to Microsoft' feedback (aka Dr. Watson ). The reason is that sometimes XML editor (which is used...

Today, we officially released MSXML4.0 Service Pack 3 (SP3) on the Microsoft Download Center as a stand-alone installer in multiple languages. MSXML4.0 SP3 is a complete replacement of MSXML4.0, MSXML4.0 SP1 and MSXML4.0 SP2 and contains a number of...

The new XML Schema Designer (see this previous blog post for a d/l location to the CTP) offers four views over XML Schema Sets: XML Schema Explorer , Graph View , Content Model View, and Start View. This entry will focus on the Content Model View. The...

In certain scenarios, it is important to be able to compare two XML trees for equivalence. For example, if you are writing a web service that serves results of queries, and you want to cache query results so that duplicate queries use previously cached...

The new XML Schema Designer (see this previous blog post for a d/l location to the CTP) offers four views over XML Schema Sets: XML Schema Explorer , Graph View, Content Model View , and Start View.  This entry will focus on the Graph View. ...

The MSXML Team is pleased to announce that MSXML 4.0 Service Pack 3 (SP3) Beta is available for public testing. This new service pack includes a number of security bug fixes as well as reliability improvements. MSXML4 SP3 is a complete replacement of...

The MSXML Team is getting ready to release the MSXML 4.0 Service Pack 3 Beta very soon! MSXML4 SP3 is a complete replacement of previous MSXML 4.0 service packs. The new service pack includes: - A number of security bug fixes - Reliability improvements...

In the Orcas SP1 release we released our XML Schema Explorer .  In the Visual tudio 10 PDC VPC we shipped our first rev of the next set of planned features for our XML Schema Designer.  Check out the Visual Studio 2010 and .NET Framework 4.0...

Beth Massi and Yang Xiao did a great Channel 9 session that centered on XML Literals and the XML Schema Explorer. Check the session out here . One thing that doesn’t come across in the video is that the Explorer can be used with any XSD set, not just...