+972 52-548-6969
Did I miss something? Since when can you do it?
time to read 1 min | 24 words
It works :-)
FUTURE POSTS
- Production Postmortem: The Spawn of Denial of Service - 14 hours from now
There are posts all the way to Dec 12, 2023
RECENT SERIES
-
Production postmortem
(51):
24 Jul 2023 - The dog ate my request -
Challenge
(74):
13 Oct 2023 - Fastest node selection metastable error state–answer -
Filtering negative numbers, fast
(4):
15 Sep 2023 - Beating memcpy() -
Recording
(9):
28 Aug 2023 - RavenDB and High Performance with Oren Eini -
Podcast
(4):
21 Jul 2023 - Hansleminutes - All the Performance with RavenDB's Oren Eini
RECENT COMMENTS
-
By Rafal on Challenge: Fastest node selection metastable error state–answer
-
By Syd on Challenge: Fastest node selection metastable error state
-
By Bart Dekker on Challenge: Fastest node selection metastable error state
-
By Ryan Heath on Challenge: Fastest node selection metastable error state
-
By Chris B on Challenge: Fastest node selection metastable error state
Syndication
| Main feed | |
| Comments feed |
Comments
You can use the constructor in this way since .NET 2.0
http://msdn.microsoft.com/en-us/library/c2zzwa6y(VS.80).aspx
And you can set the Current property since at least .NET 1.1
msdn.microsoft.com/.../....web.httpcontext.current(VS.71).aspx
I have actually used this method to test some of my code that relies on the HttpContext being initialized.
Can;t remember how long ago, but I have used something like this - but then stopped doing things like this as I tried to be more "pure" ... aint it amazing what weird things the framework does let you do, when it won't let you do really basic stuff due to paranoia from the FCL team
Comment preview