It's available in the downloads...
Chris Mankowski
Posts
-
.NET Source.... -
Team Foundation Server vs Visual Source SafeFYI... just in case you decide to use Source Safe 2005 with VS2010 you will need a hotfix: http://code.msdn.microsoft.com/KB976375[^]
-
10 Things Microsoft Can Do to Make a Real Tablet Platform...that way they can get applications for the MSFT-iPad and also for the phone platform as well.
-
Similarities between visual thinkers and liars...I was talking to a few software developers, UML designers, network engineers and I discovered a common trait... when I asked them about a technology or process sometimes they looked up and to the left. TV shows say this is because the person is lying, but why would someone lie about Object inheritance? Then, I came across this link, and it suggests that they are a visual thinker and not necessarily lying... http://www.blifaloo.com/info/lies_eyes.php[^] What do you think?
-
10 ways to suck at programming -
Looking for a crazy Programming Contest: Source code in the form of a shape or art form...I remember once seeing a contest about programmers who had to build a (functional) program in any language where the sourcecode was formatted ASCII art or pattern... where typical all the coding guidelines were thrown out and all that matters is that the code "looks pretty" Has anyone seen this contest before? Are there tools out there to convert my code into functional ASCII art?
-
The death of traditional file names and directories(see subject line)
-
Great; Microsoft reintroduced DLL hell with .NET 2.0 SP1 [modified]It seems you're saying that if you use an overload that only available in 2.0 SP1, you want the compiler to only target that build? Just like you can target 1.0, 1.1, and 2.0? Sounds reasonable, and I would expect that there is a way to do it. I think our definitions of contract is different: Isn't a "contract" between a specific interface/method overload and the caller? Does overloading a method invalidate exsisting contracts? I don't think so, and think that overloading a method between service packs is no worse than adding extension methods. Both are fine to do between releases. Your thoughts?