[quote user="blakeyrat"]I mean I already think Nuget on Windows/Visual Studio is a bad idea[/quote] NuGet is much better because: 1. Package restore (where it downloads packages from the internet at build time) is optional. By default, packages are stored in a local folder, which you can check in to source control 2. Packages are ...

[quote user="levbor"]Why am I the only one who thinks this is TRWTF? [/quote] Why have computers on when they're not being used? That's just a waste of power.

Reminds me of something I'd see on http://www.textfromxcode.com/ :P

Shouldn't the UI be communicating to a business layer, not directly to the DAL? [quote]dependency injection framework such as spring or GIN.[/quote] I'd suggest Google Guice.

[quote]Sometimes you're told that you need permission from $USER to perform an operation, but $USER can't actually enter credentials for you. [/quote] I got this one at work a while ago: Another time, it said I need permission from daniell (my user). The file wasn't locked by any other process, and closing and reopening Explorer ...

[quote user="LoremIpsumDolorSitAmet"] Nice find! So whose build code should be named and shamed?[/quote] It's in Microsoft's "Microsoft.Web.Publishing.Tasks" assembly. [quote]Well, it's better then why my copies of the Windows ISO burner seem to do: Appear to successfully finish only to find that the disk ...

Turns out the build failure was because of a particular task failing but not outputting any errors: Task "CollectFilesinFolder" (TaskId:470) Done executing task "CollectFilesinFolder" -- FAILED. (TaskId:470) I looked at this task in a decompiler and saw that it loads an error message but never actually does anything with ...

A build on the CI box (CruiseControl.NET) was failing but I couldn't see any obvious errors. So I tried building just one of the many web sites and services on my PC and got this: I'm so used to seeing red when builds fail that I didn't even realise it had failed to build.

[quote user="wonkoTheSane"]If the site uses windows auth and/or the share is locked down to certian users then the current user may not be able to access the images, Doing it this way will use the Application pool identity to access the file and pass it back to the client - still more code than is needed, but it does make a bit of ...

Did you take a screenshot? It's gone now but I'm curious as to what was in the stack trace :P Reminds me of when I saw some print_r debugging on one of the biggest news sites in Australia (news.com.au). The University of Sydney one is a lot worse though.