<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>clinq Release Rss Feed</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx</link><description>clinq Release Rss Description</description><item><title>Created Release: CLINQ 2.2.0.1 (Feb 05, 2010)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=39989</link><description>&lt;div class="wikidoc"&gt;Small update to fix bug in SelectMany&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>akutruff</author><pubDate>Fri, 05 Feb 2010 14:30:38 GMT</pubDate><guid isPermaLink="false">Created Release: CLINQ 2.2.0.1 (Feb 05, 2010) 20100205023038P</guid></item><item><title>Released: CLINQ 2.2.0.1 (Feb 05, 2010)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=39989</link><description>&lt;div&gt;Small update to fix bug in SelectMany&lt;/div&gt;&lt;div&gt;&lt;/div&gt;</description><author></author><pubDate>Fri, 05 Feb 2010 14:30:38 GMT</pubDate><guid isPermaLink="false">Released: CLINQ 2.2.0.1 (Feb 05, 2010) 20100205023038P</guid></item><item><title>Updated Release: ContinuousLinq 2.2.0.0 (Jan 06, 2010)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38322</link><description>&lt;div class="wikidoc"&gt;This is a pretty big release....
&lt;h4&gt;Significant performance improvements&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;Weak event system overhaul&lt;/li&gt;
&lt;li&gt;Implement INotifyPropertyChanging on the objects in your source collections to get most benefit.  However this is not required.  Only implementing INotifyPropertyChanged is still fine, but you will gain little performance improvement.&lt;/li&gt;&lt;/ul&gt;

&lt;h4&gt;Reactive Programming support:  ReactiveObject&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;Allows you to make a reactive and event driven object model for amazingly decoupled Models, ViewModels/Presenters.  &lt;/li&gt;
&lt;li&gt;Founded on INotifyPropertyChanged/INotifyPropertyChanging rather than requiring the user to rely on first class events.&lt;/li&gt;
&lt;li&gt;Highly optimized core that can observe changes on any object implementing INotifyPropertyChanged, and has extremely low overhead.&lt;/li&gt;
&lt;li&gt;See &lt;a href="http://kutruff.wordpress.com/2009/07/14/reactive-programming-in-c-reactiveobject/" class="externalLink"&gt;Andy Kutruff&amp;#39;s blog post on ReactiveObject&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Batch update support:  If you use AddRange when adding to the source of query, it will reduce the amount of NotifyCollectionChanged events.  This is huge for query outputs that are bound to WPF ItemsControls as the UI will only need to update once.&lt;/li&gt;&lt;/ul&gt;

&lt;h4&gt;New operators&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;SelectMany: It actually works now and is super fast&lt;/li&gt;
&lt;li&gt;GroupJoin: Great operator to help setup object relationships&lt;/li&gt;
&lt;li&gt;Except&lt;/li&gt;
&lt;li&gt;Concat&lt;/li&gt;&lt;/ul&gt;
&lt;h4&gt;Tweaks&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;ContinuousMax/Min support Nullable decimals&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>akutruff</author><pubDate>Wed, 06 Jan 2010 16:12:47 GMT</pubDate><guid isPermaLink="false">Updated Release: ContinuousLinq 2.2.0.0 (Jan 06, 2010) 20100106041247P</guid></item><item><title>Released: ContinuousLinq 2.2.0.0 (Jan 06, 2010)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38322</link><description>&lt;div&gt;This is a pretty big release....
&lt;h4&gt;Significant performance improvements&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;Weak event system overhaul&lt;/li&gt;
&lt;li&gt;Implement INotifyPropertyChanging on the objects in your source collections to get most benefit.  However this is not required.  Only implementing INotifyPropertyChanged is still fine, but you will gain little performance improvement.&lt;/li&gt;&lt;/ul&gt;

