Archive for the ‘re-motion general’ Category
You can now download the most recent re-motion builds from http://www.re-motion.org/builds/.
There are two packages for each build version: one that holds the binaries and one that holds the source code. We’re automatically uploading our weekly builds, so a new version should be added once a week. The development (1.13.x) builds include all the latest features but may also contain incomplete features. The last stable build (1.12.2) is also included. For use with re-linq, I recommend the development builds, since 1.12.2 doesn’t include the new re-linq features yet.
Note that the build packages don’t include change logs yet, we’re currently working on extracting those from our JIRA installation. That’s not so easy as it seems; among other things it requires us to upgrade to JIRA 4, which finally gives us a way to query changes by version number…
Quick announcement: There’s now a re-motion Users Google Group dedicated to the questions and comments of developers using re-motion.
So, if you use re-linq, re-motion Mixins, or any other part of re-motion and you have a question or comment, check it out: http://groups.google.com/group/re-motion-users.
Update (2009-06-05): I’ve just checked in several changes which should make it easier to build re-motion. I’m striking through all the parts of the post that are no longer relevant.
In my last post, I wrote about the problem that the re-motion trunk seems to be quite confusing to people just wanting to check out re-motion mixins. That, however, is not the only problem you might stumble into when trying to download the source code:
- First, you can only download the sources via SVN; we don’t provide a ZIP file for the source code. (We do, however, provide a ZIP file for a binary build.)
- Second, once you check out the sources from SVN, you’ll notice that the file remotion.snk is missing.
Third, you’ll note that for the Visual Studio build to work, you need to install Windows PowerShell and associate ps1 files with powershell.exe. Fourth, you cannot use NAnt to perform the build because we use some custom tasks not included with the standard NAnt releases.
- Fifth, you have to deal with fifty-something projects even when you only wanted to check out re-motion mixins.
Suboptimal. Update (2009-06-05): Much better than before 🙂
We have plans to improve on each of those issues, it’s only a question of finding the time to implement them. For now, here is some advice:
- To download the source code from our SVN server, go to http://subversion.tigris.org/ and get (and install) the SVN binaries. Create a folder called “Remotion” on your hard drive and check out the code into that folder:
svn checkout https://svn.re-motion.org/svn/Remotion/trunk/ trunk
(You can also use TortoiseSVN to check out the code if you want a graphical user interface.)
- We cannot provide our remotion.snk, so you need to create your own one:
sn -k remotion.snk
(You might need to do that from a Visual Studio 2008 Command Prompt so that the tool “sn.exe” can be found.)
Update (2009-06-05): There is now a script for that: Generate-Snk.cmd.
There is one script in the Visual Studio build process that is written using PowerShell. It is responsible for setting up the test database for Remotion.SecurityManager. If you need to build all of re-motion, please install Windows PowerShell and use Windows Explorer to associate ps1 files with it (they are associated with Notepad by default). If you do not need to build Remotion.SecurityManager, you can right-click the “SecurityManager” folder in the Solution Explorer and choose “Unload Projects in Solution Folder”. This will stop SecurityManager from being built and thus remove the requirement for PowerShell. For the time being, use Visual Studio to build re-motion. In the future, we will probably provide the necessary NAnt tasks on the re-motion website.
- If you only want to check out re-motion mixins, you don’t need any of the projects in the Data, Dms, ObjectBinding, Security, SecurityManager, or Web folders. Unload the projects from these folders from Visual Studio (right click the folders in Solution Explorer). In the Core folder, check out the Core.Core project (namespace Mixins).