You should be able to build with the tests if the following conditions are met:
1. A running SQL Server instance named SQLExpress 2. Two databases named test1 and test2 in the SQLExpress instance 3. Distributed Transaction Coordinator should be up (net start MSDTC) 4. (Vista) Build as administrator (because the tests mess with the GAC. As you can see these are not the lightest of requirements, that's why we almost always tell users not to bother with running the tests unless you're providing patches. Our build server (http://builds.castleproject.org/) runs all the tests so you can be pretty sure things are OK when its builds are successful. Good luck with horn -- Roelof. On Mon, Mar 23, 2009 at 12:06 PM, Paul Cowan <[email protected]> wrote: > You are absolutely right. > > I was trying to build by running the tests and it was causing grief because > the remoting project was looking for nunit 2.2.x. > > Without the tests, I can build and progress with my project. > > 2009/3/23 Roelof Blom <[email protected]> > > Or type "build release quick rebuild", this runs a script called build.cmd >> that takes care of running NAnt and uses the correct NUnit version. >> >> This build.cmd script is a fairly recent addition, along with embedding >> NAnt and NUnit in the Castle trunk, to prevent build problems like you >> mentioned. >> >> -- Roelof. >> >> On Sun, Mar 22, 2009 at 2:17 PM, Paul Cowan <[email protected]> wrote: >> >>> Runing "nant release quick rebuild" does indeed build every time. >>> >>> The Nant switches I was using were not working and I thank you for >>> pointing me in the right direction. >>> >>> Thanks for pointing me in the right direction. >>> >>> I'll keep Castle posted on the horn progress. >>> >>> 2009/3/22 Jonathon Rossi <[email protected]> >>> >>> What I had in quotes was exactly what I run. You don't need anything >>>> extra to run debug with tests for net-3.5. However, I do run with other >>>> switches for release and net-2.0. >>>> >>>> You can run: "nant quick rebuild" to build without tests, or "nant >>>> release quick rebuild" to build release without tests. >>>> >>>> >>>> On Sun, Mar 22, 2009 at 11:02 PM, Paul Cowan <[email protected]>wrote: >>>> >>>>> That is good to hear Jonathan. >>>>> >>>>> Can you give me an example of the switches you pass to nant in order to >>>>> build castle? >>>>> >>>>> 2009/3/22 Paul Cowan <[email protected]> >>>>> >>>>> >>>>>> 1). It has'nt moved to ruby, I have been experimenting with Ruby for >>>>>> an upcoming talk I am doing. I want to contrast the boo approach to the >>>>>> ruby/ironruby approach. The ruby stuff is in a branch where you can >>>>>> define >>>>>> build files in ruby or boo. The trunk is still boo. >>>>>> 2). When I build Castle, I never run the tests. I have to manually >>>>>> delete the projects that simply will not build. >>>>>> >>>>>> Is it safe to say that others do not experience this problem? >>>>>> >>>>>> Paul >>>>>> >>>>>> 2009/3/22 Ayende Rahien <[email protected]> >>>>>> >>>>>> a) when did horn move to ruby? b) you can try building it without the >>>>>>> tests, that should make it much easier at the end user site. since >>>>>>> running >>>>>>> the tests requires some setup on each machine (databases, mostly) >>>>>>> >>>>>>> >>>>>>> On Sun, Mar 22, 2009 at 8:51 AM, dagda1 <[email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> A few of us have started the following project named ‘horn’ to try >>>>>>>> and >>>>>>>> alleviate the pain from building the open source stack that many >>>>>>>> use: >>>>>>>> >>>>>>>> http://code.google.com/p/scotaltdotnet/ >>>>>>>> >>>>>>>> Think of it as a ruby gem like approach. >>>>>>>> >>>>>>>> We like many build from the trunk and we want to easily get a latest >>>>>>>> build when say something exciting or new like the latest version of >>>>>>>> Nhibernate or Castle is available. >>>>>>>> >>>>>>>> Obviously castle is a familiar choice with many developers and we >>>>>>>> are >>>>>>>> at the point in the project where we are trying to resolve >>>>>>>> dependencies between projects and components. >>>>>>>> >>>>>>>> We have a Dsl that describes the build information needed to >>>>>>>> retrieve >>>>>>>> and build a component. >>>>>>>> >>>>>>>> For instance if you take the horn project itself then we have the >>>>>>>> following build file: >>>>>>>> >>>>>>>> install :horn do >>>>>>>> description "A .NET build and dependency manager" >>>>>>>> build_with :msbuild, :frameworkVersion35, :buildfile => "src/ >>>>>>>> horn.sln" >>>>>>>> get_from :svn, http://scotaltdotnet.googlecode.com/svn/trunk/ >>>>>>>> >>>>>>>> dependency :log4net => "log4net" >>>>>>>> dependency :castle => "castle.core" >>>>>>>> end >>>>>>>> >>>>>>>> project.homepage "http://code.google.com/p/scotaltdotnet/"; >>>>>>>> project.forum " >>>>>>>> http://groups.google.co.uk/group/horn-development? >>>>>>>> hl=en <http://groups.google.co.uk/group/horn-development?%0Ahl=en>" >>>>>>>> project.contrib false >>>>>>>> >>>>>>>> If you look at this example, you can see that we are using msbuild >>>>>>>> to >>>>>>>> bulid horn and we are specifying 2 dependencies. We can resolve the >>>>>>>> log4net dependency as it has no dependencies. The other dependency >>>>>>>> mentioned in the DSL is: >>>>>>>> >>>>>>>> dependency :castle => "castle.core" >>>>>>>> >>>>>>>> The dependency hash specifies the :castle symbol as the parent >>>>>>>> folder >>>>>>>> where all the dsl build file is located and the “castle.core” is >>>>>>>> the .dll we are requesting. >>>>>>>> >>>>>>>> We want to have pretty much all of the castle components defined in >>>>>>>> one dsl build metadata file. >>>>>>>> >>>>>>>> We cannot build the castle stack using msbuild as for example, the >>>>>>>> asseblyinfo.cs file is created during the Nant build. >>>>>>>> >>>>>>>> The reason I am writing this is that I have never managed to build >>>>>>>> the >>>>>>>> castle stack without a hell of a lot of trouble. The default.build >>>>>>>> file to me seems a little out of date and references things like the >>>>>>>> remoting project which uses a really old version of NUnit to build. >>>>>>>> >>>>>>>> I have always had to manually hack into the default.build file in >>>>>>>> order to get it to build. >>>>>>>> >>>>>>>> I know this is just not my experience but is this unique to some of >>>>>>>> us >>>>>>>> and not all. >>>>>>>> >>>>>>>> We want to get buy in for horn and we can’t resolve the castle >>>>>>>> dependencies without being able to build it consistently. >>>>>>>> >>>>>>>> Can anyone give any advice to how we can reguarly build the Castle >>>>>>>> stack. >>>>>>>> >>>>>>>> Retrieving and building your .NET OS stack in a ruby gem type manner >>>>>>>> must appeal to most. >>>>>>>> >>>>>>>> Cheers >>>>>>>> >>>>>>>> Paul >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>> >>>> >>>> -- >>>> Jono >>>> >>>> >>>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
