Hehehe... Well, there are many reasons to wear kilts. =) Glad I was able to help.
Jeff. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of ChrisHolmes Sent: Friday, December 07, 2007 1:26 PM To: MbUnit.User Subject: MbUnit Re: CC.Net reports missing reference exception with MBUnit Holy crap - I just checked your blog Jeff. I met you at ALT.net! Who could miss the guy in the Kilt! Thanks for the help - we got our CC.Net server working last night and it's a thing of beauty now. We're really looking forward to taking advantage of all the new features in MbUnit. -Chris On Dec 6, 2:44 pm, "Jeff Brown" <[EMAIL PROTECTED]> wrote: > 2) You want to change the list of XSL files that appear in the > <buildReportBuildPlugin> section. Similarly if you want to change > which sections appear in emails (or the order in which they appear) > then you must edit the list of XSL files that appears in the > ccservice.exe.config and ccnet.exe.config files. > > Jeff. > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > On > > Behalf Of ChrisHolmes > Sent: Thursday, December 06, 2007 2:27 PM > To: MbUnit.User > Subject: MbUnit Re: CC.Net reports missing reference exception with > MBUnit > > Thanks Jeff! > > (1) and (3) helped some. We didn't have the merge task inside the > publishers section, and running the service using NET START from the > command line has enabled it to write the file. > > (2) I can't figure out though. The dashboard keeps inserting the whole > summary into the build report page. Any specific lines I should look > at in the dashboard config? I've commented out so much stuff and yet > still no affect. > > -Chris > > On Dec 6, 1:59 pm, Jeff Brown <[EMAIL PROTECTED]> wrote: > > Yes, "no particular difficulties". Perhaps I just got lucky. But > > there are some gotchas in CCNet to beware of. > > > 1) The MbUnit output needs to be merged into the CCNet artifacts. > > The merge task must be in the publishers section of your CCNet > > configuration. It will not work otherwise. > > > 2) You can configure which sections appear by editing the sections > > in the dashboard.config file. > > > 3) There could be some permissions problems writing to the file > > system when CCNet is running the build script as a Windows service. > > Try running CCNet as yourself from the command-line (using > > CCServer.exe) just to see. > > > Jeff. > > > -----Original Message----- > > From: [email protected] > > [mailto:[EMAIL PROTECTED] > > > On Behalf Of ChrisHolmes > > Sent: Thursday, December 06, 2007 1:26 PM > > To: MbUnit.User > > Subject: MbUnit Re: CC.Net reports missing reference exception with > > MBUnit > > > Wow... "no particular difficulties". I'd love to know how you pull > > that off (I'm serious, not facetious). It's been nothing but two > > days of hell for us to try and get MBUnit to work with Cruise > > Control (via > > MSBuild) > > > I've got a number of problems. Let me enumerate them, and maybe you > > folks can provide some answers: > > > (1) We experience the most difficultly when a unit test fails. The > > CC Dashboard doesn't tell us anything other than "Build Failed". It > > says there are zero unit test and no unit tests have been run. > > > Tests run: 0, Failures: 0, Not run: 0, Time: 0 seconds No Tests Run > > This project doesn't have any tests > > > When we click on the MBUnit Details or MBUnit Summary sections in > > the left hand link menu, those pages are empty. Also, when we check > > the output xml file that MBUnit is supposed to generate the file > > system shows it hasn't been updated. It is like a failure in that > > Task prevents it from properly writing out the results to XML. This > > is not the behavior we would expect, and it is not how CC.Net works with NUnit. > > > (2) When no unit tests fail, the build succeeds, but both the > > Summary and the Details get parsed into the main CC.Net page. We > > just want the Summary. When we click on the Summary link on the left > > hand menu, we get just the Summary. When we click no Details, we get > > just the Details page. But on the main page we get both. > > > (3) If I run our build script from the command line with a failing > > unit test,it DOES update the xml output file. > > > None of this makes any sense to me. We're using CC.Net version > > 1.3.0.3051. If anyone has a clue why this behavior is happening, > > please let me know. > > > -Chris > > > On Dec 5, 11:47 pm, "Jeff Brown" <[EMAIL PROTECTED]> wrote: > > > It's not clear to me from this description what may be wrong. > > > > I've not had any particular difficulties getting MbUnit to work in > > CCNet. > > > > Jeff, > > > > -----Original Message----- > > > From: [email protected] > > > [mailto:[EMAIL PROTECTED] > > > > On > > > > Behalf Of ChrisHolmes > > > Sent: Wednesday, December 05, 2007 10:28 AM > > > To: MbUnit.User > > > Subject: MbUnit CC.Net reports missing reference exception with > > > MBUnit > > > > We're currently in the process of replaceing NUnit with MBUnit. I > > > thought this would be simple: just remove references to NUnit in > > > the test projects and add references to MBUnit. > > > > The problem is that CruiseControl build fails. I've got our CC.Net > > > build stripped down to the bare minimum: just compile the solution > > > file with msbuild. Still no luck. > > > > I can run msbuild to compile the application from the command line > > > on the build server and it works fine. It's only through CC.NET > > > that it > > is failing. > > > > Any tips? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" 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/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
