(just for the record, I hate April fools day, so this isn't a joke)

With v2.6, we'll release our last version with .NET 1.x support (CF 1.x, .NET 1.0, .NET 1.1). We will try to implement all of the new features (except linq support ) we add to v2.6 (which aren't that many though) also to the .NET 1.x version of the library but no enhancements to the framework code will be added to the .NET 1.x branch anymore (bugfixes are done though). So memory usage enhancements, refactorings etc. are done solely on the .NET 2.0 branch (which is also the .NET 3.5 runtime, the CLR is the same anyway).

We did add derived table support to the .net 1.x branch as it's an important new feature, however it's likely that the changes required for non-ansi joins aren't added to the .NET 1.x branch. We are aware that we still have customers using .net 1.1 and therefore we decided to keep .net 1.x support in v2.6. However as backporting code to .net 1.x (and if template changes are required, the burden is even higher) is sometimes significantly expensive due to refactorings which have to be done in the .NET 1.x codebase without proper tooling for refactorings in vs.net 2003, we decided to limit the .NET 1.x changes in v2.6 to new features only.

v3 will be based on .NET 3.5 with runtimes / templates support for .net 2.0+ only, hence the end of life for .net 1.x in LLBLGen Pro with v2.6.