&lt;h4&gt;Reactive Programming support:  ReactiveObject&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;Allows you to make a reactive and event driven object model for amazingly decoupled Models, ViewModels/Presenters.  &lt;/li&gt;
&lt;li&gt;Founded on INotifyPropertyChanged/INotifyPropertyChanging rather than requiring the user to rely on first class events.&lt;/li&gt;
&lt;li&gt;Highly optimized core that can observe changes on any object implementing INotifyPropertyChanged, and has extremely low overhead.&lt;/li&gt;
&lt;li&gt;See &lt;a href="http://kutruff.wordpress.com/2009/07/14/reactive-programming-in-c-reactiveobject/"&gt;Andy Kutruff&amp;#39;s blog post on ReactiveObject&lt;span&gt;&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Batch update support:  If you use AddRange when adding to the source of query, it will reduce the amount of NotifyCollectionChanged events.  This is huge for query outputs that are bound to WPF ItemsControls as the UI will only need to update once.&lt;/li&gt;&lt;/ul&gt;

&lt;h4&gt;New operators&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;SelectMany: It actually works now and is super fast&lt;/li&gt;
&lt;li&gt;GroupJoin: Great operator to help setup object relationships&lt;/li&gt;
&lt;li&gt;Except&lt;/li&gt;
&lt;li&gt;Concat&lt;/li&gt;&lt;/ul&gt;
&lt;h4&gt;Tweaks&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;ContinuousMax/Min support Nullable decimals&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div&gt;&lt;/div&gt;</description><author></author><pubDate>Wed, 06 Jan 2010 16:12:47 GMT</pubDate><guid isPermaLink="false">Released: ContinuousLinq 2.2.0.0 (Jan 06, 2010) 20100106041247P</guid></item><item><title>Created Release: ContinuousLinq 2.2.0.0 (Jan 06, 2010)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=38322</link><description>&lt;div class="wikidoc"&gt;This is a pretty big release....
&lt;h4&gt;Significant performance improvements&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;Weak event system overhaul&lt;/li&gt;
&lt;li&gt;Implement INotifyPropertyChanging on the objects in your source collections to get most benefit.  However this is not required.  Only implementing INotifyPropertyChanged is still fine, but you will gain little performance improvement.&lt;/li&gt;&lt;/ul&gt;

&lt;h4&gt;Reactive Programming support:  ReactiveObject&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;Allows you to make a reactive and event driven object model for amazingly decoupled Models, ViewModels/Presenters.  &lt;/li&gt;
&lt;li&gt;Founded on INotifyPropertyChanged/INotifyPropertyChanging rather than requiring the user to rely on first class events.&lt;/li&gt;
&lt;li&gt;Highly optimized core that can observe changes on any object implementing INotifyPropertyChanged, and has extremely low overhead.&lt;/li&gt;
&lt;li&gt;See &lt;a href="http://kutruff.wordpress.com/2009/07/14/reactive-programming-in-c-reactiveobject/" class="externalLink"&gt;Andy Kutruff&amp;#39;s blog post on ReactiveObject&lt;span class="externalLinkIcon"&gt;&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Batch update support:  If you use AddRange when adding to the source of query, it will reduce the amount of NotifyCollectionChanged events.  This is huge for query outputs that are bound to WPF ItemsControls as the UI will only need to update once.&lt;/li&gt;&lt;/ul&gt;

