I'm currently conducting a due-diligence review of a technical system. The system is a classic distributed, two-tier system with data held centrally and business-logic delegated to an application tier. I've been asked to perform a security analysis as part of my review. I can't tell you anything about the project itself, for confidentiality (and security) reasons, but I thought I'd share some of the thought processes behind what I've been doing.

A colleague has been asking how to do this and I've found a great post written years ago. I've linked it here...

I've compiled a list of the Technorati tags that I use on this site. Find out more here...

This is just a quick addendum to a colleague's post about using JSON in .NET. Read more for an example and a link to the original post.

Have you ever wanted to change the default namespace of an XmlDocument in .NET. It's not as easy as it might be.

I'm currently reading "Enterprise Architecture as Strategy" by Jeanne W. Ross, et al., published by Harvard Business School Press. I recommend that you obtain a copy and read it if you are interested or involved in enterprise architecture or business IT strategy.

Today I've been talking to some of our developers about generics in C#. As part of it, we worked through an example, the Badger Example, which I've reproduced here for those intrigued!

I've been looking at the C# specification for the new keyword when used on a class member declaration and thought I'd share my findings. If you are a die-hard C# coder then you won't find anything new here, but of course that doesn't mean that you already know it! Maybe it would be better to check...

Have you ever wanted to remove a handler from an event, but haven't had a reference to the object receiving the event, or perhaps you don't even know what type the object has! .NET hides the details of events but with a bit of help from the Reflection classes, you can edit the handlers for your own purposes.

I was recently asked why some expressions didn't seem to be doing what the developer intended. Typically, this was due to the use of the short or byte data types. This post is a brief discussion on the related parts of the C# Language Specification (version 3.0).