[MonoDevelop] Re: Monodevelop-list Digest, Vol 11, Issue 24 trusted sender for your account)

Lluis Sanchez lluis at ximian.com
Mon Mar 20 05:51:09 EST 2006

El jue, 16-03-2006 a las 22:45 +1000,
monodevelop-list.1.tracyanne at spamgourmet.com escribió:
> I have a small Windows forms project that was launching from Monodevelop
> without any issues with previous versions of the Mono Framework. I am
> currently running Mono_1.1.13_4
> I get the following error:
> Exception occurred: Argument cannot be null.
> Parameter name: path2
> System.ArgumentNullException: Argument cannot be null.
> Parameter name: path2
> in <0x0018f> System.IO.Path:Combine (System.String path1, System.String
> path2)
> in <0x000c1> MonoDevelop.Projects.Project:CopyReferencesToOutputPath
> (System.String destPath, Boolean force)
> in <0x0004d> MonoDevelop.Projects.Project:CopyReferencesToOutputPath
> (Boolean force)
> in <0x00041> MonoDevelop.Projects.DotNetProject:DoExecute
> (IProgressMonitor monitor, MonoDevelop.Projects.ExecutionContext
> context)
> in <0x00165> MonoDevelop.Projects.Project:Execute (IProgressMonitor
> monitor, MonoDevelop.Projects.ExecutionContext context)
> in <0x00073> MonoDevelop.Projects.Combine:Execute (IProgressMonitor
> monitor, MonoDevelop.Projects.ExecutionContext context)
> in <0x00165>
> MonoDevelop.Ide.Gui.ProjectOperations:ExecuteCombineEntryAsync
> (System.Object ob)
> what does this mean?

This exception means that Path.Combine is being called with a null value
as second parameter, and that this is not allowed.

I don't see how a Mono upgrade could be the cause of this exception. If
you have a sample project I can use to reproduce the crash, that would
be helpful.

> regards
> Tracy Barlow
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list

More information about the Monodevelop-list mailing list