The issue i was referring to is actually CCNET-1130, but the problem
might be related. I'll try to find some time to review both issues for
Mono compatibility.

regards,

Daniel


On Mon, 24 Nov 2008 22:07:15 +0100
Daniel Hommel <[EMAIL PROTECTED]> wrote:

> 
> Maybe the fix for CCNET-1057 is not sufficient for running on mono.
> I'll put that on my TODO list. I had CC.Net working on Linux/Mono once
> but that was before the fix for CCNET-1057 was applied. I think we
> might need to distinguish between .NET and Mono to calculate the
> correct path.
> 
> regards,
> 
> Daniel
> 
> 
> On Mon, 24 Nov 2008 12:19:15 -0800
> Corey Graham <[EMAIL PROTECTED]> wrote:
> 
> > 
> > It looks like you are missing a drive letter. Have you tried
> > launching this from a simple DOS shell that is not a cygwin shell?
> > Cygwin interprets your drive letters differently.
> > 
> > Corey
> > 
> > Sent from my iPhone
> > 
> > On Nov 19, 2008, at 1:03 PM, Sam Umbach <[EMAIL PROTECTED]> wrote:
> > 
> > >
> > > I've seen some similar issues posted regarding running the
> > > webdashboard webapp under mono on linux, but I'm seeing a
> > > different error message under Windows.  Is anyone out there
> > > successfully running CCNet 1.4 webdashboard under Mono/XSP on
> > > Windows?
> > >
> > > * Windows XP Professional SP2
> > > * Mono 2.0.1 (mono-2.0.1-gtksharp-2.10.4-win32-1.exe)
> > > * CruiseControl.NET 1.4.1
> > >
> > > I launch XSP from the webdashboard directory:
> > >
> > > /cygdrive/c/CruiseControl.NET/webdashboard$ /cygdrive/c/Mono-2.0.1/ 
> > > bin/
> > > xsp
> > > xsp2
> > > Listening on address: 0.0.0.0
> > > Root directory: c:\CruiseControl.NET\webdashboard
> > > Listening on port: 8080 (non-secure)
> > > Hit Return to stop the server.
> > >
> > > When I hit the webdashboard URL at http://localhost:8080/, I get
> > > the following exception.  This looks similar to the issue
> > > reported in CCNET-1057
> > > (http://jira.public.thoughtworks.org/browse/CCNET-1057), but in
> > > my case the path is missing the drive letter (Path: :/
> > > DOCUME~1/..., should be Path: c:/DOCUME~1/...).  Launching XSP
> > > from a DOS shell also results in the same error.
> > >
> > > System.IO.IOException: Win32 IO returned ERROR_INVALID_NAME.
> > > Path: :/
> > > DOCUME~1/sumbach/LOCALS~1/Temp/sumbach-temp-aspnet-0/3e498371/
> > > assembly/ shadow/4ad927c1/3ac32d54_701a0a95_00000001
> > >  at System.IO.Directory.GetFileSystemEntries (System.String path,
> > > System.String searchPattern, FileAttributes mask, FileAttributes
> > > attrs) [0x00000]
> > >  at System.IO.Directory.GetFiles (System.String path,
> > > System.String searchPattern) [0x00000]
> > >  at Exortech.NetReflector.NetReflectorTypeTable.Add (System.String
> > > path, System.String searchPattern) [0x00000]
> > >  at
> > > ThoughtWorks. 
> > > CruiseControl. 
> > > WebDashboard.Configuration.DashboardConfigurationLoader.GetTypeTable
> > > () [0x00000]
> > >  at
> > > ThoughtWorks. 
> > > CruiseControl. 
> > > WebDashboard.Configuration.DashboardConfigurationLoader..ctor
> > > (Objection.NetReflectorPlugin.ObjectionNetReflectorInstantiator
> > > instantiator, IPhysicalApplicationPathProvider
> > > physicalApplicationPathProvider) [0x00000]
> > >  at
> > > ThoughtWorks. 
> > > CruiseControl. 
> > > WebDashboard.Configuration.CachingDashboardConfigurationLoader..ctor
> > > (ObjectSource objectSource, System.Web.HttpContext context)
> > > [0x00000] at
> > > ThoughtWorks. 
> > > CruiseControl. 
> > > WebDashboard. 
> > > Dashboard.CruiseObjectSourceInitializer.GetDashboardConfiguration
> > > (ObjectSource objectSource, System.Web.HttpContext context)
> > > [0x00000] at
> > > ThoughtWorks. 
> > > CruiseControl. 
> > > WebDashboard. 
> > > Dashboard.CruiseObjectSourceInitializer.SetupObjectSourceForRequest
> > > (System.Web.HttpContext context) [0x00000]
> > >  at
> > > ThoughtWorks. 
> > > CruiseControl.WebDashboard.MVC.ASPNET.HttpHandler.ProcessRequest
> > > (System.Web.HttpContext context) [0x00000]
> > >  at System.Web.HttpApplication+<Pipeline>c__Iterator5.MoveNext ()
> > > [0x00000]
> > >  at System.Web.HttpApplication.Tick () [0x00000]
> 

Reply via email to