Remotion Linq 2.0.0 alpha 3 released

[Michael Ketting]

I've just released alpha 3 of the re-linq frontend:
* Re-introduced dedicated builds for .NET 3.5 and .NET 4.0 as part of the NuGet package. (https://www.re-motion.org/jira/browse/RMLNQ-57, https://www.re-motion.org/jira/browse/RMLNQ-59)
* Performance improvement for startup. (https://www.re-motion.org/jira/browse/RMLNQ-41)
* Removed utilities and collection types not directly related with the public API. (https://www.re-motion.org/jira/browse/RMLNQ-63, https://www.re-motion.org/jira/browse/RMLNQ-64)

Planned changes:
* Replacing re-linq's ExpressionTreeVisitor with .NET 4.0 provided ExpressionTreeVisitor type + extension type for remaining features not covered by the native implementation.
* Replacing FormattingExpressionTreeVisitor with native implementation of string output for expression trees.
* Sealing types that are not meant as extension point

Best regards, Michael

[Alexander Zaytsev]

Hi,

What about Remotion.Linq.EagerFetching for .NET 4?

Best Regards,

Alexander

--
You received this message because you are subscribed to the Google Groups "re-motion Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to re-motion-use...@googlegroups.com.
To post to this group, send email to re-moti...@googlegroups.com.
Visit this group at http://groups.google.com/group/re-motion-users.
For more options, visit https://groups.google.com/d/optout.

[Michael Ketting]

Hi Alexander!

Didn't realize there was interest for it (actually, the entire Eager Fetching namespace, not just .NET 4.0 :) ), but yeah, sure, shouldnt' be a problem.

Best regards, Michael

On Monday, March 30, 2015 at 2:27:19 AM UTC+2, Alexander Zaytsev wrote:

Hi,

What about Remotion.Linq.EagerFetching for .NET 4?

Best Regards,

Alexander

On Sun, Mar 29, 2015 at 3:37 AM, Michael Ketting <> wrote:

I've just released alpha 3 of the re-linq frontend:
* Re-introduced dedicated builds for .NET 3.5 and .NET 4.0 as part of the NuGet package. (https://www.re-motion.org/jira/browse/RMLNQ-57, https://www.re-motion.org/jira/browse/RMLNQ-59)
* Performance improvement for startup. (https://www.re-motion.org/jira/browse/RMLNQ-41)
* Removed utilities and collection types not directly related with the public API. (https://www.re-motion.org/jira/browse/RMLNQ-63, https://www.re-motion.org/jira/browse/RMLNQ-64)

Planned changes:
* Replacing re-linq's ExpressionTreeVisitor with .NET 4.0 provided ExpressionTreeVisitor type + extension type for remaining features not covered by the native implementation.
* Replacing FormattingExpressionTreeVisitor with native implementation of string output for expression trees.
* Sealing types that are not meant as extension point

Best regards, Michael

--
You received this message because you are subscribed to the Google Groups "re-motion Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to re-motion-users+unsubscribe@googlegroups.com.
To post to this group, send email to re-motion-users@googlegroups.com.

[Alexander Zaytsev]

Yes, we, the NHibernate, do have interest in Fetching, and we still .NET 4

Best Regards,

Alexander

To unsubscribe from this group and stop receiving emails from it, send an email to re-motion-use...@googlegroups.com.
To post to this group, send email to re-moti...@googlegroups.com.

[Michael Ketting]

Hi Alexander!

I've now added .NET 4.0 (and .NET 3.5) support to re-linq Eager Fetching and released v2.0.0 alpha.4.

Best regards, Michael

On Tuesday, March 31, 2015 at 6:03:26 AM UTC+2, Alexander Zaytsev wrote:

Yes, we, the NHibernate, do have interest in Fetching, and we still .NET 4

Best Regards,

Alexander