Re: [Mono-list] P/Invoke, Mono, .NET and Windows XP funny platform

2005-06-10 Thread Jonathan Pryor
Your fundamental problem is that you're targeting Windows XP. Ha ha only serious. (A colloquialism for "that's funny, but I'm serious too...") The slightly longer explanation is here: http://www.mono-project.com/Interop_with_Native_Libraries#Windows_DLL_Search_Path The real explanatio

RE: [Mono-list] P/Invoke, Mono, .NET and Windows XP funny platform

2005-06-10 Thread Jeroen Frijters
Jonathan Pryor wrote: > Your fundamental problem is that you're targeting Windows XP. > > The real explanation is that Win32 is broken when it comes to > supporting multiple different versions of the "same" library. > Absolutely, fundamentally, *broken*. More to the point, it > doesn't support t

Re: [Mono-list] P/Invoke, Mono, .NET and Windows XP funny platform

2005-06-13 Thread Francis Brosnan Blázquez
First of all, thanks for your reply. It have been really productive. Some issues about your reply: Your fundamental problem is that you're targeting Windows XP. Ha ha only serious. (A colloquialism for "that's funny, but I'm serious too...") The slightly longer explanation is here:

Re: [Mono-list] P/Invoke, Mono, .NET and Windows XP funny platform

2005-06-13 Thread Jonathan Pryor
On Mon, 2005-06-13 at 16:30 +0200, Francis Brosnan Blázquez wrote: > About the library renaming issue. > > Renaming library basename could help us to find a solution to build > application that can run on top of mono and .NET runtime ensuring the > libraries the af-arch framework relies on will a