Issue 25 in linqbridge: Namespace Pollution of System.Linq

[linqb...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 25 by brianb...@gmail.com: Namespace Pollution of System.Linq
http://code.google.com/p/linqbridge/issues/detail?id=25

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.

[linqb...@googlecode.com]

Updates:
Status: WontFix

Comment #1 on issue 25 by azizatif: Namespace Pollution of System.Linq
http://code.google.com/p/linqbridge/issues/detail?id=25

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.