![intentions broken resharper 9 intentions broken resharper 9](https://image.slidesharecdn.com/resharperfornugs-110131023741-phpapp02/95/resharper-presentation-for-nugs-9-728.jpg)
Thus, the XSLT parser will wrap them itself. The answer to this is not to include the CDATA block ourselves, but to tell the XSLT document which elements need to contain the CDATA block, instead. If you just add the CDATA block to your XSLT a standard parser will take the XSL element within it as to be ignored, and not process it. Unfortunately, the CDATA block tells the parser not to parse the content within it, so what we actually end up with is: What the CDATA block does is tell any parsers that the content is to be, essentially, ignored. Wrap the body content of the elements we want to remain as body content in a CDATA tag, like this: So, we want to keep this 'inner XML' as it is (ie: pretty XML and not escaped) but indicate that it's not part of the current XML document. We now have XML containing some more XML, which should really be considered plain text, until it's needed. If you want to do that for specific elements only, just move the 'value-of' XSL element to where you want it.
#Intentions broken resharper 9 code
What this does is match every element named 'Description' in the original XML and unescape it's content - so code like < and > become.Unescaping the code, in XSLT, is a little tricky, but if you assume every element which needs unescaping is the same, then we can do this: Ok, so, in summary, we have valid XML with escaped XML (or XHTML) which needs to be wrapped sensibly so it's not mixed up and we need to do this in. So now I need to unescape it back into normal HTML, so it can be rendered on a page without hassle, but without making it part of the XML document. Of course, using SQLXML to pull this out I find that the body of some of the elements contains this escaped HTML. Some of this XHTML is broken because the writer was probably using a rich-text editor which sent fragments of XHTML to the database.
#Intentions broken resharper 9 software
They lose the shine off their passion for development, becoming bigots or hypocrites that believe they could build it better, faster, stronger if it were up to them but the software is the way it is because of someone else.I have a T-SQL table of data, one field of which contains escaped X/HTML - that is, it has XHTML where the important characters, like, are represented as < and > etc.Unfortunately, all too soon they become “experienced” developers. They know the whole of the system is bigger than they can accomplish alone, and provided that they are mentored in best practices (School is little-to-no help there) they make for some excellent development tallent. Their minds are like sponges and most of them have a passion to be responsible for building something. This is one reason I like graduate developers.
![intentions broken resharper 9 intentions broken resharper 9](https://devblogs.microsoft.com/visualstudio/wp-content/uploads/sites/4/2020/12/169P2NETProd4.png)
If they don’t get the green field, they move on. They want, they’ve “earned” greenfield status. “Veteran” developers would never willingly remain on the “legacy” project. Management wants to squeeze every penny out of the existing product so that means more enhancements and customizations to “just get sales” ot provide cash flow or prop up investment into a new and improved version. What’s left of the original development team starts beating drums for a new version of the product using the “now” modern technologies (C#, ASP.Net 3.5, etc.) while greenhorns are left to maintain the old beast.
![intentions broken resharper 9 intentions broken resharper 9](https://ssl-static.libsyn.com/p/assets/1/5/9/b/159b5c314843f862/TLPR_Logo_Standard.jpg)
(VB6, C++, ASP, ASP.Net 1.1)Īfter the product is released to the world and starts going through the “fermenting” stages (bug fixes, enhancements, customizations) the ball of mud is forming. The initial development team starts out with the best intentions, and the best “current” skills, knowledge, and technology they have in their posession at the time. Economics & general attitude of the development team.