Comments on: An Alternative to the C# Generic new() Constraint

By: Ade Miller

Ade Miller — Mon, 25 May 2009 15:26:19 +0000

dreamxpert,

You could use this approach. I prefer the inversion of control pattern where EnsureElementExists knows nothing about how to create an instance of T and relies on the delegate.

I’d also we wary of using GetConstructor() as now you’re using reflection which is likely to be slower than calling a delegate.

Ade

By: dreamxpert

dreamxpert — Sat, 23 May 2009 16:51:50 +0000

Why not use this?
(T)typeof(T).GetConstructor(

By: An Alternative to the C# Generic new() Constraint using Lambdas | #2782 - Agile software development, patterns and practices for building Microsoft .NET applications.

Fri, 13 Mar 2009 23:37:04 +0000

[...] long while back I wrote about An alternative to the C# generic new() constraint using anonymous delegates to provide a mechanism for constructing an object which did not support a [...]

By: #2872 » Blog Archive » Windows Live Writer

#2872 » Blog Archive » Windows Live Writer — Wed, 14 Nov 2007 23:20:37 +0000

[...] the WordPress web UI for authoring posts with a lot of code in. You might have noticed that the last attempt at code formatting was somewhat different. I’ve switched to using Windows Live Writer with Steve Dunn’s [...]

By: Ade

Ade — Tue, 13 Nov 2007 17:14:31 +0000

Nice catch Jason,

I’ve updated the code to reduce the constraint on ConstructorDelegate and fixed the if statement.

Ade

By: Jason Bock

Jason Bock — Tue, 13 Nov 2007 16:48:19 +0000

Nifty idea…the only thing I’m wondering about is why you have a where constraint on ConstructorDelegate. It seems like that would overtly constraint your open-ended solution.

And just to be nitpicky…wouldn’t you add the object you just created in your if block so you wouldn’t keep creating it?

Again, good idea – I like this :)