An easy way to use LINQ to Objects in your Unity3D iOS games

  • Same API as in Microsoft .NET LINQ
  • Exactly same behaviour even in non-trivial cases
  • Works flawlessly on any platform including iOS
  • Compatible with modern Unity3D 4.x

Learn More Buy This


Same API as in Microsoft .NET LINQ

All the same convenient extension methods you're accustomed to

We have implemented all 176 methods from .NET LINQ Enumerable class including Select, Where, OrderBy, ThenBy, All, Any and many others. All class and method definitions are the same as in LINQ to Objects.

Exactly same behaviour even in non-trivial cases

All your previous code using LINQ will work fine with LINQ to iOS

LINQ to iOS works like Microsoft .NET LINQ even in complex situations. It throws same exceptions when wrong parameters are passed and supports complex features such as deferred execution.

Works flawlessly on any platform including iOS

Works well on iOS, Android, Web, Mac and PC

LINQ to iOS is well-tested on both mobile and desktop platforms. It causes no errors or crashes on any of them. Having problems with JIT-compile errors on iOS? Now you can solve those problems with LINQ to iOS!

Compatible with modern Unity3D 4.x

Supports from Unity3D 4.0.0 to the latest version

Every method is covered with numerous unit-tests included into the project that help us identify the problems and fix them quickly. In case if you encounter any problems we guarantee you a responsive support and free updates.

Getting Started

LINQ to iOS is very easy to be integrated to your project. It just takes you two steps to make it working.

Download & Import

Download and import the package into your project. Make sure that LinqTools.dll is placed inside your Plugins folder.

Use it

Replace System.Linq with LinqTools everywhere in your existing code. Add using LinqTools; line to any script where you're going to use LINQ. Now you're ready to use LINQ on any platform!

Need To Know More


The way LINQ to iOS works

As you know most LINQ methods are generic. Generic methods that you know call the other generic methods inside their implementation. However Mono compiler has limitations to nested generics. It cannot process too much nested generic methods and classes and so you receive JIT-compile errors in runtime.

We have reimplemented all the LINQ methods, but we left only public methods generic. All the core logic is implemented inside non-generic methods, with appropriate cast in the end. That's why LINQ to iOS is working flawlessly even on iOS.

Forum Buy