It’s that wonderful time of the year again. Of course I’m talking about the holiday season, the season to be merry and the season I have no time to do anything else besides work and go to a ton of parties from friends, family and coworkers.
The software I’m working on needs a new authorisation system. The system needs to be prepared for 3 scenarios: to restrict access to a page, to hide part of a page and to block access to data. Let’s solve these problems using claims.
To create a report, I had to combine the contents of several PDFs into one. Thanks to iTextSharp, it’s really easy. Then I had the problem, how do I test this?
Troy Hunt tweeted how a site uses a fake password field so that browsers wouldn’t show the insecure warning. If you want to know the details of this incident, I gladly refer to Troys blog post. In this blog, I want to talk about the deliberate malpractice that goes into this behaviour.
While writing an XML parser I customised, my unit tests all failed with an error message along the lines of “Could not load file ‘C:\Users[username]\AppData\Local\Temp[guid]\Data\test.xml’ or one of its dependencies. The system cannot find the file specified.”.
In the past week, some of my colleagues didn’t understand difference between instance and static methods. They didn’t know why the instance methods couldn’t be called without calling
new and why the static methods couldn’t access instance fields. So if they didn’t know, maybe some of you will find it enlightening as well.
For a few weeks now, I’ve updated the look and feel of this blog. Let me give you a quick explanation why I did this.