sfeldman.NET - All Comments

Working in Sandbox

sfeldman.NET — Thu, 12 Nov 2009 02:56:07 GMT

As I have already mentioned, I am involved in a project that uses BizTalk 2009. With this beast, you

re: LINQ to XML for Better Maintainability

Bill Sorensen — Mon, 26 Oct 2009 17:25:26 GMT

I think you made the right decision with LINQ to XML. I would seldom even consider using a regular expression to parse XML in a production application. Regex's are a great solution to a particular class of problems; parsing XML/HTML is not in that class. Using a DOM parser as you did will work in every case, even edge cases (nested tags, entities, etc.).

And I've gone down the XSLT rabbit-hole before. While it has its uses, it left me with a complex, difficult to read stylesheet that no one else wanted to maintain.

re: LINQ to XML for Better Maintainability

Sean Feldman — Fri, 23 Oct 2009 13:05:05 GMT

Koen,

Thank you for the suggested option. In case you compare the code snippet I have showed (3 lines) and the code (and I consider XSLT to be a part of code as well), this is already more work. On top of that, now your logic is distributed in code (C#) and XSLT. Planning for future changes when you have even indication that is going to happen is a waste. I try to keep in mind YAGNI principle. When a day comes, and requirements change, I will refactor not only code, but also the design, if needed. Over-designing a simple implementation can have nasty outcomes... KISS is more appropriate in this case.

re: LINQ to XML for Better Maintainability

Koen De Waele — Fri, 23 Oct 2009 10:38:34 GMT

Why not using an xslt sheet for this?

// Load the style sheet.

XslCompiledTransform xslt = new XslCompiledTransform();

xslt.Load("output.xsl");

// Execute the transform and output the results to a file.

xslt.Transform("input.xml", "output.xml");

and with the following xslt (from top of my head, check for errors)

<xsl:template match="/">

<xsl:apply-templates select="Attachment">

</xsl:template>

using an xslt shields your code better from changes in xml formats (and thus makes it more maintainable, even for non-developer types :-)).

<xsl:template match="Attachment">

<xsl:copy-of select="Name">

</xsl:template>

re: Too Loosely Coupled Code – One Year Later

Doug Wagner — Wed, 21 Oct 2009 06:03:08 GMT

Good to hear you are continuing to make progress on this. Always something to learn and so little time.

It is not only a certain level of development that applies but having the context and time to understand. Understanding the business domain, the conventions adopted by the team, etc. apply to the context. I think documentation has seldom helped after the passage of too much time whether it is the code, tests, comments or external.

The key is what helps the current team.

Cheers,

Doug

Twitter Trackbacks for LINQ to XML for Better Maintainability - sfeldman.NET [asp.net] on Topsy.com

Fri, 09 Oct 2009 06:09:14 GMT

Pingback from Twitter Trackbacks for LINQ to XML for Better Maintainability - sfeldman.NET [asp.net] on Topsy.com

Too Loosely Coupled Code – One Year Later

sfeldman.NET — Wed, 07 Oct 2009 03:06:48 GMT

More than a year ago, I have posted a blog entry related to what I was trying to implement in one of

Too Loosely Coupled Code – One Year Later

sfeldman.NET — Wed, 07 Oct 2009 03:01:28 GMT

More than a year ago, I have posted a blog entry related to what I was trying to implement in one of

Too Loosely Coupled Code – One Year Later

sfeldman.NET — Wed, 07 Oct 2009 02:59:35 GMT

More than a year ago, I have posted a blog entry related to what I was trying to implement in one of

re: Consuming ASMX Web Service With WCF

chat — Fri, 02 Oct 2009 20:20:49 GMT

Thank you so much for the information