Welcome to the CodeSmith Community!


Product Updates

A description has not yet been added to this group.


Rate This
  • Comments 3
  • Added Visual Studio 2010 and .NET 4 Support
  • Updated QuickStart with latest Dynamic Data and DataServices
  • Added SQLCacheDependancy Support
  • Added IQueryable Cache Extensions
  • Added Include extension for advanced eager loading
  • Improved AuditLog, now includes updates after SubmitChanges
  • Fixed bug in CacheManager where default profile did not load properly
  • Added override RuleManager.Run override that populates the TrackedObject.Original
  • Fixed bug in AuditLog
  • Fixed bugs in VB Quick Start
  • Added DataContextName to QuickStart.cst
  • Fixed Managers didn't have the same access modifier as entities
  • Fixed bug in GetByKey function in VB
  • Fixed invalid cast exception for Range attribute on short properties
  • Fixed bug in ExecuteFutureQueries when no queries were loaded
  • Fixed bug in Manager when column didn't exist
  • Added logic to skip columns of type 'hierarchyid'
  • Added work around for L2S Profiler not working with transactions
  • Fixed bug where Metadata property types did not match up with Enums
  • Added BeginTransaction with no overload

Download PLINQO 5.0

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • * Please enter your name
  • * Please enter a comment
  • Post
  • The year is 2010. Visual Studio's UI is all new. The .NET framework is on version 4.0. ...and PLINQO

  • Is the VB version up to date?  I can create a C# solution and the data project compiles fine.  When I change to VB, I get a lot of errors of the type:

    C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll : (0,0) CodeSmith template compiler: BC42204: Assembly 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll' references assembly 'System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089', which is ambiguous between 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.dll' (referenced by project 'vbc') and 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll' (referenced by project 'vbc'). 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.dll' will be used. If both assemblies are identical, change the references to the same location.

  • Hello,

    This is a known issue, please see the following post for the work around (community.codesmithtools.com/.../42145.aspx)



Page 1 of 1 (3 items)