Yes, you should compile your dll in the environment in which it will run, or
use a cross compiler targeted to that environment.
If you don't have the source I suspect you are out of luck. There is much
more to it than simply fiddling with the headers. You may be able to use
something like wine,
I can show the threads associated with my process using ps or top, but not
their names.
Should I expect to be able to show the names of threads that were named in
mono using myThread.Name = whatever?
If so, how?
Or is this information not available at that level?
Thanks
--
View this
Greetings,
I'm new to using mono. I have a Windows application that I have developed
in C# with some P/Invoke calls to an unmanaged dll. I am attempting to run
this thing in a Linux environment, but am having issues with the unamanged
calls (exact error is given below). After a fair amount of
Hi,
I just had the same issue. Did you resolve it? If so, how?
Best Regards
Henrik Hagen
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hello,
It seems that the assembly System.DirectoryServices.Protocols
is not installed in the GAC. Is it a real problem or just my mistake?
Best regards,
--
Raphael Boissel
EPITA 2014
___
Mono-devel-list mailing list
Hi
I have updated to Mono 3.2.8 on Windows and is unable to print with Gtk#
(gtk3). Everything else is working with Gtk#, but when trying to print,
not print dialog is opened and the program hangs.
* I have [STAThread] on my main function.
* gtk3-demo.exe is able to print.
* I have testet with
On Mar 19, 2014, at 12:33 AM, Greg gregorymors...@gmail.com wrote:
I believe the calls are failing because the unamanged dll has not been
compiled in the native environment. Is this true, or should mono be able to
handle unmanaged dlls that were compiled in Windows?
Mono does not support
If that isn’t possible, you should look into using Wine. Mono should run atop
Wine (last I heard…), so this may be a viable solution for you.
The default for Wine nowadays (since 1.5 or so) is to install Mono
automatically (for various reasons, it uses a special Windows build)
and use it to
AFAIK Mono doesn't implement this specific library. Code was just stubbed 5
years ago as seen in
https://github.com/mono/mono/blob/master/mcs/class/System.DirectoryServices.Protocols/System.DirectoryServices.Protocols.dll.sources
Rafael Teixeira
O..:.)
On Sat, Mar 22, 2014 at 7:51 PM,