&lt;h4&gt;New operators&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;SelectMany: It actually works now and is super fast&lt;/li&gt;
&lt;li&gt;GroupJoin: Great operator to help setup object relationships&lt;/li&gt;
&lt;li&gt;Except&lt;/li&gt;
&lt;li&gt;Concat&lt;/li&gt;&lt;/ul&gt;
&lt;h4&gt;Tweaks&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;ContinuousMax/Min support Nullable decimals&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>akutruff</author><pubDate>Wed, 06 Jan 2010 16:11:14 GMT</pubDate><guid isPermaLink="false">Created Release: ContinuousLinq 2.2.0.0 (Jan 06, 2010) 20100106041114P</guid></item><item><title>Updated Release: CLINQ v2.1.0.0 (May 26, 2009)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=27860</link><description>&lt;div&gt;CLINQ v2.1.0.0 is a maintenance release that entirely focuses on performance.&lt;br&gt;&lt;br&gt;    * Expression compilation caching - Expression&amp;lt;T&amp;gt;.Compile() is very slow and must be run every time a query is created.  (This is a standard for most LINQ libraries these days.)  For classes that are reused, queries were being recompiled each and every time these classes were instantiated.  Now, compiled code for expressions is cached, resulting in a 109x performance increase for open expressions, and an 8x performance increase for closures.  Added as an extension method to Expression&amp;lt;T&amp;gt; called CachedCompile().&lt;br&gt;&lt;br&gt;    * Added more generic Func delegates to System namespace - For some reason the .Net framework only supplies definitions of Func&amp;lt;T&amp;gt; up to Func&amp;lt;T1, T2, T3, T4, TResult&amp;gt;.  We now generate up to T20, which should give you plenty of breathing room for complicated queries.&lt;br&gt;&lt;br&gt;    * Added Partial() helper extension - Added helper methods for &lt;a href="http://blogs.msdn.com/wesdyer/archive/2007/01/29/currying-and-partial-function-application.aspx"&gt;Partial Function Application&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;    * Smart Property Notification (From 2.0.0.0) - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluatons every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/div&gt;</description><author>akutruff</author><pubDate>Mon, 01 Jun 2009 15:14:09 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.1.0.0 (May 26, 2009) 20090601031409P</guid></item><item><title>Released: CLINQ v2.1.0.0 (May 26, 2009)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=27860</link><description>&lt;div&gt;CLINQ v2.1.0.0 is a maintenance release that entirely focuses on performance.&lt;br&gt;&lt;br&gt;    * Expression compilation caching - Expression&amp;lt;T&amp;gt;.Compile() is very slow and must be run every time a query is created.  (This is a standard for most LINQ libraries these days.)  For classes that are reused, queries were being recompiled each and every time these classes were instantiated.  Now, compiled code for expressions is cached, resulting in a 109x performance increase for open expressions, and an 8x performance increase for closures.  Added as an extension method to Expression&amp;lt;T&amp;gt; called CachedCompile().&lt;br&gt;&lt;br&gt;    * Added more generic Func delegates to System namespace - For some reason the .Net framework only supplies definitions of Func&amp;lt;T&amp;gt; up to Func&amp;lt;T1, T2, T3, T4, TResult&amp;gt;.  We now generate up to T20, which should give you plenty of breathing room for complicated queries.&lt;br&gt;&lt;br&gt;    * Added Partial() helper extension - Added helper methods for &lt;a href="http://blogs.msdn.com/wesdyer/archive/2007/01/29/currying-and-partial-function-application.aspx"&gt;Partial Function Application&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;    * Smart Property Notification (From 2.0.0.0) - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluatons every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/div&gt;</description><author></author><pubDate>Mon, 01 Jun 2009 15:14:09 GMT</pubDate><guid isPermaLink="false">Released: CLINQ v2.1.0.0 (May 26, 2009) 20090601031409P</guid></item><item><title>Updated Release: CLINQ v2.1.0.0 (May 26, 2009)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=27860</link><description>&lt;div&gt;CLINQ v2.1.0.0 is a maintenance release that entirely focuses on performance.&lt;br&gt;&lt;br&gt;    * Expression compilation caching - Expression&amp;lt;T&amp;gt;.Compile() is very slow and must be run every time a query is created.  (This is a standard for most LINQ libraries these days.)  For classes that are reused, queries were being recompiled each and every time these classes were instantiated.  Now, compiled code for expressions is cached, resulting in a 109x performance increase for open expressions, and an 8x performance increase for closures.  Added as an extension method to Expression&amp;lt;T&amp;gt; called CachedCompile().&lt;br&gt;&lt;br&gt;    * Added more generic Func delegates to System namespace - For some reason the .Net framework only supplies definitions of Func&amp;lt;T&amp;gt; up to Func&amp;lt;T1, T2, T3, T4, TResult&amp;gt;.  We now generate up to T20, which should give you plenty of breathing room for complicated queries.&lt;br&gt;&lt;br&gt;    * Added Partial() helper extension - Added helper methods for &lt;a href="http://blogs.msdn.com/wesdyer/archive/2007/01/29/currying-and-partial-function-application.aspx"&gt;Partial Function Application&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;    * Smart Property Notification (From 2.0.0.0) - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluatons every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/div&gt;</description><author>akutruff</author><pubDate>Mon, 01 Jun 2009 15:13:20 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.1.0.0 (May 26, 2009) 20090601031320P</guid></item><item><title>Updated Release: CLINQ v2.1.0.0 (May 26, 2009)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=27860</link><description>&lt;div&gt;CLINQ v2.1.0.0 is a maintenance release that entirely focuses on performance.&lt;br&gt;&lt;br&gt;    * Expression compilation caching - Expression&amp;lt;T&amp;gt;.Compile() is very slow and must be run every time a query is created.  (This is a standard for most LINQ libraries these days.)  For classes that are reused, queries were being recompiled each and every time these classes were instantiated.  Now, compiled code for expressions is cached, resulting in a 109x performance increase for open expressions, and an 8x performance increase for closures.  Added as an extension method to Expression&amp;lt;T&amp;gt; called CachedCompile().&lt;br&gt;&lt;br&gt;    * Added more generic Func delegates to System namespace - For some reason the .Net framework only supplies definitions of Func&amp;lt;T&amp;gt; up to Func&amp;lt;T1, T2, T3, T4, TResult&amp;gt;.  We now generate up to T20, which should give you plenty of breathing room for complicated queries.&lt;br&gt;&lt;br&gt;    * Added Partial() helper extension - Added helper methods for &lt;a href="http://blogs.msdn.com/wesdyer/archive/2007/01/29/currying-and-partial-function-application.aspx"&gt;Partial Function Application&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;    * Smart Property Notification (From 2.0.0.0) - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluatons every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/div&gt;</description><author>akutruff</author><pubDate>Tue, 26 May 2009 14:06:43 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.1.0.0 (May 26, 2009) 20090526020643P</guid></item><item><title>Released: CLINQ v2.1.0.0 (May 26, 2009)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=27860</link><description>&lt;div&gt;CLINQ v2.1.0.0 is a maintenance release that entirely focuses on performance.&lt;br&gt;&lt;br&gt;    * Expression compilation caching - Expression&amp;lt;T&amp;gt;.Compile() is very slow and must be run every time a query is created.  (This is a standard for most LINQ libraries these days.)  For classes that are reused, queries were being recompiled each and every time these classes were instantiated.  Now, compiled code for expressions is cached, resulting in a 109x performance increase for open expressions, and an 8x performance increase for closures.  Added as an extension method to Expression&amp;lt;T&amp;gt; called CachedCompile().&lt;br&gt;&lt;br&gt;    * Added more generic Func delegates to System namespace - For some reason the .Net framework only supplies definitions of Func&amp;lt;T&amp;gt; up to Func&amp;lt;T1, T2, T3, T4, TResult&amp;gt;.  We now generate up to T20, which should give you plenty of breathing room for complicated queries.&lt;br&gt;&lt;br&gt;    * Added Partial() helper extension - Added helper methods for &lt;a href="http://blogs.msdn.com/wesdyer/archive/2007/01/29/currying-and-partial-function-application.aspx"&gt;Partial Function Application&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;    * Smart Property Notification (From 2.0.0.0) - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluatons every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/div&gt;</description><author></author><pubDate>Tue, 26 May 2009 14:06:43 GMT</pubDate><guid isPermaLink="false">Released: CLINQ v2.1.0.0 (May 26, 2009) 20090526020643P</guid></item><item><title>Updated Release: CLINQ v2.1.0.0</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=27860</link><description>&lt;div&gt;CLINQ v2.1.0.0 is a maintenance release that entirely focuses on performance.&lt;br&gt;&lt;br&gt;    * Expression compilation caching - Expression&amp;lt;T&amp;gt;.Compile() is very slow and must be run every time a query is created.  (This is a standard for most LINQ libraries these days.)  For classes that are reused, queries were being recompiled each and every time these classes were instantiated.  Now, compiled code for expressions is cached, resulting in a 109x performance increase for open expressions, and an 8x performance increase for closures.  Added as an extension method to Expression&amp;lt;T&amp;gt; called CachedCompile().&lt;br&gt;&lt;br&gt;    * Added more generic Func delegates to System namespace - For some reason the .Net framework only supplies definitions of Func&amp;lt;T&amp;gt; up to Func&amp;lt;T1, T2, T3, T4, TResult&amp;gt;.  We now generate up to T20, which should give you plenty of breathing room for complicated queries.&lt;br&gt;&lt;br&gt;    * Added Partial() helper extension - Added helper methods for &lt;a href="http://blogs.msdn.com/wesdyer/archive/2007/01/29/currying-and-partial-function-application.aspx"&gt;Partial Function Application&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;    * Smart Property Notification (From 2.0.0.0) - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluatons every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/div&gt;</description><author>akutruff</author><pubDate>Tue, 26 May 2009 13:58:40 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.1.0.0 20090526015840P</guid></item><item><title>Updated Release: CLINQ v2.0.0.0 (Mar 13, 2009)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=16757</link><description>&lt;div&gt;
CLINQ v2.0.0.0 is a major new release for CLINQ. In fact, much of it has been completely re-written from the ground up. The main focus of this release has been performance. Everything in CLINQ v2.0.0.0 is designed to run faster and eliminate redundancy.&lt;br&gt; &lt;br&gt;Some of the noteworthy &lt;a href="http://clinq.codeplex.com/Wiki/View.aspx?title=CLINQ v2.0 Features"&gt;CLINQ v2.0 Features&lt;/a&gt;:&lt;br&gt;&lt;ul&gt;
&lt;li&gt;&lt;b&gt;&lt;a href="http://clinq.codeplex.com/Wiki/View.aspx?title=Smart Property Notification"&gt;Smart Property Notification&lt;/a&gt;&lt;/b&gt; - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluations every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>dotnetaddict</author><pubDate>Fri, 13 Mar 2009 17:00:49 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.0.0.0 (Mar 13, 2009) 20090313050049P</guid></item><item><title>Released: CLINQ v2.0.0.0 (Mar 13, 2009)</title><link>http://clinq.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=16757</link><description>&lt;div&gt;
CLINQ v2.0.0.0 is a major new release for CLINQ. In fact, much of it has been completely re-written from the ground up. The main focus of this release has been performance. Everything in CLINQ v2.0.0.0 is designed to run faster and eliminate redundancy.&lt;br&gt; &lt;br&gt;Some of the noteworthy &lt;a href="http://clinq.codeplex.com/Wiki/View.aspx?title=CLINQ v2.0 Features"&gt;CLINQ v2.0 Features&lt;/a&gt;:&lt;br&gt;&lt;ul&gt;
&lt;li&gt;&lt;b&gt;&lt;a href="http://clinq.codeplex.com/Wiki/View.aspx?title=Smart Property Notification"&gt;Smart Property Notification&lt;/a&gt;&lt;/b&gt; - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluations every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author></author><pubDate>Fri, 13 Mar 2009 17:00:49 GMT</pubDate><guid isPermaLink="false">Released: CLINQ v2.0.0.0 (Mar 13, 2009) 20090313050049P</guid></item><item><title>Updated Release: CLINQ v2.0.0.0</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx?ReleaseId=16757</link><description>&lt;div&gt;
CLINQ v2.0.0.0 is a major new release for CLINQ. In fact, much of it has been completely re-written from the ground up. The main focus of this release has been performance. Everything in CLINQ v2.0.0.0 is designed to run faster and eliminate redundancy.&lt;br&gt; &lt;br&gt;Some of the noteworthy &lt;a href="http://www.codeplex.com/clinq/Wiki/View.aspx?title=CLINQ v2.0 Features"&gt;CLINQ v2.0 Features&lt;/a&gt;:&lt;br&gt;&lt;ul&gt;
&lt;li&gt;&lt;b&gt;&lt;a href="http://www.codeplex.com/clinq/Wiki/View.aspx?title=Smart Property Notification"&gt;Smart Property Notification&lt;/a&gt;&lt;/b&gt; - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluations every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>DotNetAddict</author><pubDate>Tue, 07 Oct 2008 17:21:31 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.0.0.0 20081007052131P</guid></item><item><title>Updated Release: CLINQ v2.0.0.0</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx?ReleaseId=16757</link><description>&lt;div&gt;
CLINQ v2.0.0.0 is a major new release for CLINQ. In fact, much of it has been completely re-written from the ground up. The main focus of this release has been performance. Everything in CLINQ v2.0.0.0 is designed to run faster and eliminate redundancy.&lt;br&gt; &lt;br&gt;Some of the notable new features in this release:&lt;br&gt;&lt;ul&gt;
&lt;li&gt;&lt;b&gt;&lt;a href="http://www.codeplex.com/clinq/Wiki/View.aspx?title=Smart Property Notification"&gt;Smart Property Notification&lt;/a&gt;&lt;/b&gt; - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluations every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. &lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>DotNetAddict</author><pubDate>Tue, 07 Oct 2008 17:16:38 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.0.0.0 20081007051638P</guid></item><item><title>Updated Release: CLINQ v2.0.0.0</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx?ReleaseId=16757</link><description>&lt;div&gt;
CLINQ v2.0.0.0 is a major new release for CLINQ. In fact, much of it has been completely re-written from the ground up. The main focus of this release has been performance. Everything in CLINQ v2.0.0.0 is designed to run faster and eliminate redundancy.&lt;br&gt; &lt;br&gt;Some of the notable new features in this release:&lt;br&gt;&lt;ul&gt;
&lt;li&gt;&lt;b&gt;Smart Property Notification&lt;/b&gt; - In previous releases of CLINQ, the adapters would attach to the source collection and would trigger re-evaluations every time any property on any object changed. In CLINQ v2, the only time we ever re-evaluate the CLINQ query is when a property that actually impacts the result set is changed. In other words, if you are filtering a result set on Age but the Name property keeps changing over and over again, we will no longer be wasting CPU cycles doing needless re-evaluations. The .NET Addict's blog has a good post describing this feature here &lt;a href="http://www.codeplex.com/clinq/Wiki/View.aspx?title=http://dotnetaddict.dotnetdevelopersjournal.com/clinq2_deeproperty.htm"&gt;http://dotnetaddict.dotnetdevelopersjournal.com/clinq2_deeproperty.htm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>DotNetAddict</author><pubDate>Tue, 07 Oct 2008 17:15:44 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.0.0.0 20081007051544P</guid></item><item><title>Updated Release: CLINQ v2.0.0.0</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx?ReleaseId=16757</link><description>&lt;div&gt;
CLINQ v2.0.0.0 is a major new release for CLINQ. In fact, much of it has been completely re-written from the ground up. The main focus of this release has been performance. Everything in CLINQ v2.0.0.0 is designed to run faster and eliminate redundancy.&lt;br&gt; &lt;br&gt;Some of the notable new features in this release:&lt;br&gt;&lt;ul&gt;
&lt;li&gt;&lt;i&gt;&amp;quot;Smart&amp;quot; adapters&lt;/i&gt; - CLINQ now parses the expression tree of all your CLINQ queries to determine which properties need to be monitored. &lt;b&gt;Only&lt;/b&gt; those properties will be monitored, all other property changes are ignored. This &lt;i&gt;dramatically&lt;/i&gt; reduces the CPU footprint of CLINQ queries.&lt;/li&gt;&lt;li&gt;&lt;i&gt;Aggregation Pausing&lt;/i&gt; - You can now pause all aggregation or individually pause single continuous values. This is ideal for when you know your application is going to process a vast amount of bulk data but you don't want to abuse the GUI during the update. Even better, when the bulk update is done, &lt;i&gt;only those aggregates that were affected during the pause&lt;/i&gt; will be re-aggregated. &lt;/li&gt;&lt;li&gt;&lt;i&gt;Deep property notifications&lt;/i&gt; - You can now monitor deep levels of property changes inside a CLINQ query.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>DotNetAddict</author><pubDate>Tue, 07 Oct 2008 17:12:09 GMT</pubDate><guid isPermaLink="false">Updated Release: CLINQ v2.0.0.0 20081007051209P</guid></item><item><title>UPDATED RELEASE: CLINQ v1.1.0.0 (May 02, 2008)</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx?ReleaseId=12569</link><description>This release of CLINQ contains both new features and incremental upgrades to existing functionality. The code has been cleaned up significantly as we&amp;#39;ve been trimming some of the needless fat from some of the library methods and classes.&lt;br /&gt;&lt;br /&gt;New features include the ability to perform &amp;#91;Continuous Aggregation&amp;#93;, which allows you to define a continuous query that,  instead of returning a set of results, returns a continuously updating continuous value such as a sum, min, max, average, or even standard deviation. &lt;br /&gt;&lt;br /&gt;We have also created a new demo application for this version of CLINQ called &amp;#34;Stock Monitor&amp;#34;, which simulates looking at ticker data for a particular stock. It shows not only how to do multiple continuous queries based on a single source set, but also shows off the power of continuous aggregates, and even how to create a live, continuous line graph using WPF data binding and CLINQ aggregates&amp;#33;</description><author></author><pubDate>Fri, 02 May 2008 16:58:08 GMT</pubDate><guid isPermaLink="false">UPDATED RELEASE: CLINQ v1.1.0.0 (May 02, 2008) 20080502045808P</guid></item><item><title>UPDATED RELEASE: CLINQ v1.1.0.0</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx?ReleaseId=12569</link><description>This release of CLINQ contains both new features and incremental upgrades to existing functionality. The code has been cleaned up significantly as we&amp;#39;ve been trimming some of the needless fat from some of the library methods and classes.&lt;br /&gt;&lt;br /&gt;New features include the ability to perform &amp;#91;Continuous Aggregation&amp;#93;, which allows you to define a continuous query that,  instead of returning a set of results, returns a continuously updating continuous value such as a sum, min, max, average, or even standard deviation. &lt;br /&gt;&lt;br /&gt;We have also created a new demo application for this version of CLINQ called &amp;#34;Stock Monitor&amp;#34;, which simulates looking at ticker data for a particular stock. It shows not only how to do multiple continuous queries based on a single source set, but also shows off the power of continuous aggregates, and even how to create a live, continuous line graph using WPF data binding and CLINQ aggregates&amp;#33;</description><author></author><pubDate>Fri, 02 May 2008 16:57:40 GMT</pubDate><guid isPermaLink="false">UPDATED RELEASE: CLINQ v1.1.0.0 20080502045740P</guid></item><item><title>UPDATED RELEASE: CLINQ v1.1.0.0</title><link>http://www.codeplex.com/clinq/Release/ProjectReleases.aspx?ReleaseId=12569</link><description>This release of CLINQ contains both new features and incremental upgrades to existing functionality. The code has been cleaned up significantly as we&amp;#39;ve been trimming some of the needless fat from some of the library methods and classes.&lt;br /&gt;&lt;br /&gt;New features include the ability to perform &amp;#91;Continuous Aggregation&amp;#93;, which allows you to define a continuous query that,  instead of returning a set of results, returns a continuously updating continuous value such as a sum, min, max, average, or even standard deviation. &lt;br /&gt;&lt;br /&gt;We have also created a new demo application for this version of CLINQ called &amp;#34;Stock Monitor&amp;#34;, which simulates looking at ticker data for a particular stock. It shows not only how to do multiple continuous queries based on a single source set, but also shows off the power of continuous aggregates, and even how to create a live, continuous line graph using WPF data binding and CLINQ aggregates&amp;#33;</description><author></author><pubDate>Fri, 02 May 2008 16:55:04 GMT</pubDate><guid isPermaLink="false">UPDATED RELEASE: CLINQ v1.1.0.0 20080502045504P</guid></item></channel></rss>