Conclusion

Read trough

Vladekk — Tue, 19 Feb 2008 11:33:39 GMT

I read tutorial till parsing example part, don't have time for this now. I understood almost all of this before, but FP switch is something new to me, had to think on this one a bit.

re: Conclusion

UrosBizjak — Sun, 06 Apr 2008 17:51:26 GMT

Great tutorial. Some of the code is very advanced (at least for me), but you gave some great solutions to problems.

It gives me much better insight into this whole LINQ business.

Thank you.

re: Conclusion

Ryan Riley — Mon, 05 May 2008 22:45:32 GMT

Thanks for this tutorial, Eric. It's very clear and helpful. It took me about 8 hours total go straight through, copying and testing only select code segments. (I'm not certain as to the time, but that's about right; I was looking at some other links for further reference, too.)

The examples you gave were good, too, but I wonder why you would use fp techniques instead of an XSLT transformation since you're using OpenXML. I can certainly see some great benefits to this for generating object transformations.

re: Conclusion

EricWhite — Tue, 06 May 2008 05:48:57 GMT

Hi Ryan,

There are two types of XML transforms, generally speaking: 1) transform a document to some simpler form of XML, and 2) transform a document into a new document (a document centric transform).

For the first type of transform, my experience is that it is far easier to write the transform using LINQ to XML compared to XSLT. I also find the code easier to read. I think that this is only true for developers after getting some level of experience with LINQ.

And there is the issue of performance - some LINQ transforms might perform better than the same transform in XSLT. There are a lot of reasons for this:

- XPath expressions are typically interpreted, whereas LINQ expressions are statically bound.

- no need to fire off a separate process in C# to do the transform.

But this by itself could be a dubious reason, as it is possible to write poorly coded transforms in either language.

For document centric transforms, XSLT works well; to use LINQ, you have to do something like the technique detailed here: http://blogs.msdn.com/ericwhite/archive/2007/07/30/how-to-use-annotations-to-transform-linq-to-xml-trees-in-an-xslt-style.aspx

And that technique, while it would perform well, is a bit abstract.

Sometimes there is an advantage to staying within one language, C# 3.0, instead of coding using a hybrid approach.

I've written a pile of programs to extract data and text from Open XML documents, and I really enjoy using LINQ for those purposes.

You are right, for object transformations, LINQ rocks!

-Eric

Complete Listing of ParseWordML

Eric White's Blog — Fri, 29 Aug 2008 14:32:47 GMT

[Table of Contents] [Next Topic] The following code is attached to this page. using System; using System.Collections.Generic;

re: Conclusion

AD — Sat, 27 Sep 2008 08:06:40 GMT

Currently learning FP at University and I must say that your tutorial helped me a LOT. Thank you for taking the time to write this, much appreciated.

Peace.

re: Conclusion

Wu — Thu, 15 Oct 2009 17:45:44 GMT

Phenomenal tutorial. I found it enlightening and enjoyable. FP has always been a very gray area for me, I never really "got it" or understood how to apply it in a conventional manner. You're tutorial has helped me in both areas.

Cheers!

- Wu

re: Conclusion

EricWhite — Wed, 21 Oct 2009 15:20:04 GMT

Hi Wu, thanks! -Eric

re: Conclusion

KarthikVishnu — Wed, 25 Nov 2009 04:21:11 GMT

Great tutorial. It would be helpful if you write a similar tutorial for Expression Trees.