test please delete

[voodooflux]

You know you want to.

You know that I know I want to

[voodooflux]

Then a pizza afterwards.

Yes, that could work.

[voodooflux]

Now look what you've done! You've set this bugger off too.

Ooh, you're lucky CM's not here.

She'd paddle you raw!

In my dreams

[zeitghost]

Will anyone read this?

[BrowneIssue]

I saw this last night and was going to reply but thought it better to start today with the following monument unsullied by my poor scrawlings.

In fact, didn't Microsoft make a terrible mistake by producing a Dictionary component intended for use in scripting scenarios such as ASP, but made it apartment-threaded instead of free-threaded, with the result that a load of sample code they'd put out wouldn't work on IIS?

Ah no, my memory is failing me - it was that Eric Lippert (who's a lovely chap, BTW) accidentally marked it as "both" instead of "apartment" (second comment, by Mr Lippert himself) - ASP liked apartment threading

I remember having no end of trouble with an ASP app where we cached some XSLT stuff in Application - I fixed it by using the MSXML2 FreeThreadedDOMDocument, which (if you read the docs, as I ought to have done) was the reason they introduced that

I would supply a link to the relevant docs, but they seem to have broken the MSDN library to an inconceivable extent at the moment...

Ah, found it (via Google - who would've thunk it?) and suffice to say it's an unbelievably obscure thing to spot even in their own documentation

You need to pick out a scarcely-mentioned point on this page (whilst ignoring the fact that the example they claim to be written in JavaScript has the heading "J#", which is of course their own [failed] take on Java, and has as much to do with JavaScript as a car has to do with a carpet) and this page where you need to read a code example and notice the subtle point that it's using the "FreeThreadedDOMDocument" identifier - a fact not called out anywhere else on the page, but without which your attempt to cache an XSLProcessor in the ASP Application object will fail, even though the XSLProcessor itself is perfectly happy there, was designed to live in places like that, and merely needs the support of its original stylesheet document having been a FreeThreadedDOMDocument rather than a mere DOMDocument

Leaky Abstractions in COM? Never...

We're not worthy.

[zeitghost]

the mists of time are clearing. somewhere.

Not around here they're not... can't see the skool at the moment... The Fog, The Fog.... aaaaaaaaaaaaaargh!

[voodooflux]

Will anyone read this?

No.

Or this?

Certainly not.

Didn't think so.

[voodooflux]

Say, is that a bit of unfinished pancake roll?

Not bloody likely!

[BrowneIssue]

Morning drivellers

[voodooflux]

The only thing I find more tedious than football is...

...quiche?