PrimalScript Enterprise - quick in-the-trenches review
Until today, I had a passing familiarity with .xml files. I've seen them. I've tried to interpret them. Once I had to edit one for production; but I had excellent vendor documentation. Notepad was fine.
Today, I was asked to help edit / fix / figure out an .xml file. I had been using PrimalScript Enterprise demo for a few weeks (for editing .vbs/.htm/.asp), and remembered it had an .xml interface. Using PrimalScript to view / edit that .xml file at least allowed us to avoid some stupid human errors, like not closing a section with the </whatever>.
Although we technically didn't succeed (never did get that migcustomapp.xml to work w/USMT3 scanstate/loadstate as we had hoped), having PrimalScript keep us on the straight and narrow with syntax at least prevented us from wasting time testing with a bad .xml
Tomorrow's another day for usmt3 & migcustomapp testing; w/PrimalScript showing it's worth, I believe I can convince the boss to buy licenses for the whole team.