A common immutability practice is to simply protect the property setter with an immutability flag. Take a simple class that has a single integer field for to back our property and a single boolean flag to mark it immutable. using System; public class SimplyImmutable { private int field1 = 0; private...

I've seen this happen quite often. When developers create their immutable types, they assume the only view the user will ever have is of the type through some interface. Normally the interfaces are defined before-hand and included in some library that the user is supposed to link to. This can easily...

I figured I'd start with the obvious. You can never control a machine 100%, so there is always the opportunity that whatever systems of protection you have in place, they can be overcome. This same principle applies to security and cheating systems as well. Things start to become mutable in .NET under...

Brad Abrams posts an article on Mutable reference types should not be read-only fields . You really have to think about what this means. In the example he creates a new type, say F, that has some internal data. On another type, he creates a read-only field of type F. He then demonstrates, how you can...

Doing a PermitOnly when using File Permissions seems to be the way to lock down file access in the .NET environment. It ensures that the API you are calling can only access the specified file path and often times this can be important unless you trust the library you are calling (I try not to trust any...

A common immutability practice is to simply protect the property setter with an immutability flag. Take a simple class that has a single integer field for to back our property and a single boolean flag to mark it immutable. using System; public class SimplyImmutable { private int field1 = 0; private...

I've seen this happen quite often. When developers create their immutable types, they assume the only view the user will ever have is of the type through some interface. Normally the interfaces are defined before-hand and included in some library that the user is supposed to link to. This can easily...

I figured I'd start with the obvious. You can never control a machine 100%, so there is always the opportunity that whatever systems of protection you have in place, they can be overcome. This same principle applies to security and cheating systems as well. Things start to become mutable in .NET under...

Brad Abrams posts an article on Mutable reference types should not be read-only fields . You really have to think about what this means. In the example he creates a new type, say F, that has some internal data. On another type, he creates a read-only field of type F. He then demonstrates, how you can...

Doing a PermitOnly when using File Permissions seems to be the way to lock down file access in the .NET environment. It ensures that the API you are calling can only access the specified file path and often times this can be important unless you trust the library you are calling (I try not to trust any...