Cool. J
From: [email protected] [mailto:[email protected]] On Behalf Of Roelof Blom Sent: den 6 april 2009 15:59 To: [email protected] Subject: Re: Problems building, priorities of facilities. Latest trunk defaults to using nunit-console from SharedLibs\build\NUnit\bin, like in your patch but now for the entire project. Regarding the warning about NAnt 0.86b1: for .NET 3.5 it's better to use nightly builds (those are a lot newer than 0.86 beta!), I've made the warning in the build script more explicit. Cheers, Roelof. On Mon, Apr 6, 2009 at 7:25 AM, Henrik Feldt <[email protected]> wrote: >The facility has been moved, but its test cases continues to be a separated project. About the >error, it's an issue with NUnit. Use the version 2.2.8 of nunit to resolve it. I thought that was why people added /SharedLibs/build/NUnit/bin, but have I missed something here? Why isn't that added on its own, so that people don't have to run into this and fix it manually every time :D? Anyway, I patched that. See the attached file. Tried running, tests pass both from root and from the remoting folder should you want to build from there directly. There's also a funny thing, when the build tells me that I should use a newer version of nant, when I'm using 0.86b1, which is the latest... Why is that there? Rename the zip to .zip instead; google doesn't like executables because we might click them without knowing they are executable. (!) Regards, Henrik -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Henry Conceição Sent: den 6 april 2009 02:01 To: [email protected] Subject: Re: Problems building, priorities of facilities. inline On Sun, Apr 5, 2009 at 8:06 PM, Henrik Feldt <[email protected]> wrote: > Hello, > > > > Boldness added for your convenience to speed up reading ;). > > > > Problems building: > > 1. ActiveRecord tests, by default SQL Server 2008 doesn’t like > some of the syntax around “name”. I haven’t changed anything here, so > I mostly just disable that test case, but I guess I could select the > correct dialect and make it work. > > 2. > Castle.Facilities.Remoting.Tests.ConfigurableRegistrationTestCase.Clie > ntContainerConsumingRemoteComponents > fails with System.AppDomainUnloadedException: Attempted to access an > unloaded AppDomain. > All the rest of the test-cases after this also fail. The interesting > thing here is how there’s a .txt saying that facility has moved to > MicroKernel.Facilities when, clearly obviously it hasn’t had its > housewarming party yet, but is still getting tested. I added a > property in the build configuration file to disable testing of that > facility till it supposedly gets removed: deadremoting.test, so I can > disable it when testing the rest. Running the rest of the tests > afterwards succeed. What’s the status on this? Should I delete the old one and send a patch?? The facility has been moved, but its test cases continues to be a separated project. About the error, it's an issue with NUnit. Use the version 2.2.8 of nunit to resolve it. > > 3. When opening the solution in VS2008, there are 3-4 places > where libs have been referenced from GAC, where I try not to place > these libs which keep getting updated – anrControls, NHibernate and > Boo.Lang .. Parser .. Compiler in some of the project. I fixed this on > trunk and referenced from SharedLibs instead. Also NVelocity, I > couldn’t find in the NVelocity.dll file in the SharedLibs; why? So I > added it there. I’m submitting a patch for this in this e-mail. > Furthermore, the BrailTestSite isn’t signed by default which causes an > exception when running the brail tests. Looking in the solution, > there’s no link the CastleKey.sln. I added a link to this key and > tried the tests again (after first rebuilding the projects individually) and it passes then. > > 4. WcfFacility fails because I need to start a NetTcpPortSharing > (according to the exception message), so I guess I have to start that. > However, I’m not using that facility either, so I added exactly the > same switch as in remoting, albeit renamed, in the default.build file > there, so I can disable testing of it. > > 5. When disabling the above, I can build and all is good, all > tests pass. (so I run; nant –D:activerecord.test=false > –D:deadremoting.test=false > -D:wcfintegration.test=false) > > > > Other things: > > 1. I’ve created a component installer which allows you to > specify priorities when installing facilities. I did this because when > I launch my own facilities, they had some dependencies on the > components of each other, however, as far as I could see there was no > feature in the kernel to do this. Should I add it into the trunk and > send a patch? The question here is also, is there anyone who wants it? > > 2. What did you guys think about the FileTransaction I mailed > about before? Sending mail to Ernst Naezer bounced when using his > e-mail he’s using for this list. Does anybody have his e-mail so I can > talk to him directly? > > 3. Is there a release coming soon? > > Cheers, > > Henke > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
