Tamir hates lambdas. He was having a problem with one of his lambda expressions and twittered about it. Around that time I opened my twitter account (yes, Yosi finally convinced me) and offered my help. He wanted to have a single extension method that could iterate over a collection and either change or keep the values it got. …
Blogs / Omer van Kloeten's .NET Zen
View all »
Latest posts
-
A Limitation of Lambda Expressions and Overloaded Extension Methods
http://weblogs.asp.net/okloeten/archive/2008/05/07/6165335.aspx -
Linq to SQL: ChangeConflictException With "WHERE 0 = 1"
http://weblogs.asp.net/okloeten/archive/2008/04/28/6139181.aspxI just finished debugging a very annoying error, where I kept getting a ChangeConflictException with the message "Row not found or changed" while trying to update my data. I found that there were no Member Conflicts in the exception, which seemed really weird to me. …
-
Linq: FirstOrFallback
http://weblogs.asp.net/okloeten/archive/2008/04/23/6123904.aspxSometimes you want to use FirstOrDefault, but the default value of T is a valid value that might get returned. If you used FirstOrDefault, you wouldn't know whether the value that you got is a valid first or the default fallback. …
View all »
124 blog reactions
-
Dew Drop - May 8, 2008
http://www.alvinashcraft.com/2008/05/08/dew-drop-may-8-2008/.NET A Limitation of Lambda Expressions and Overloaded Extension Methods (Omer van Kloeten) Covariance and Contravariance, Part Eleven: To Infinity, but Not Beyond (Eric Lippert) Do You Really Need a Data Access Layer with LINQ? (Jason Young) Introducing Machine.Specifications (or MSpec for Short)
-
The Morning Brew #89
http://blog.cwa.me.uk/2008/05/08/the-morning-brew-89/does, and questions if this should really be a function in its own right. Day-to-day with Subversion - Bil Simser gives the indepth details of day-to-day life with Subversion, covering all the common activities you perform with source code control. A Limitation of Lambda Expressions and Overloaded Extension Methods - Omer van Kloeten highlights a limitation of Lambda expressions (no ref parameters), and shows how overloaded extension methods can work AddIn Enabled Applications - Sacha Barber gives a great introduction into the new System.Addin functionality, with
-
Microsoft Robotics Developer Studio 2008
http://www.dotnetjunkies.com/WebLog/paul/archive/2008/05/05/...Command-Query Separation and Immutable Builders [Via: podwysocki ] Deserializing XML with IronPython [Via: Harry Pierson ] Day-to-day with Subversion [Via: Bil Simser ] Javascript Using JQuery DatePicker in ASP.Net [Via: Chris Brandsma ] LINQ Linq: SequenceSuperset [Via: Omer van Kloeten ] Introducing LINQ To Regex [Via: RoyOsherove ] There Is Always Risk In Portability [Via: scott ] ASP.NET MVC ASP.NET MVC - ActionResult... The Good & Not So Bad [Via: mhawley ]
-
A Limitation of Lambda Expressions and Overloaded Extension Methods
http://weblogs.asp.net/okloeten/archive/2008/05/07/6165335.a...Filed under: Advices, C# Posted to: Joe On ASP.NET by: JoeStagner 05-07-2008 7:55 AM
-
Link Listing - May 6, 2008
http://inq.net/archive/2008/05/07/link-listing---may-6-2008....[Via: podwysocki ] Deserializing XML with IronPython [Via: Harry Pierson ] Day-to-day with Subversion [Via: Bil Simser ] Javascript Using JQuery DatePicker in ASP.Net [Via: Chris Brandsma ] LINQ Linq: SequenceSuperset [Via: Omer van Kloeten ] Introducing LINQ To Regex [Via: RoyOsherove ] There Is Always Risk In Portability [Via: scott ] ASP.NET MVC ASP.NET MVC - ActionResult... The Good & Not So Bad [Via: mhawley ]
-
Foundations of Programming - pt 7 - Addendum
http://codebetter.com/blogs/karlseguin/archive/2008/05/04/fo...registers for an event in ClassB (the event source) a reference is created from ClassB to ClassA. Two solutions exists: de-registering from events when you're done (the IDisposable pattern is the ideal solution), or use the WeakEvent Pattern or a simplified version. Deterministic Finalization Despite the presence of the garbage collector, developers must still take care of managing some of their references. That's because some objects hold on to vital or limited resources, such as file handles or database
-
Foundations of Programming - pt 7 - Addendum
http://codebetter.com/blogs/karlseguin/archive/2008/05/04/fo...registers for an event in ClassB (the event source) a reference is created from ClassB to ClassA. Two solutions exists: de-registering from events when you're done (the IDisposable pattern is the ideal solution), or use the WeakEvent Pattern or a simplified version. Deterministic Finalization Despite the presence of the garbage collector, developers must still take care of managing some of their references. That's because some objects hold on to vital or limited resources, such as file handles or database
-
Foundations of Programming - pt 7 - Addendum
http://codebetter.com/blogs/karlseguin/archive/2008/05/04/fo...registers for an event in ClassB (the event source) a reference is created from ClassB to ClassA. Two solutions exists: de-registering from events when you're done (the IDisposable pattern is the ideal solution), or use the WeakEvent Pattern or a simplified version. Deterministic Finalization Despite the presence of the garbage collector, developers must still take care of managing some of their references. That's because some objects hold on to vital or limited resources, such as file handles or database
-
Foundations of Programming - pt 7 - Addendum
http://codebetter.com/blogs/karlseguin/archive/2008/05/04/fo...registers for an event in ClassB (the event source) a reference is created from ClassB to ClassA. Two solutions exists: de-registering from events when you're done (the IDisposable pattern is the ideal solution), or use the WeakEvent Pattern or a simplified version. Deterministic Finalization Despite the presence of the garbage collector, developers must still take care of managing some of their references. That's because some objects hold on to vital or limited resources, such as file handles or database
-
Foundations of Programming - pt 7 - Addendum
http://codebetter.com/blogs/karlseguin/archive/2008/05/04/fo...registers for an event in ClassB (the event source) a reference is created from ClassB to ClassA. Two solutions exists: de-registering from events when you're done (the IDisposable pattern is the ideal solution), or use the WeakEvent Pattern or a simplified version. Deterministic Finalization Despite the presence of the garbage collector, developers must still take care of managing some of their references. That's because some objects hold on to vital or limited resources, such as file handles or database
Top Tags
What this blog is about
