This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I don't know what the question is exactly, but the "trick" seems to be using = instead of ==. That means true is assigned to assertEnabled, and true is the value of the expression. If you didn't pay close attention you might think assertEnabled would be compared to true, and false would be the value of the expression.
Joined: Sep 09, 2012
Thank you .
I understood this after I posted the question.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com