This project is read-only.

Your project is useless, Linq works on .NET 2.0 !

Yes, NLinq is useless. Well, at least for people programming their applications with Visual Studio .NET 2008. For people using a previous version it might be usefull. There are also some scenarios where this could answer the Linq "dynamic" model flow (c.f. bellow).

It's not Linq, you even don't have intellisense !

Yes, NLinq is not as powerfull as Linq. Actually we are not stating that NLinq is better than Linq, even not as good. The Linq language is a subset of C# and VB.NET in Visual Studio 2008. Thus we can't have those keywords in other versions, which makes it impossible not to use strings to represent Linq queries.

How is the performance with NLinq ?

Bad ! And maybe even more than Linq has bad performances. You can't "browse" objects in a generic way with the same performance you browse them specifically. I mean if you want "performance", just don't use Linq, even C#, use assembler. You should ask yourself what time you judge convenient for a specific query, then try it. I can say that most of the time you won't say it's too slow for the advantage it offers.
If you want better performance, some other projects add indexing to "Linq To Objects" (c.f.

So what should I use NLinq for ?

Fun ! And maybe some more interesting things. If you are using earlier versions of Visual Studio .NET the answer is the same as why you should use Linq. But there are some scenarios where NLinq can be helpful even for Visual Studio .NET 2008 users. For instance if you need to set mathematical formulas or object queries outside the application, i.e. in configuration files or the database, even the real Linq can't help you. Then NLinq beats it ! Yeah !!!!

Last edited Sep 6, 2007 at 8:03 AM by sebastienros, version 3


No comments yet.