Yves Reynhout's Blog - All Comments

Twitter Trackbacks for MVVM Mediator Deluxe - Yves Reynhout's Blog [asp.net] on Topsy.com

Wed, 07 Oct 2009 00:11:28 GMT

Pingback from Twitter Trackbacks for MVVM Mediator Deluxe - Yves Reynhout's Blog [asp.net] on Topsy.com

re: O/R Mapping - Tools, Libraries & Frameworks

Yachtcharter Griechenland — Wed, 23 Sep 2009 07:11:48 GMT

I was just thinking about Libraries & Frameworks and you've really helped out. Thanks!

re: O/R Mapping - Tools, Libraries & Frameworks

Peter Brunner — Wed, 11 Feb 2009 17:40:20 GMT

Telerik OpenAccess ORM (formerly Vanatec OpenAccess)

http://www.telerik.com/orm

re: Beware of using the ThreadStaticAttribute in an ASP.NET environment

deostroll — Thu, 15 Jan 2009 17:11:56 GMT

Create your own HttpContext class from Brian Bilbro --> the site throws an error. Evidently not your problem, but any similar article out there...?

re: O/R Mapping - Tools, Libraries & Frameworks

Peter Morris — Sat, 29 Nov 2008 16:01:54 GMT

ECO is at www.capableobjects.com - not codegear / embarcadero etc.

re: O/R Mapping - Tools, Libraries & Frameworks

Christian Liensberger — Sat, 29 Nov 2008 09:09:12 GMT

Opf3 is also missing :)

re: O/R Mapping - Tools, Libraries & Frameworks

Pablo — Fri, 28 Nov 2008 03:49:31 GMT

I use schematrix schemacoder.

www.schematrix.com/.../default.aspx

This generate the code clean and easy.

re: Visiting SQL - Part 2

max — Thu, 13 Nov 2008 14:26:20 GMT

hello !

I think it's a good idea, and i am interesting in my studies to see your image called "coreclasses.gif" in this part ...

but the image are not visible! the link is dead maybe :) !

Good luck, bye :) !

re: Beware of using the ThreadStaticAttribute in an ASP.NET environment

wekempf — Fri, 05 Sep 2008 17:23:38 GMT

I'm not going to address the problem you think exists here. Let others do that. But I want to point out your code has several glaring problems.

1. You should never lock a Type object. (msdn.microsoft.com/.../1c9txz50.aspx).

2. The DCL (double-checked lock) pattern is dangerous and rarely needed on .NET. On many platforms, DCL is broken. The .NET VM actually provides for properly using the DCL regardless of the platform the byte code is eventually compiled on, but it requires the use of "volatile" or "MemoryBarrier", which you've not done. For a singleton, however, you can and should just rely on the language semantics of static constructors and not use the DCL (of course, in this case it's not a traditional singleton, but see the next point). (blogs.msdn.com/.../volatile-and-memorybarrier.aspx)

3. In this case, the DCL isn't needed. "_instance" is "ThreadStatic" and can't be accessed by other threads. No synchronization is required for the initialization code.

Beware of using the ThreadStaticAttribute in an ASP.NET environment -

DotNetKicks.com — Thu, 04 Sep 2008 23:29:24 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com