Activity Not Available
4
I Use This!

News

Analyzed 3 months ago. based on code collected 3 months ago.
Posted over 5 years ago by re-motion Team
re-mix (formerly known as re-motion mixins) has been published to CodePlex. The link is http://remix.codeplex.com Similar to re-linq, the source code repository will still be part of the re-motion project. The source code and binaries of a “mixin ... [More] release” will be published to CodePlex. The re-mix page on CodePlex will also contain additional documentation to […] [Less]
Posted over 5 years ago by Michael Ketting
Today’s blog-post is about the recent namespace change in re-linq. About a month ago, we restructured re-motion’s folders and namespaces to make re-linq a top-level project within re-motion. This move had been a long time coming but the time was never right until now. It is also the first step towards pushing the re-linq source […]
Posted about 6 years ago by Michael Ketting
As of this week, the re-motion project has a publicly available issue tracker, courtesy of Atlassian’s JIRA and Patrick Größ, who took it upon himself to tame the beast. Aside from setting it up and integrating it with our DMZ, this also meant integrating it with our internal processes here at rubicon. I’ll get to […]
Posted about 6 years ago by re-motion Team
I'm happy to announce that re-linq is going to support partial trust environments out of the box starting from build 1.13.63, which is due at the end of this week. Once it's ready, you can get it here: http://www.re-motion.org/builds/. The SVN trunk ... [More] already includes the partial trust feature. re-linq can also be used from ASP.NET medium trust, but some LINQ query features (such as anonymous types created by the C# compiler or access to local variables from a query) require reflection permissions not available in default medium trust. Note that the C# compiler often automatically uses anonymous types when you write a LINQ query with multiple from clauses or joins. In order to be able to parse such queries using re-linq (or any other LINQ provider, I assume), the ReflectionPermission must explicitly be granted with the MemberAccess permission flag in addition to the default ASP.NET medium trust permissions. - Fabian Copied from our mailing list. Please post any questions about this feature to the list. [Less]
Posted about 6 years ago by Fabian
I’m happy to announce that re-linq is going to support partial trust environments out of the box starting from build 1.13.63, which is due at the end of this week. Once it’s ready, you can get it here: http://www.re-motion.org/builds/. The SVN trunk already includes the partial trust feature. re-linq can also be used from ASP.NET […]
Posted over 6 years ago by Fabian
The re-motion team has worked on this for quite some time: Michael Ketting gathered the requirements, Patrick Größ wrote a JIRA integration tool based on Michael’s instructions, I integrated that tool into our build system. And now we’re finally “done” – we finally have release notes for our weekly re-motion builds. Here is a partial […]
Posted over 6 years ago by re-motion Team
The re-motion team has worked on this for quite some time: Michael Ketting gathered the requirements, Patrick Größ wrote a JIRA integration tool based on Michael’s instructions, I integrated that tool into our build system. And now we’re finally ... [More] “done” – we finally have release notes for our weekly re-motion builds. Here is a partial screenshot of the ones for version 1.13.43: The re-linq build packages also have dedicated release notes which only include re-linq issues: The release notes are automatically generated from our JIRA issues; we try to create descriptive issues for each change we are making. This involves new features and bugfixes as well as  breaking changes, performance improvements, and so on. We started doing so some time ago, in anticipation of having auto-generated release notes, and so we’ve been able to generated release notes for older builds as well. This means if you’re currently using 1.13.23 and want to know what has changed since then, you can simply look up all the release notes starting from 1.13.24 (be aware, though, that older release notes might not be as complete as the new ones). The downloadable ZIP packages contain the release notes of all the builds created for the respective minor version (1.13, currently). Here’s what the download package for build 1.13.43 contains: All in all, I hope this will make it easier for you to determine when to upgrade your re-motion versions; and it might also give some meaning to the “COMMONS-1234” keys we’re always referring to in our SVN commit messages :) [Less]
Posted over 6 years ago by Fabian
I’ve already alluded to it on our mailing list, and now it’s official: starting with build 1.13.41, the re-linq assembly Remotion.Data.Linq.dll is now a stand-alone DLL. Over Christmas, Matthias Görtler spent quite a few hours rewriting those parts of re-linq that used to depend on the rest of re-motion. Here’s the result: 1.13.40: What a […]
Posted over 6 years ago by re-motion Team
I’ve already alluded to it on our mailing list, and now it’s official: starting with build 1.13.41, the re-linq assembly Remotion.Data.Linq.dll is now a stand-alone DLL. Over Christmas, Matthias Görtler spent quite a few hours rewriting those parts ... [More] of re-linq that used to depend on the rest of re-motion. Here’s the result: 1.13.40: What a difference a reference makes… 1.13.41: Only standard libs, please As you can see, the reference to Remotion.dll also added indirect dependencies on Remotion.Interfaces.dll, log4net, and Castle DynamicProxy 2. By removing that reference, re-linq now only depends on .NET framework assemblies. That should facilitate interoperability for projects that already use a specific version of log4net or DynamicProxy. If you have any questions, just post them to our discussion group. - Fabian [Less]
Posted almost 7 years ago by re-motion Team
Fabian had the news first, but here it is: We wanted to take re-motion to CodePlex already, but LGPL v3 is not a valid license there. We modified the license headers of re-motion from LGPL v3 to "LGPL v2.1 or later”, so we should be cool with ... [More] CodePlex. Here’s the link: relinq.codeplex.com All the stuff, including the Subversion repository, is still here on re-motion.org, and CodePlex has only a few links and downloads. That’s a first step, and we believe that some people will learn about re-linq only through its presence on CodePlex. Later, we plan to decouple re-linq from the rest of re-motion, since there is not a lot of shared code: re-linq uses almost nothing from re-motion, and it should therefore be a separate project, with a separate release cycle. re-store (re-motion’s ORM) uses re-linq and will continue to do so. In upcoming releases, re-store will be treated just like any other downstream project from re-linq’s perspective. [Less]