<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>MultiTierLinqToSql Releases Rss Feed</title><link>http://www.codeplex.com/MultiTierLinqToSql/Release/ProjectReleases.aspx</link><description>MultiTierLinqToSql Releases Rss Description</description><item><title>Created Release: Release 2.1 (Sep 30, 2009)</title><link>http://multitierlinqtosql.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=33761</link><description>&lt;div class="wikidoc"&gt;&lt;b&gt;Bug fixes&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;*Handles primary key names that have been renamed in dbml&lt;br /&gt;*T4 template now correctly generates classes for UDFs (Updated to L2ST4 v0.83)&lt;br /&gt;&lt;br /&gt;&lt;b&gt;New&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;*Added a new example which uses a ListView&lt;/div&gt;&lt;div class="ClearBoth"&gt;&lt;/div&gt;</description><author>taliesins</author><pubDate>Wed, 30 Sep 2009 10:26:18 GMT</pubDate><guid isPermaLink="false">Created Release: Release 2.1 (Sep 30, 2009) 20090930102618A</guid></item><item><title>Released: Release 2.1 (Sep 30, 2009)</title><link>http://multitierlinqtosql.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=33761</link><description>&lt;div&gt;&lt;b&gt;Bug fixes&lt;/b&gt;&lt;br&gt;&lt;br&gt;*Handles primary key names that have been renamed in dbml&lt;br&gt;*T4 template now correctly generates classes for UDFs (Updated to L2ST4 v0.83)&lt;br&gt;&lt;br&gt;&lt;b&gt;New&lt;/b&gt;&lt;br&gt;&lt;br&gt;*Added a new example which uses a ListView&lt;/div&gt;&lt;div&gt;&lt;/div&gt;</description><author></author><pubDate>Wed, 30 Sep 2009 10:26:18 GMT</pubDate><guid isPermaLink="false">Released: Release 2.1 (Sep 30, 2009) 20090930102618A</guid></item><item><title>Updated Release: Release 2.0 (Apr 14, 2009)</title><link>http://multitierlinqtosql.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=26114</link><description>&lt;div&gt;Contains some major refactoring as described here:&lt;br&gt;http://multitierlinqtosql.codeplex.com/Thread/View.aspx?ThreadId=52788&lt;br&gt;Plus some non-breaking improvements&lt;/div&gt;</description><author>rbates</author><pubDate>Tue, 14 Apr 2009 13:19:22 GMT</pubDate><guid isPermaLink="false">Updated Release: Release 2.0 (Apr 14, 2009) 20090414011922P</guid></item><item><title>Released: Release 2.0 (Apr 14, 2009)</title><link>http://multitierlinqtosql.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=26114</link><description>&lt;div&gt;Contains some major refactoring as described here:&lt;br&gt;http://multitierlinqtosql.codeplex.com/Thread/View.aspx?ThreadId=52788&lt;br&gt;Plus some non-breaking improvements&lt;/div&gt;</description><author></author><pubDate>Tue, 14 Apr 2009 13:19:20 GMT</pubDate><guid isPermaLink="false">Released: Release 2.0 (Apr 14, 2009) 20090414011920P</guid></item><item><title>Updated Release: Release 1.7 (Oct 31, 2008)</title><link>http://www.codeplex.com/MultiTierLinqToSql/Release/ProjectReleases.aspx?ReleaseId=18913</link><description>&lt;div&gt;
&lt;h1&gt;
Release 1.7
&lt;/h1&gt;&lt;ul&gt;
&lt;li&gt;Contains a number of fixes to the way the GenericObjectDatasource works, mainly to make error handling function correctly. If an error is thrown during an insert or update, the exception is now passed into the Updated or Inserted event of the GenericObjectDatasource, so that it can be handled by client code (see the Error Handling section of the main page for more details)&lt;/li&gt;
&lt;/ul&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;This release has also refactored the code, so that all the generic code is now kept in one assembly GenericDataLayer and the project specific stuff has been moved out into another assembly. This makes it easier to use this code in your projects without having to remove example code from the main project.&lt;/li&gt;
&lt;/ul&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;The GenericController class now has a DiscardDataContext method which removes the datacontext from whereever it is stored (Request or Thread) and disposes it. This can be used in the event of errors to get a new DataContext&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>rbates</author><pubDate>Fri, 31 Oct 2008 11:22:45 GMT</pubDate><guid isPermaLink="false">Updated Release: Release 1.7 (Oct 31, 2008) 20081031112245A</guid></item><item><title>Released: Release 1.7 (Oct 31, 2008)</title><link>http://www.codeplex.com/MultiTierLinqToSql/Release/ProjectReleases.aspx?ReleaseId=18913</link><description>&lt;div&gt;
&lt;h1&gt;
Release 1.7
&lt;/h1&gt;&lt;ul&gt;
&lt;li&gt;Contains a number of fixes to the way the GenericObjectDatasource works, mainly to make error handling function correctly. If an error is thrown during an insert or update, the exception is now passed into the Updated or Inserted event of the GenericObjectDatasource, so that it can be handled by client code (see the Error Handling section of the main page for more details)&lt;/li&gt;
&lt;/ul&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;This release has also refactored the code, so that all the generic code is now kept in one assembly GenericDataLayer and the project specific stuff has been moved out into another assembly. This makes it easier to use this code in your projects without having to remove example code from the main project.&lt;/li&gt;
&lt;/ul&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;The GenericController class now has a DiscardDataContext method which removes the datacontext from whereever it is stored (Request or Thread) and disposes it. This can be used in the event of errors to get a new DataContext&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author></author><pubDate>Fri, 31 Oct 2008 11:22:45 GMT</pubDate><guid isPermaLink="false">Released: Release 1.7 (Oct 31, 2008) 20081031112245A</guid></item><item><title>Updated Release: Release 1.7</title><link>http://www.codeplex.com/MultiTierLinqToSql/Release/ProjectReleases.aspx?ReleaseId=18913</link><description>&lt;div&gt;
&lt;h1&gt;
Release 1.7
&lt;/h1&gt;&lt;ul&gt;
&lt;li&gt;Contains a number of fixes to the way the GenericObjectDatasource works, mainly to make error handling function correctly. If an error is thrown during an insert or update, the exception is now passed into the Updated or Inserted event of the GenericObjectDatasource, so that it can be handled by client code (see the Error Handling section of the main page for more details)&lt;/li&gt;
&lt;/ul&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;This release has also refactored the code, so that all the generic code is now kept in one assembly GenericDataLayer and the project specific stuff has been moved out into another assembly. This makes it easier to use this code in your projects without having to remove example code from the main project.&lt;/li&gt;
&lt;/ul&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;The GenericController class now has a DiscardDataContext method which removes the datacontext from whereever it is stored (Request or Thread) and disposes it. This can be used in the event of errors to get a new DataContext&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>rbates</author><pubDate>Fri, 31 Oct 2008 11:21:55 GMT</pubDate><guid isPermaLink="false">Updated Release: Release 1.7 20081031112155A</guid></item><item><title>Updated Release: Release 1.7</title><link>http://www.codeplex.com/MultiTierLinqToSql/Release/ProjectReleases.aspx?ReleaseId=18913</link><description>&lt;div&gt;
&lt;h1&gt;
Release 1.7
&lt;/h1&gt;&lt;ul&gt;
&lt;li&gt;Contains a number of fixes to the way the GenericObjectDatasource works, mainly to make error handling function correctly. If an error is thrown during an insert or update, the exception is now passed into the Updated or Inserted event of the GenericObjectDatasource, so that it can be handled by client code.&lt;/li&gt;
&lt;/ul&gt;See the Error Handling section of the main page for more details.&lt;br&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;This release has also refactored the code, so that all the generic code is now kept in one assembly GenericDataLayer and the project specific stuff has been moved out into another assembly. This makes it easier to use this code in your projects without having to remove example code from the main project.&lt;/li&gt;
&lt;/ul&gt; &lt;br&gt;&lt;ul&gt;
&lt;li&gt;The GenericController class now has a DiscardDataContext method which removes the datacontext from whereever it is stored (Request or Thread) and disposes it. This can be used in the event of errors to get a new DataContext&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>rbates</author><pubDate>Thu, 30 Oct 2008 18:00:18 GMT</pubDate><guid isPermaLink="false">Updated Release: Release 1.7 20081030060018P</guid></item></channel></rss>