On 21.07.2010 11:32, Tim Martin wrote: > On 20/07/2010 3:43 PM, Alexander Shulgin wrote: >> You're missing the --deps parameter, obviously. >> > > Thanks for the suggestion. I originally tried --deps, but it doesn't > work for me. I get the error message: > > Unhandled Exception: System.IO.FileNotFoundException: Could not load > file or assembly 'Foobar.Common.Support' or one of its dependencies. The > system cannot find the file specified. > File name: 'Foobar.Common.Support' > at System.AppDomain.Load (System.Reflection.AssemblyName assemblyRef, > System.Security.Policy.Evidence assemblySecurity) [0x00000] > at (wrapper remoting-invoke-with-check) System.AppDomain:Load > (System.Reflection.AssemblyName,System.Security.Policy.Evidence) > at System.AppDomain.Load (System.Reflection.AssemblyName assemblyRef) > [0x00000] > at (wrapper remoting-invoke-with-check) System.AppDomain:Load > (System.Reflection.AssemblyName) > at System.Reflection.Assembly.Load (System.Reflection.AssemblyName > assemblyRef) [0x00000] > at MakeBundle.QueueAssembly (System.Collections.ArrayList files, > System.String codebase) [0x00000] > at MakeBundle.Main (System.String[] args) [0x00000] > > But Foobar.Common.Support.dll exists in the current directory where I'm > trying to make the bundle, and if I explicitly list it on the command > line then it adds it without trouble. I tried mucking with the -L flag, > but that doesn't seem to help. I've analysed the dependencies of the DLL > in Windows, and the only non-core dependency is also present in the > directory. > > Any suggestions?
Sorry, not sure. May be it should be looking for `Foobar.Common.Support.dll' and not plain `Foobar.Common.Support'? You might need to check your assembly references. Otherwise, if it works by adding Foobar.Common.Support.dll on command line, why not try going this way? -- Alex _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
