Integrating the Mono debugger with Visual Studio sounds like a very good
thing to do. This way, you could possibly also debug Mono if your
application crashes.
It also makes sure you only need to install Mono in order to test it.
Of course, that requires the Mono debugger to be working on Windows
This is a bug. You can see the bug report here:
http://bugzilla.ximian.com/show_bug.cgi?id=77062
A solution is mentioned there: you need to set the LD_LIBRARY_PATH.
quote
I am not sure how this is supposed to work. Setting the LD_LIBRARY_PATH
helped however:
[EMAIL PROTECTED]:~$ export
Pressing ENTER in a single line textbox on a form that has a default
button causes an extra character to be added to the textbox instead of
the button being pressed.
Also, pressing backspace to remove this non-printable character leaves a
relic.
Thanks for filing the bug.
Pressing ENTER in a single line textbox on a form that has a default
button causes an extra character to be added to the textbox instead of
the button being pressed.
Also, pressing backspace to remove this non-printable character leaves a
relic.
Frederik.
Miguel de Icaza schreef:
I humbly
Rolf fixed some issues that were keeping ASP.NET applications written in
VB.NET from running. You may want to mention that support for VB.NET in
ASP.NET has improved.
Frederik
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
You'll need Mono 1.2.3 and most likely Mono from SVN. Try to get
yourself familiar with building mono from SVN on your Linux computer.
I would advise against prj2make. Try NAnt instead. It has the benefit of
helping cross-platform build: you can use the same build script on both
Linux and
Hi,
This is a rather new document I'm working on. It should get you started.
If you have issues, please let me know!
Getting Mono
Bootstrapping
You currently need to have the latest version of Mono installed on your
computer. To build Mono from SVN, you first need to have the Mono
