Hi, I can reproduce it only for the trivial case: delete an assembly which is referenced by the app.
If you email me a zip/tar.gz with the assemblies, I'll have a look at the problem. Robert Travis Staloch wrote: > Robert, > > I'm still stuck with this. Sorry if you couldn't get my message last time, I > had one message where your email was the subject and one where my attached > words didn't make it through. > > Does anyone have any ideas why mkbundle on windows would be acting this way > with mono 1.17? > > Thanks, > > --Travis > > Travis Staloch wrote: >> I'm trying to use mkbundle on windows with Mono-1.1.16 and not having >> any luck. I'm running mkbundle as shown below. All of the dlls >> referenced by MyApp.exe are in the same directory as MyApp.exe. >> Thats also the directory where I'm running the mkbundle command from. > >>> mkbundle --deps MyApp.exe >> OS is: Windows Sources: 1 Auto-dependencies: True >> >> Unhandled Exception: System.IO.FileNotFoundException: MyAppCommon, >> Version=1.0.2441.695, Culture=neutral : MyAppCommon, >> Version=1.0.2441.695, Culture=neutral > > What happens if you call "mono MyApp.exe" from inside of this > directory? > > Robert > > > --------------------------------- > Stay in the know. Pulse on the new Yahoo.com. Check it out. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
