Court of Lord Zoltan v2

I wrote this story a good few years ago now. I've been meaning to put it up for a while now, and only now just got the wherewithall to do so. A mystery of three By Andras Zoltan "Christ", thought Andras, as he sifted through the thousands of papers on the desk "Somewhere here are the words that'll elevate me to the next level, I need to find them, bring them together to make a collage of feelings and ideas; a catastrophe of logic and reason. But where do I start?" The bits of paper all had dark, angular scrawls all over them. On not one of them did any discernable sentence appear. Instead they seemed to have been leaked onto the paper both in the act of writing them as well as dreaming them up, as though a product of a deep trance. As soon as they caught his gaze, the words seemed to fly at him, each one's impact growing from the last; their chaos seeping into his mind as it tried to make sense of what he was seeing. He stared at one of

Before I start – if you’ve found a bunch of other articles about this around the net, tried the fixes that are mentioned and still not getting any joy – then read on – you might find this solves your problem. Earlier today I discovered that when I run any ASP.Net 2 or 4 application through IIS7.5 using the default application pools (which use ApplicationPoolIdentity) on Windows 2008 R2 x64 I get an error message similar to this:   Server Error in '/MvcApplication31' Application. Compilation Error Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. Compiler Error Message: CS0016: Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\mvcapplication31\222b4fe6\4e80a86\App_global.asax.clb4bsnc.dll' -- 'The directory name is invalid. ' Source Error: [No relevant source

I was going to post this as a question over at SO , but as I got to the end I realised a blog would probably be better (apart from the fact that only five people will read it!). The project I'm working uses runtime objects that are produced with configuration-driven delegates built using Expression trees. I'm doing a big functionality merge at the moment and have reached a class that, because of another that has grown, is now obsolete. So I want to make it 'properly' obsolete (generate compiler errors), go through the static codebase and change all the references. The problem is that the class library is used, through Expressions, by a few other apps so I can't yet get rid of the class completely - I'll perhaps look at farming that job off to somebody else. So I thought I'd just check whether the expression compiler honours the ObsoleteAttribute when marked as an error, and it doesn't: [ TestClass ] public class UnitTest1 {      [ Obsolete (