I just figured it out. It was not a problem with the web references it was a problem with a diagnostics tracelistener switch set in the app.config, which was calling a windows file path, I changed that and it still didnt wouldnt work so I removed the tracelistener and all trace.write calls and the app runs without a hitch.
weird. Shawn Vose wrote: >That is what I initially thought so I did some tests, it isnt the case. >I removed all calls to the web reference and added the methods that were >being called within the reference to another dll. Everything works >fine(minus some other crazy stuff going on which I will figure out). I >will try and write a test to recreate it for a bug report because I >would rather use the web service than have to write a lib every time I >want to port to a *nix box. > >Paolo Molaro wrote: > > > >>On 09/19/06 Shawn Vose wrote: >> >> >> >> >>>I have an exe that I built using visual studio 2000 that runs with out a >>>hitch on mono. The exe takes a name of an assembly from the command line >>>and executes the said method from the command line using refelection. >>>The assembly that I am trying to fire works to a point. The break occurs >>>when I try to create an instance to a web service. >>> >>> >>> >>> >>[...] >> >> >> >> >>>INNER_EXCEPTION:System.Reflection.TargetInvocationException: Exception >>>has been thrown by the target of an invocation. ---> >>>System.IO.IOException: Sharing violation on path ./logs/IntegrationBus.log >>>in <0x0032a> System.IO.FileStream:.ctor (System.String name, FileMode >>>mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean >>>isAsync, Boolean anonymous) >>> >>> >>> >>> >>[...] >> >> >> >> >>>in <0x0003d> System.Diagnostics.TextWriterTraceListener:.ctor >>>(System.String fileName, System.String name) >>> >>>In the exception message it is telling me of an unknown method. Is there >>>a way to find out what this "unknown method"'s name is? >>> >>> >>> >>> >>The exception message is telling you that there is a sharing violation >>while opening the file "./logs/IntegrationBus.log". This probably means >>that another process has the file open already and the >>TextWriterTraceListener ctor wants to open it again (or there may be a >>bug in the code that keeps track of emulating the sharing policy of >>windows in the mono io-layer). >>Try removing the file, or file a bug report with a test case that >>reproduces the issue. >> >>lupus >> >> >> >> >> > > >_______________________________________________ >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
