I'm published at MSDN

| 5 Comments | No TrackBacks
This weekend I was completely unplugged, my wife took me away of computers and we drove to Tiberias. No laptop, no internet, just two days of swimming in the Sea of Galilee aka Kineret and fish-eating. It was great. Sea of Galilee

Apparently at the same time my article I was talking about finally made its appearance at XML Extreme Column of MSDN. Here it is: "Producing Multiple Outputs from an XSL Transformation". It's about how to achieve multiple output XSLT in .NET. My first article, so any comments espacially critical ones will be greatly appreciated. Is it well-written or at least clear? Should MultiXmlTextWriter be developed further? I've been thinking about HTML output method, this can be done by creating HTMLTextWriter:XmlWriter, like System.Web.UI.HtmlTextWriter one, but implementing XmlWriter instead. Probably not bad idea.

Related Blog Posts

No TrackBacks

TrackBack URL: http://www.tkachenko.com/cgi-bin/mt-tb.cgi/52


I think adding html output would be extremely useful.

Sounds interesting.

Don't worry.

Recently I took some time measurements between different implementations of the same thing. They were written in a variety of languages -- Python, Java, C, C#, XSLT.

You'd be surprised when these results are published.


Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL

I'm still considering using XSLT to get HTML output. That seems to be way easy, but I'm not sure about performance, anyway it needs to be measured.

Hi Oleg,

Congratulations for your first article on MSDN and for a job well done!

I miss a comparison between your approach and the approach when the different output documents are produced from the global result using a second-step XSLT transformation.

For example, is your method consuming less memory and how much less? Is it faster and how much?

The second method I mentioned can successfully produce HTML and text documents.


Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL

Leave a comment