Reputation: 1992
I created a default LINQ-to-SQL context against my local db, and when I tried to create a new query on one of the databases I received:
CS1705 Assembly 'TypedDataContext_hfitox' with identity 'TypedDataContext_hfitox, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'System.Runtime, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version than referenced assembly 'System.Runtime' with identity 'System.Runtime, Version=7.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
I'm not sure where the 7.0 reference is coming from (for the .NET dropdown in LINQPad, I've tried 'auto' as well), but wondering if there is a way to force built in contexts to use a different runtime? I will have an issue in my 'real' query where I am referencing .NET 7 assemblies and using them, but you can see in image below that is not the case. Any workarounds?
Upvotes: 0
Views: 165