search

whatta / linqbridge

Automatically exported from code.google.com/p/linqbridge
Other
0 stars 0 forks source link

Namespace Pollution of System.Linq #25

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.  Use something that depends on LinqBridge in an MVC 3 application
2.  Create a Razor View that uses Linq
3.   Razor will use LinqBridge instead of Linq

As near as we can tell, LinqBridge's pollution of System.Data causes a runtime 
namespace collision.  The solution is to manually delete the LinqBridge dll.

Obviously, this is why one does not pollute namespaces.

Original issue reported on code.google.com by brianb...@gmail.com on 29 Aug 2011 at 4:52

GoogleCodeExporter commented 9 years ago 
MVC 3 requires Microsoft .NET Framework 4.0 where it is pointless to use 
LINQBridge. LINQBridge is designed to be used in projects using C# 3 or later 
but targeting Microsoft .NET Framework 2.0 and where the System.Linq namespace 
does not cause conflict.

Original comment by azizatif on 16 Apr 2012 at 6:34