TLDR: Microsoft MVC has a ‘secret’ backdoor which is not very useful for developers or hackers. Recently I was poking around in the Microsoft MVC codebase trying to figure out how to make my own bundler. While there I came across the following rather peculiar looking code:
Working in software development I am always surprised by how often developers don’t understand the security model of the platforms they work on. In this article I would like to share with you some of the basics of browser security. The topic has a lot of depth but I believe if one understands several fundamental principle […]
A couple days ago I had a fun idea running through my head. What if one could take the standard linq function Concat() and have it “consume” its own output as the input which created the output, a paradoxical call if you will.
This can be represented with the following F# like pseudo-code:
Let y be 1…100
Let x be y.Concat(x)
A couple weeks back I published Jmaxxz.Deet, a software library which brought reference types to the C# language which were guaranteed never to be null. While I maintain that null references are an indication of poor design and should be avoided at all cost, I am forced to admit that Jmaxxz.Deet is not the answer. Over the course of […]
I am happy to introduce Jmaxxz Deet. The Deet assembly contains a single struct, NotNull. This struct provides a mechanism to formally specify that a reference can NEVER be null. This ability is present in both Spec# and Sing#. However, for those of us still making use of VB, C#, F# and other traditional .Net languages still do not have a mechanism to do so. NotNull brings this capability to all of those languages.
Null references have been a part of programing forever, but I dispute the validity of a high level language having Nullable Reference types as the norm. Consider the following examples showing how null references often show up in the real world (right before they crash your application).
I am sure we have all worked with someone at one point or another who takes their job way too seriously. You’ve just written up the most awesomest code ever, but you need to get it through a code review. Unfortunately the guy who does code reviews likes object oriented programing (what a sell out). You know if you hand it to him your code as it is now he will just tell you to rewrite it all and use more classes, more methods, comments on your methods, and better code structure. So how do you get him to give you the thumbs up to check in your code?
Currently I am working on an application where wanted to make use of an IoC. For no particular reason I chose to try Unity, an open source IoC frameworked developed by Microsoft.Due to the lack of meaningful code samples out their I will provide several simple examples of how to use Unity.
The following page contains an excellent set of examples for the Unity IoC framework: http://weblogs.asp.net/podwysocki/archive/2008/03/27/ioc-and-unity-configuration-changes-for-the-better.aspx.