Re: [Mono-list] Future of JIT
Hello, Have you considered VCODE/ICODE to become a basis for your JIT backend? We did, early on. We decided against it for licensing reasons, and because it is not really a great technology. A cool hack, yes. Hopefully when the new JIT engine is release, we will release some technical documents on it as well. Miguel. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] array access
On 02/02/03 Sterling Hughes wrote: I'm trying to dynamically determine the type of elements stored within an object of MONO_TYPE_ARRAY, is there anyway to do this? MonoClass *elem_class = mono_object_class (array_object)-element_class; The same code works for vectors, too (MONO_TYPE_SZARRAY). lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Problem with Process.GetCurrentProcess
On 02/01/03 Artur Karazniewicz wrote: Since few days I have problem with Process.GetCurrentProcess - before it works fine but now: [...] Please file a bug in bugzilla.ximian.com so that we can keep track of it. Thanks. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] gtk-sharp and gc
On 02/01/03 Martin Baulig wrote: Is it possible to run gtk-sharp without a garbage collection enabled, I have still not been able to install the garbage collector. Mono complains about GCHandles when I run a gtk-sharp program, and they used to work before Please, explain what are the issues you had with installing the garbage collector. Building mono e/o gtk-sharp without GC support is only a bad workaround that currently should be needed only to run with libwine. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Various problems in ADO.NET
Here am I again. Finally I succeed using MySqlDataAdapter.Update().
Finally I found that in:
protected virtual int Update (DataRow[] dataRows, DataTableMapping
tableMapping)
it says:
string dsColumnName = columnMappings [parameter.SourceColumn].DataSetColumn;
But columnMappings is an empty collection.
If I use string dsColumnName = parameter.SourceColumn; instead, then it can
continue to run.
If I fix this together with the BaseColumnName fix and Aleksey Demakov's patch
(not yet in CVS), then this is the first time I succeed using
MySqlDataAdapter.Update() to update the modified DataTable/DataRow values under
mono with the same code as in the Microsoft Runtime.
Regards,
Alan
- Original Message -
From: Alan Tam [EMAIL PROTECTED]
To: Mono-List [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 6:24 PM
Subject: Re: [Mono-list] Various problems in ADO.NET
Dear All,
I've further traced into the source and found that:
In private void BuildSchema (IDataReader reader, DataTable table, SchemaType
schemaType)
of mcs/class/System.Data/System.Data.Common/DbDataAdapter.cs
It says:
if (schemaRow [BaseColumnName].Equals (DBNull.Value))
sourceColumnName = DefaultSourceColumnName;
else
sourceColumnName = (string) schemaRow [BaseColumnName];
The BaseColumnName field in the Schema table is Null, but the ColumnName
field
in the table is the correct column name. May I know if it is the problem of
ByteFX or the mono class library, i.e. is BaseColumnName really the field we
want?
Thank you.
Regards,
Alan
- Original Message -
From: Alan Tam [EMAIL PROTECTED]
To: Mono-List [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 3:33 PM
Subject: [Mono-list] Various problems in ADO.NET
I used this program in both csc/Windows and mcs/Linux:
using System;
using System.Data;
using ByteFX.Data.MySQLClient;
public class Test {
public static void Main() {
string connectionString = ...;
MySQLConnection myConnection = new MySQLConnection(connectionString);
myConnection.Open();
DataSet ds = new DataSet(PE);
MySQLDataAdapter adpOE = new MySQLDataAdapter();
adpOE.SelectCommand = new MySQLCommand(SELECT * FROM PE,
myConnection);
adpOE.Fill(ds, PE);
ds.WriteXmlSchema(PE.xml);
}
}
This is Linux output:
?xml version=1.0?
xs:schema targetNamespace= xmlns:mstns= xmlns=
xmlns:msdata=urn:schemas-microsoft-com:xml-msdata
attributeFormDefault=qualified elementFormDefault=qualified
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xs:element name=PE msdata:IsDataSet=true msdata:Locale=iv
xs:complexType
xs:choice maxOccurs=unbounded
xs:element name=PE
xs:complexType
xs:sequence
xs:element name=Column type=xs:string minOccurs=0 /
xs:element name=Column1 type=xs:string minOccurs=0 /
xs:element name=Column2 type=xs:string minOccurs=0 /
xs:element name=Column3 type=xs:string minOccurs=0 /
xs:element name=Column4 type=xs:string minOccurs=0 /
xs:element name=Column5 type=xs:string minOccurs=0 /
xs:element name=Column6 type=xs:string minOccurs=0 /
xs:element name=Column7 type=xs:
This is Windows output:
?xml version=1.0 standalone=yes?
xs:schema id=PE xmlns= xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:msdata=urn:schemas-microsoft-com:xml-msdata
xs:element name=PE msdata:IsDataSet=true msdata:Locale=zh-HK
xs:complexType
xs:choice maxOccurs=unbounded
xs:element name=PE
xs:complexType
xs:sequence
xs:element name=PEID type=xs:int minOccurs=0 /
xs:element name=EUID type=xs:int minOccurs=0 /
xs:element name=Heading type=xs:string minOccurs=0 /
xs:element name=DTFrom type=xs:dateTime minOccurs=0 /
xs:element name=DTTo type=xs:dateTime minOccurs=0 /
xs:element name=RepeatFreq type=xs:int minOccurs=0 /
xs:element name=RepeatTimes type=xs:int minOccurs=0 /
xs:element name=Venue type=xs:string minOccurs=0 /
xs:element name=ImportType type=xs:int minOccurs=0 /
/xs:sequence
/xs:complexType
/xs:element
/xs:choice
/xs:complexType
/xs:element
/xs:schema
The Linux output contains errors on:
1. The file truncates the last 1024 byte octet.
2. The column names are all missing
3. The column types are all wrong.
May I know are they all bugs?
Regards,
Alan
___
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
Re: [Mono-list] Mapping PHP and Mono
Hi all, En réponse à Sterling Hughes [EMAIL PROTECTED]: Hi, I'm working on making mono and php talk with each other, I figure since PHP# is probably a way off, it should be easy enough to use mono's C api to create overloaded objects. Isn't this the purpose of the PHP extension ext/rpc/dotnet? More here: http://cvs.php.net/cvs.php/php4/ext/rpc/dotnet http://cvs.php.net/co.php/php4/ext/rpc/dotnet/README?r=1.1 http://cvs.php.net/co.php/php4/ext/rpc/dotnet/README?r=1.1.16.1 They provide a short sample : ?php $stack = new DOTNET(mscorlib,System.Collections.Stack); $stack-Push(.Net); $stack-Push(Hello ); echo $stack-Pop() . $stack-Pop(); ? It's two years old, in experimental status, and doesn't seem to be very active, but... Regards, Christophe Lauer -- Christophe Lauer : http://clauer.free.fr - mailto:[EMAIL PROTECTED] Le site de la communauté .NET Francophone : http://www.dotnet-fr.org/ ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
On 02/01/03 Adam Treat wrote: I don't see why this should be about 'Adam wanting to make this happen' because this concerns the entire Mono community. Right now, mono technical discussion is going on behind a closed list that is not open to all mono developers. This is a matter of openness. Technical discussions happen where people feel confortable sending the first mail in the thread. It doesn't matter at all if another list is set up, there is already mono-list that has served as a wide forum. If somebody thinks a mail is appropriate for a wider audience than the core mono hackers, he should send it to mono-list until mono-devel is setup. Personally, I think there is no pressing need for mono-devel until the aumount of non-developer mail on mono-list makes the real developers unsubscribe from it:-) Something that is likely to heppen in a few months, though, with the first stable release of mono. Until that time, we'll enjoy your technical contributions on mono-list. Cheers. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
On 02/01/03 Adam Treat wrote: On Saturday 01 February 2003 07:37 pm, Miguel de Icaza wrote: No. Many other people would be subscribed to mono-devel-list, those sharing your same interests for example. BTW, what is the policy for exclusion from mono-hackers? Does this include Adam, this was already explained to you both on IRC an on this list. The policy for inclusion is very easy: do something for mono. Miguel has handed out subscriptions to the list and cvs accounts very liberally. Your exclusion has very little to do with your interest in others CLRs (pnet uses my own code and I'm still subscribed to mono-hackers:-). The mono-hackers access is a matter of trust. You lost the trust when you proposed to fork the code in the mono assemblies. Now, you can argue that that wasn't a good reason for losing trust in you since you have been a user/helper of mono from almost the very beginning. The fact is, though, that since then, you have done _nothing_ to regain the trust. And some of your mails don't help either, like this one, because the questions here where already publically answered on the list, so it looks like you're just trying to stir things instead of helping the project. I know it has been frustrating for you, but don't think it's any less frustrating for us. Thanks. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Compile error with current cvs
Hi,
I've been tracking down the source of the problem, and it seems to be in
autoconf.
The script mono-build-w32.sh selects the stable version of autoconf, which
generates a configure script that fails to detect gc.h, due to a problem
already pointed out by Francisco Figueiredo some mails ago. This is the
output in config.log:
configure:6525:
gcc -mno-cygwin -E -I/home/Lluis/install/include -DGC_WIN32_THREADS -DWIN32_
THREADS conftest.c /dev/null 2conftest.out
In file included from configure:6521:
/home/Lluis/install/include/gc/gc.h:61:1: warning: GC_WIN32_THREADS
redefined
conftest.c:1:1: warning: this is the location of the previous definition
configure: failed program was:
#line 6520 configure
#include confdefs.h
#include gc/gc.h
This problem can be solved by commenting the #define GC_WIN32_THREADS in
gc.h. Then, it compiles.
On the other hand, the script autogen.sh does not select the stable version
of autoconf, so when it is not executed through mono-build-w32.sh, it uses
the devel version to generate the configure script. This script does not
fail to detect gc.h as far as CPPFLAGS is set to my install/include
directory. However, the libtool script generated by this configure script is
unable to link the jit, since it generates all those undefined reference
errors.
So to compile using autogen.h I had to include this in the script:
CPPFLAGS=$CPPFLAGS -I/home/Lluis/install/include
LDFLAGS=$LDFLAGS -L/home/Lluis/install/lib
export CPPFLAGS
export LDFLAGS
if [ ! -z ${AUTO_STABLE} -o -e /usr/autotool/stable ]; then
export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
export AUTO_DEVEL=${AUTO_STABLE}
fi
Well, I've been able to compile and install... and now I get this when error
when running mono:
** ERROR **: file jit.c: line 4101 (mono_get_lmf_addr): should not be
reached
But that's another problem ...
Regards,
Lluis.
- Original Message -
From: Gonzalo Paniagua Javier [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 02, 2003 11:33 PM
Subject: Re: [Mono-list] Compile error with current cvs
El vie, 31-01-2003 a las 18:29, Lluis Sanchez escribió:
*** Warning: linker path does not have real file for library -lgc.
*** I have the capability to make that library automatically link in
when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libgc but no candidates were found. (...for file magic test)
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.
I also get this warning.
.libs/win32-exception.o(.text+0x26): In function `seh_handler':
/home/Lluis/mono/mono/jit/win32-exception.c:51: undefined reference to
`_g_malloc'
.libs/codegen-x86.o(.text+0x3241): In function `mono_burg_emit_16':
/home/Lluis/mono/mono/jit/codegen-x86.c:1257: undefined reference to
`__assert'
.libs/codegen-x86.o(.text+0x3269):/home/Lluis/mono/mono/jit/codegen-x86.c:12
57: undefined reference to `__assert'
.libs/codegen-x86.o(.text+0x330c):/home/Lluis/mono/mono/jit/codegen-x86.c:12
57: undefined reference to `__assert'
.libs/codegen-x86.o(.text+0x4227): In function `mono_burg_emit_23':
/home/Lluis/mono/mono/jit/codegen-x86.c:1385: undefined reference to
`_g_log'
.libs/codegen-x86.o(.text+0x5495): In function `mono_burg_emit_26':
/home/Lluis/mono/mono/jit/codegen-x86.c:1482: undefined reference to
`__assert'
... and so on.
I have gc.dll (the one from libgc-6.1-dev.zip) copied in my install/lib
folder, and all gc headers in install/include/gc.
...but this looks like another problem. Do you have glib2 installed and
PKG_CONFIG_PATH properly set?
-Gonzalo
___
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
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
On 02/03/03 Adam Treat wrote: Adam, this was already explained to you both on IRC an on this list. The policy for inclusion is very easy: do something for mono. Miguel has handed out subscriptions to the list and cvs accounts very liberally. I have already 'done something for mono' in case you haven't noticed. Just I know, that's the reason you were on the list in the first place, nobody has ever denied that. In the same mail you replied to, I said you helped mono since the beginning, trying to misrepresent my views won't help your cause. Your exclusion has very little to do with your interest in others CLRs (pnet uses my own code and I'm still subscribed to mono-hackers:-). The mono-hackers access is a matter of trust. You lost the trust when you proposed to fork the code in the mono assemblies. This again. I never proposed to fork the code despite your contentions to the contrary. Some more context ... one day while lurking in the Portable.NET IRC channel I asked about the status of Portable.NET's System.Xml. After receiving the answer that it was incapable of generating the Qt# bindings I suggested that Portable.NET use Mono's System.Xml instead of duplicating the dotgnu-2002-11-03.log: [07:23] t3rmin4t0r we could use other licenses outside pnetlib [07:23] t3rmin4t0r or fork mono's System.Xml [07:23] manyoso well, mono's System.Xml is X11 so we should be able to relicense it with GPL+Linking [07:24] manyoso yah, i think that sounds good [...] [07:25] manyoso i think forking System.Xml is a good idea, but then we'd also want to patch as mono's System.Xml is improved I'm not a native english speaker, but in the free software world the word 'fork' has a very precise meaning. When you also talk about relicensing the forked code with an incompatible license, that means that fixes and enhancements can't be folded back: this is as bad a fork as you can get. effort. This is entirely analogous (as I've pointed out to you and to Miguel in numerous conversations and have yet to hear a reason why this is considered 'forking') to Mono's inclusion of Portable.NET's I18N libraries. No, it's completely different. The I18N code was kindly donated by Rhys under the X11 license: the code is not forked. In mono we have just a copy and we send back to Rhys all the changes done there (that aren't irrelevant to him, such as integration in the mono build setup). We're not relicensing the code to make it incompatible with the pnet codebase. In fact, Miguel has publicly stated that Portable.NET, DotGNU, Rotor, Intel, Evil Company are all welcome to work on and use Mono's class libraries (this The license allows that. The license doesn't allow them to pretend to have access to the mono-hackers list. was the reason stated for the X11 license change) so I find this issue of 'forking' to be dubious. Anyways, I've asked for clarification on what Miguel would like done WRT System.Xml and have explained that I never wished to 'fork' any of Mono's libraries and this has been met with near silence. We talked about this on IRC and you said your words (quoted above) have been misunderstood (despite them being quite clear in the meaning). But once you loose trust on some people, it takes some effort to gain it back, it's not as simple as saying that what you said was not what you wanted to say. And instead of patches, bug reports, suggestions and the like, what did we get? Flamewars on mono-list :-( The fact is, though, that since then, you have done _nothing_ to regain the trust. Why should I continue to contribute when it is so readily apparent that Miguel is interested in excluding me completely. Miguel doesn't want you excluded, he even told you on IRC that if you start contributing again it would raise significantly the priority of setting up the mono-devel list and making it an effective list for mono developers. I have not seen Mono do _anything_ to regain my trust. Mono doesn't exist as a person, so I'm not sure what that would mean. If I lost your trust, let me know privately what I should do to gain it back (hey, if you ever travel near Venice or Padua here in Italy, be sure to send me mail and we'll share a bottle of wine:-). If you have similar issues with someone else in the project, do it privately, a public mailing list is not the best medium for settling personal issues. If you can't reconcile the positions, ignore some people and carry on with your contributions, like many people do in large projects. Cheers. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Compile error with current cvs
El lun, 03-02-2003 a las 16:17, Lluis Sanchez escribió:
configure:6525:
gcc -mno-cygwin -E -I/home/Lluis/install/include -DGC_WIN32_THREADS -DWIN32_
THREADS conftest.c /dev/null 2conftest.out
In file included from configure:6521:
/home/Lluis/install/include/gc/gc.h:61:1: warning: GC_WIN32_THREADS
redefined
conftest.c:1:1: warning: this is the location of the previous definition
configure: failed program was:
#line 6520 configure
#include confdefs.h
#include gc/gc.h
This problem can be solved by commenting the #define GC_WIN32_THREADS in
gc.h. Then, it compiles.
On the other hand, the script autogen.sh does not select the stable version
of autoconf, so when it is not executed through mono-build-w32.sh, it uses
the devel version to generate the configure script. This script does not
fail to detect gc.h as far as CPPFLAGS is set to my install/include
directory. However, the libtool script generated by this configure script is
unable to link the jit, since it generates all those undefined reference
errors.
So to compile using autogen.h I had to include this in the script:
CPPFLAGS=$CPPFLAGS -I/home/Lluis/install/include
LDFLAGS=$LDFLAGS -L/home/Lluis/install/lib
export CPPFLAGS
export LDFLAGS
if [ ! -z ${AUTO_STABLE} -o -e /usr/autotool/stable ]; then
export AUTO_STABLE=${AUTO_STABLE:-/usr/autotool/stable}
export AUTO_DEVEL=${AUTO_STABLE}
fi
Well, I've been able to compile and install... and now I get this when error
when running mono:
** ERROR **: file jit.c: line 4101 (mono_get_lmf_addr): should not be
reached
But that's another problem ...
This is the problem that I fixed when I added -DWIN32_THREADS. Sometimes
(i didn't investigate further) the GC_API #define wasn't being defined
properly (lacked dllimport) because WIN32_THREADS was not always defined
(!?). This causes a SIGSEGV when mono runtime accesses GC variables such
as GC_finalize_on_demand.
If we fix the problem without using -DWIN32_THREADS... Can you check if
defining _DLL and removing WIN32_THREADS work?
Btw, I'm using gc6.1 headers and dll and didn't run into the problems
you have.
-Gonzalo
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
Adam Treat [EMAIL PROTECTED] writes: Why should I continue to contribute when it is so readily apparent that Miguel is interested in excluding me completely. I have not seen Mono do _anything_ to regain my trust. Ok, so far this whole discussion was about you wanting to join a private mailing list of the Mono project. Miguel as the project leader excluded you from the list and as the project leader, it's his decision to do so. He also offered you a simple solution to the problem by providing that GNU Mailman patch which makes things work for everyone. Everything you did so far was complaining and wasting everybody's time, so can we please stop this discussion or at least move it into private mail (where people can decide just to ignore it) instead of spamming a public mailing list with such a silly discussion. Thanks. -- Martin Baulig [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
--- Paolo Molaro [EMAIL PROTECTED] wrote: On 02/03/03 Adam Treat wrote: Adam, this was already explained to you both on IRC an on this list. The policy for inclusion is very easy: do something for mono. Miguel has handed out subscriptions to the list and cvs accounts very liberally. I have already 'done something for mono' in case you haven't noticed. Just I know, that's the reason you were on the list in the first place, nobody has ever denied that. In the same mail you replied to, I said you helped mono since the beginning, trying to misrepresent my views won't help your cause. You said, 'policy for inclusion is very easy: do something for mono' ... if this were the case then I would be included. This is not the case. So when you say that is the 'policy' and you also acknowledge that I've 'done something for mono' ... hence the inevitable question 'then why am I not on the list'? I am not trying to misrepresent your views, I am just struggling to understand why you would say this is the 'policy' when you acknowledge that I've 'done something for mono'. If I've misrepresented your views then I apologize, but please do clarify. Your exclusion has very little to do with your interest in others CLRs (pnet uses my own code and I'm still subscribed to mono-hackers:-). The mono-hackers access is a matter of trust. You lost the trust when you proposed to fork the code in the mono assemblies. This again. I never proposed to fork the code despite your contentions to the contrary. Some more context ... one day while lurking in the Portable.NET IRC channel I asked about the status of Portable.NET's System.Xml. After receiving the answer that it was incapable of generating the Qt# bindings I suggested that Portable.NET use Mono's System.Xml instead of duplicating the dotgnu-2002-11-03.log: [07:23] t3rmin4t0r we could use other licenses outside pnetlib [07:23] t3rmin4t0r or fork mono's System.Xml [07:23] manyoso well, mono's System.Xml is X11 so we should be able to relicense it with GPL+Linking [07:24] manyoso yah, i think that sounds good [...] [07:25] manyoso i think forking System.Xml is a good idea, but then we'd also want to patch as mono's System.Xml is improved I'm not a native english speaker, but in the free software world the word 'fork' has a very precise meaning. When you also talk about relicensing the forked code with an incompatible license, that means that fixes and enhancements can't be folded back: this is as bad a fork as you can get. effort. This is entirely analogous (as I've pointed out to you and to Miguel in numerous conversations and have yet to hear a reason why this is considered 'forking') to Mono's inclusion of Portable.NET's I18N libraries. No, it's completely different. The I18N code was kindly donated by Rhys under the X11 license: the code is not forked. In mono we have just a copy and we send back to Rhys all the changes done there (that aren't irrelevant to him, such as integration in the mono build setup). We're not relicensing the code to make it incompatible with the pnet codebase. dotgnu-2002-11-25.log: [09:42] t3rmin4t0r manyoso: are you game to port mono's System.Xml to pnet ? [09:42] manyoso am interested in that [09:42] manyoso i can take a look at that soon [09:42] manyoso am working on Binge at the moment [09:43] manyoso when it does work, i think we should maintain it in pnet's cvs and mail patches back and forth alla the i8ln libs dotgnu-2002-11-29.log: [05:36] manyoso t3rmin4t0r: i've talked to lupus about copying System.Xml into pnet [05:36] manyoso he has no problem as long as pnet sends fixes/patches/additions back to mono-list when something changes [05:37] manyoso kinda like they do with the i18n libs [05:38] manyoso so for everything to be good pnet'd have to license all fixes/patches/additions back to mono ... [05:38] manyoso t3rmin4t0r: you think that'll be an issue? [05:38] t3rmin4t0r manyoso: we already licensed some of *our* code already to mono [05:38] raciel manyoso: is there troubles with System.Xml ? [05:38] manyoso cool. sounds good. [05:38] manyoso that's what i thought, i just wanted to make sure [05:39] manyoso raciel: no, no troubles. am just talking about reusing the Mono System.Xml in pnet When I said the above I was not thinking of maintaining an incompatible change. I was only concerned with pnet supporting our binding generator. I've since then clarified this with Miguel and with you and all of this settled. Mono's System.Xml was not forked. If this is reason enough for you and/or Miguel to lose trust in me, then ok ... *sigh*. The current dispute really has nothing to do with this anyway. As I've already said ***I am not asking for miguel to let me in on his secrets*** I am only asking to participate in developer discussions about Mono. Once again, this was settled and I dropped it completely. I am only asking
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
--- Martin Baulig [EMAIL PROTECTED] wrote: Adam Treat [EMAIL PROTECTED] writes: Why should I continue to contribute when it is so readily apparent that Miguel is interested in excluding me completely. I have not seen Mono do _anything_ to regain my trust. Ok, so far this whole discussion was about you wanting to join a private mailing list of the Mono project. Miguel as the project leader excluded you from the list and as the project leader, it's his decision to do so. He also offered you a simple solution to the problem by providing that GNU Mailman patch which makes things work for everyone. Ok, could you please reread this thread. I am not asking to join mono-hackers again. I simply wish to be included in the development discussion of Mono. If Miguel wishes to use mono-hackers for relating secrets and confidential information then ok, please setup a list for the open discussion. One list for open development discussion and one list for Ximian secrets and confidential information about Mono. Already agreed to. Everything you did so far was complaining and wasting everybody's time, so can we please stop this discussion or at least move it into private mail (where people can decide just to ignore it) instead of spamming a public mailing list with such a silly discussion. No, that is not everything I've done. I am asking for Miguel to follow through on something he has already agreed to. If you do not wish to see this thread continue then don't misstate what I have said and then expect me to drop it. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Extending the framework - Masked Text Box
Hello, First I must say that I enjoy being a bit of a lurker on this list. Here is the deal. When developingapps in C# or VB.NET there is no "masked textbox" availablein the standard (MS) framework. When searching for this on Goggle, one sees quite a few people looking for this functionality. Anyway, my brother wrote one that inherits from text box and implements all of the things that people have come to expect from a masked textbox along with other nice enhancements. He would like to contribute his code to the Mono project. He asked me if I (being a member of this list) would find out how to get the code submitted. I don't know if this is the appropriate place to ask this question or not, but I'm sure if it isn't, that someone will be able to point us in the right place. Thanks, Gabriel P.S. Keep up the GREAT work.
Re: [Mono-list] Extending the framework - Masked Text Box
--- Gabriel Emily Bin [EMAIL PROTECTED] wrote: Hello, First I must say that I enjoy being a bit of a lurker on this list. Here is the deal. When developing apps in C# or VB.NET there is no masked textbox available in the standard (MS) framework. When searching for this on Goggle, one sees quite a few people looking for this functionality. Anyway, my brother wrote one that inherits from text box and implements all of the things that people have come to expect from a masked textbox along with other nice enhancements. He would like to contribute his code to the Mono project. He asked me if I (being a member of this list) would find out how to get the code submitted. I don't know if this is the appropriate place to ask this question or not, but I'm sure if it isn't, that someone will be able to point us in the right place. Thanks, Gabriel P.S. Keep up the GREAT work. The System.Windows.Forms namespace for mono is not complete and I am not sure if mono has plans for a third party SWF library at this point, but with that said, you can always post the code to one of the many Windows Forms sites that take third party controls. Here is one for instance: http://windowsforms.net/Default.aspx?tabindex=8tabid=50 I am sure there are others and if you would feel like contributing GPL code then I would suggest SharpDevelop ... they might be interested, but I am not sure. http://www.icsharpcode.net/OpenSource/SD/Default.aspx Cheers, Adam __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] FxCop?
Hello, I recently saw Miguel mention FxCop. I'm not sure about the licensing stuff, so I'm asking here (hoping someone can answer this question): Is it allowed to use FxCop on the (mono) class libraries / assemblies and (based upon it's analysis) modify the mono sources? Or rephrasing: Are we allowed to use this tool to improve Mono? Yes, you are allowed to use FxCop to improve Mono's class libraries. Be warned though that there are too many warnings generated that should be ignored, so it should not be done blindly. If the answer is yes, then how are we going to proceed with this? Do we agree with all the rules it checks, etc? Is it ok for me to run the tool on a certain assembly and start fixing things? I think we should run the tool on our assemblies and generate a set of settings that we are comfortable having. At the same time, there are some very simple things that we should do *anyways*, so lets post patches to the list and take it from there. Miguel ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] FxCop?
Miguel de Icaza wrote:
Yes, you are allowed to use FxCop to improve Mono's class libraries.
Be warned though that there are too many warnings generated that should
be ignored, so it should not be done blindly.
I already figured that much out :)
If the answer is yes, then how are we going to proceed with this?
Do we agree with all the rules it checks, etc? Is it ok for me to run
the tool on a certain assembly and start fixing things?
I think we should run the tool on our assemblies and generate a set of
settings that we are comfortable having.
That sounds like a good idea, I think the tool allows this with regards
to saving/loading an exclude set.
So we could probably define a mono 'exludes' file and have it in CVS.
At the same time, there are
some very simple things that we should do *anyways*, so lets post
patches to the list and take it from there.
What do we do with the following rules (I started with Mono.PEToolkit -
but I think starting with any assembly will result in the same general
rules to be 'hit'):
* Assemblies are marked CLSCompliant ('Mono.PEToolkit' should have the
CLSCompliantAttribute, and its value should be true.)
* Assemblies have strong names (Sign 'Mono.PEToolkit' with a strong name
key.)
I think we can skip this one for now, right?
* Assemblies have version numbers (Add an AssemblyVersion attribute to
the 'Mono.PEToolkit' assembly.)
* Exceptions do not extend System.Exception (Change
'BadMetaDataException' to extend either ApplicationException or
SystemException.)
* Exceptions require multiple constructors (Add a constructor with a
string parameter and exception parameter to custom exception
'BadMetaDataException'. Add a protected constructor with a
SerializationInfo object parameter and a StreamingContext object
parameter to custom exception 'BadMetaDataException'.)
* Exceptions are marked Serializable (Add a Serializable attribute to
'BadMetaDataException'.)
That should be enough to start discussing/working on for now.
---
Jeroen Janssen
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
On 02/03/03 Adam Treat wrote: You said, 'policy for inclusion is very easy: do something for mono' ... if this were the case then I would be included. This is not the case. So when you say that is the 'policy' and you also acknowledge that I've 'done something for mono' ... hence the inevitable question 'then why am I not on the list'? Because the default is to trust people, so it's very easy to get in. Later trust in you was lost, for whatever reason, so you were excluded from a list whose members we trust. dotgnu-2002-11-03.log: [07:23] t3rmin4t0r we could use other licenses outside pnetlib [07:23] t3rmin4t0r or fork mono's System.Xml [07:23] manyoso well, mono's System.Xml is X11 so we should be able to relicense it with GPL+Linking [...] dotgnu-2002-11-25.log: [...] [09:43] manyoso when it does work, i think we should maintain it in pnet's cvs and mail patches back and forth alla the i8ln libs You have been removed from the list on 2002-11-20, after two weeks of pondering. These logs are after that, so they could not be used as a basis for a different judgement at the time:-) this was settled and I dropped it completely. I am only asking for Miguel to follow through. The initial email that sparked this thread was a simple, 'Hey, what's up with mono-devel'? What makes you think a mail on mono-list would have had more effect that a private mail? I'll tell you an important secret address: [EMAIL PROTECTED] :-) In fact, Miguel has publicly stated that Portable.NET, DotGNU, Rotor, Intel, Evil Company are all welcome to work on and use Mono's class libraries (this The license allows that. The license doesn't allow them to pretend to have access to the mono-hackers list. Whaahhh? I have no idea what you are trying to say here. Once again, I am not asking for access to Ximian secrets or 'confidential information'. You've asked that I not misrepresent your views and I would kindly ask the same. It was an example to point out that anyone would have been removed from mono-hackers if they intended to do harm to the mono project, no matter the license of the assemblies. Forking the code does harm the project. If I lost your trust, let me know privately what I should do to gain it back (hey, if you ever travel near Venice or Padua here in Italy, be sure to send me mail and we'll share a bottle of wine:-). If you have similar issues with someone else in the project, do it privately, a public mailing list is not the best medium for settling personal issues. If you can't reconcile the positions, ignore some people and carry on with your contributions, like many people do in large projects. I was just responding to what you said about how I should 'do something' to gain trust. It is difficult to not take this personally. When I said we expected you to do something to regain the trust it was because I (and I'm sure miguel, too) would love to have you working together with us again. You should start taking it personally if I send you a mail with banner f*ck off |mail ... ;-) Fine. Once again, I am not looking for access to any confidential information. I just think the mono development discussion should take place in an open forum as we have all agreed. I don't A mono-devel mailing list was already in the plans for a long time. It hasn't been done because it's not a priority: most of the non-confidential technical discussions happen on mono-list anyway or on IRC. Anyway, the list will be announced soon, hopefully that will put an end to this thread:-) Thank you for your nice invitation. Next time you visit Boston I'd like to extend the same invitation :-) Noted:-) lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
On Mon, 2003-02-03 at 18:14, Adam Treat wrote: --- Martin Baulig [EMAIL PROTECTED] wrote: Adam Treat [EMAIL PROTECTED] writes: Why should I continue to contribute when it is so readily apparent that Miguel is interested in excluding me completely. I have not seen Mono do _anything_ to regain my trust. Ok, so far this whole discussion was about you wanting to join a private mailing list of the Mono project. Miguel as the project leader excluded you from the list and as the project leader, it's his decision to do so. He also offered you a simple solution to the problem by providing that GNU Mailman patch which makes things work for everyone. Ok, could you please reread this thread. I am not asking to join mono-hackers again. I simply wish to be included in the development discussion of Mono. If Miguel wishes to use mono-hackers for relating secrets and confidential information then ok, please setup a list for the open discussion. One list for open development discussion and one list for Ximian secrets and confidential information about Mono. Already agreed to. Again - you can use mono-list for that. For example I post all JIT related things to mono-list. So whats the problem? - Dietmar ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Re: mono-hackers -- mono-devel-list
--- dietmar [EMAIL PROTECTED] wrote: Again - you can use mono-list for that. For example I post all JIT related things to mono-list. So whats the problem? - Dietmar I can use those lists, but conversations that are not confidential and that affect mono development are going on in mono-hackers. I just wish these conversations were open, that's all. See the 'RE: Mono-Hackers' threads that were cross posted to mono-list last month for instance. These were cross-posted but what about other threads which were not? Anyways, it is useless to continue. Miguel is not going to back down unless I write that silly patch and I'm not goint to write it. This thread can die here. Cheers, Adam __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] RE: Mono-list digest, Vol 1 #761 - 8 msgs
I do not know about the license, but I assume it would be ok to use it on mono classes. Run the tool, and use common sense about the errors it reports. If in doubt ask on the list. For instance FXcop checks to see if a namespace has too many classes (should be split) or too few classes (should be combined). The real test of namespace size is does this stuff go together. Many of the .NET name spaces have too many or too few classes by FXCop standards. Of course we would not split or combine the namespaces. This is just one example. When working at the library or compiler level, this that might not make sense otherwise can still be good. Still FXCop is a good tool, and if it flags something as bad, it should at least be looked at. Dennis -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 9:42 AM To: [EMAIL PROTECTED] Subject: Mono-list digest, Vol 1 #761 - 8 msgs Message: 8 Date: Mon, 03 Feb 2003 18:41:55 +0100 From: Jeroen Janssen [EMAIL PROTECTED] To: mono-list [EMAIL PROTECTED] Subject: [Mono-list] FxCop? Hello, I recently saw Miguel mention FxCop. I'm not sure about the licensing stuff, so I'm asking here (hoping someone can answer this question): Is it allowed to use FxCop on the (mono) class libraries / assemblies and (based upon it's analysis) modify the mono sources? Or rephrasing: Are we allowed to use this tool to improve Mono? If the answer is yes, then how are we going to proceed with this? Do we agree with all the rules it checks, etc? Is it ok for me to run the tool on a certain assembly and start fixing things? --- Jeroen Janssen --__--__-- ___ Mono-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list End of Mono-list Digest ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Extending the framework - Masked Text Box
Just make it compile to a separate assembly (from System.Windows.Forms) with a separate namespace. But, beware, for inclusion in mono class library it should be X11 licensed. If you want to GPL it you can put it on sourceforge as an independent project, or follow Adam's link. Welcome to open source marvels and pitfalls, :D Rafael Teixeira Brazilian Polymath Mono, MonoQLE Hacker _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] FxCop?
Hello,
* Assemblies are marked CLSCompliant ('Mono.PEToolkit' should have the
CLSCompliantAttribute, and its value should be true.)
We want this.
* Assemblies have strong names (Sign 'Mono.PEToolkit' with a strong name
key.)
I think we can skip this one for now, right?
Yes, skippable for now.
* Assemblies have version numbers (Add an AssemblyVersion attribute to
the 'Mono.PEToolkit' assembly.)
We should add, something that matches the MS versions possibly.
* Exceptions do not extend System.Exception (Change
'BadMetaDataException' to extend either ApplicationException or
SystemException.)
Good for non-core assemblies. For core assemblies (those that are
compatible with Microsoft) we have not really any option.
* Exceptions require multiple constructors (Add a constructor with a
string parameter and exception parameter to custom exception
'BadMetaDataException'. Add a protected constructor with a
SerializationInfo object parameter and a StreamingContext object
parameter to custom exception 'BadMetaDataException'.)
* Exceptions are marked Serializable (Add a Serializable attribute to
'BadMetaDataException'.)
We want both.
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] mBas now understands rootnamespace argument
Implemented rootnamespace line command option. It defaults to the output file name. Also now, like vbc, if no source file name is provided just mBas will just show the help text, instead of outputting an error message. I could not test the namespaces created, as type-reflector in cvs can't run in console mode... 'make -f makefile.gnu console' builds and gives no warning but running type-reflector with mono gives a 'Error: Invalid displayer:' message. I checked the xml config file for type-reflector and it seems to have it right... Happy hackings, Rafael Teixeira Brazilian Polymath Mono, MonoQLE Hacker _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] FxCop?
That sounds like a good idea, I think the tool allows this with regards to saving/loading an exclude set. So we could probably define a mono 'excludes' file and have it in CVS. I think there is some means to define 'new' rules (an 'includes' file, perhaps) and we should construct one such file with mono specific rules, and add it to cvs too. Does this idea have some merit? Any rules that are new or different from fxcop's standard set? Cheers, Rafael Teixeira Brazilian Polymath Mono, MonoQLE Hacker _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] mBas now understands rootnamespace argument
Hi Rafael, Is it possible to do database stuff with MonoBasic yet? For example, here is a simple program that works on .NET below: Imports System Imports System.Data Imports System.Data.SqlClient Module Module1 Sub Main() Dim con As SqlConnection con = New SqlConnection(Server=localhost;database=pubs;user id=someuser;password=somepass) con.Open() Dim cmd As SqlCommand cmd = con.CreateCommand() cmd.CommandText = select fname from employee Dim reader As SqlDataReader reader = cmd.ExecuteReader() If (reader.Read()) Then Dim firstName As String firstName = reader.GetString(0) Console.WriteLine(firstName) Else Console.WriteLine(No data returned.) End If End Sub End Module -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of A Rafael D Teixeira Sent: Monday, February 03, 2003 2:41 PM To: [EMAIL PROTECTED] Subject: [Mono-list] mBas now understands rootnamespace argument Implemented rootnamespace line command option. It defaults to the output file name. Also now, like vbc, if no source file name is provided just mBas will just show the help text, instead of outputting an error message. I could not test the namespaces created, as type-reflector in cvs can't run in console mode... 'make -f makefile.gnu console' builds and gives no warning but running type-reflector with mono gives a 'Error: Invalid displayer:' message. I checked the xml config file for type-reflector and it seems to have it right... Happy hackings, Rafael Teixeira Brazilian Polymath Mono, MonoQLE Hacker _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ___ 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
RE: [Mono-list] Extending the framework - Masked Text Box
I suppose that someone somewhere will have the time to administer a project who's sole goal is to track and incorporate different extensions into a System.Windows.Forms.Extra namespace. C#Develop already uses an extension toolkit for its rendering. Maybe, that code can also be incorporated there. Phil -Original Message- From: A Rafael D Teixeira [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 2:50 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Mono-list] Extending the framework - Masked Text Box Just make it compile to a separate assembly (from System.Windows.Forms) with a separate namespace. But, beware, for inclusion in mono class library it should be X11 licensed. If you want to GPL it you can put it on sourceforge as an independent project, or follow Adam's link. Welcome to open source marvels and pitfalls, :D Rafael Teixeira Brazilian Polymath Mono, MonoQLE Hacker _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ___ 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
Re: [Mono-list] Future of JIT
Woo! Seriously, I've been hacking on getting together a working OS X Mono environment off and on for a couple of months now, and this is a huge step in the right direction, thanks Paolo. Andy On Monday, February 3, 2003, at 02:05 PM, Paolo Molaro wrote: On 02/03/03 Piers Haken wrote: Hopefully when the new JIT engine is release, we will release some technical documents on it as well. Yeah that would be great. Maybe you or Paolo could give us a little teaser to tide us over until then? Maybe some of the basic algorithmic Ok, here is the scoop: I have mini (the codename for the new JIT) happily running and compiling methods on MacOSX to x86 native code with the wrong endianness! lupus / ducks :-) -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ 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
Re: [Mono-list] FxCop?
Miguel de Icaza wrote:
Hello,
* Assemblies are marked CLSCompliant ('Mono.PEToolkit' should have the
CLSCompliantAttribute, and its value should be true.)
We want this.
For all assemblies?
* Assemblies have version numbers (Add an AssemblyVersion attribute to
the 'Mono.PEToolkit' assembly.)
We should add, something that matches the MS versions possibly.
Ok, that means someone has to dig out the MS version numbers (any
volunteers?).
What about 'mono' assemblies (things that don't are available from MS)?
(nicest things would be to have configure create it based on some
setting I think).
You could go for mono version number (example: put 0.19 in the version
for mono 0.19), or go for assembly specific version numberings.
At least for everything 'in' mcs/class I think it might be better to
follow the mono version numbering.
* Exceptions do not extend System.Exception (Change
'BadMetaDataException' to extend either ApplicationException or
SystemException.)
Good for non-core assemblies. For core assemblies (those that are
compatible with Microsoft) we have not really any option.
Ok, maybe we should put an mono-FxCop-rule 'explanation' somewhere.
The 'rules' are different for core and non-core assemblies.
* Exceptions require multiple constructors (Add a constructor with a
string parameter and exception parameter to custom exception
'BadMetaDataException'. Add a protected constructor with a
SerializationInfo object parameter and a StreamingContext object
parameter to custom exception 'BadMetaDataException'.)
* Exceptions are marked Serializable (Add a Serializable attribute to
'BadMetaDataException'.)
We want both.
Is this also the case for core assemblies?
(forgive me, but I don't know if the current core assemblies contain
exceptions without following these two rules).
---
Jeroen Janssen
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Running Windows.Forms app under mono?
Hi, I have a fresh installation of RedHat 8.0 with the latest build of mono and wine installed. I also have Windows 2000 installed on drive c, and have setup both wine and mono correctly. I have a simple .net forms test app that I'd like to run under mono. I have tried a number of things, but seem to be pulling me hair out at this stage. 1) Tried 'wine mono SimpleWindow.exe' == returned wine: cannot find 'mono' 2) Tried mono SimpleWindow.exe == returned (just a small snippet of the errors Ive removed a lot of lines since they kept repeating.) ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libcomctl32.dll.so (comctl32.dll): libcomctl32.dll.so: cannot open shared object file: No such file or directory ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libuser32.dll.so (user32.dll): libuser32.dll.so: cannot open shared object file: No such file or directory ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libkernel32.dll.so (kernel32.dll): libkernel32.dll.so: cannot open shared object file: No such file or directory Unhandled Exception: System.MissingMethodException: A missing method exception has occurred. in 0x00046 06 System.Windows.Forms.Win32:RegisterClass (System.Windows.Forms.WNDCLASS) in 0x00127 00 System.Windows.Forms.ScrollableControl:get_CreateParams () in 0x00012 00 System.Windows.Forms.ContainerControl:get_CreateParams () in 0x00012 00 System.Windows.Forms.Form:get_CreateParams () in 0x00062 00 System.Windows.Forms.Control:CreateHandle () in 0x00012 00 System.Windows.Forms.Form:CreateHandle () in 0x003db 00 System.Windows.Forms.Control:.ctor () in 0x00015 00 System.Windows.Forms.ScrollableControl:.ctor () in 0x00014 00 System.Windows.Forms.ContainerControl:.ctor () in 0x00043 00 System.Windows.Forms.Form:.ctor () in 0x00043 00 SimpleWindow.frmMain:.ctor () in 0x00024 00 SimpleWindow.frmMain:Main () 3) Looked at my /etc/mono/config file and it's like this: configuration dllmap dll=cygwin1.dll target=libc.so.6 / dllmap dll=libc target=libc.so.6 / dllmap dll=libxslt.dll target=libxslt.so / dllmap dll=libmySQL.dll target=libmysqlclient.so / dllmap dll=odbc32.dll target=libodbc.so / dllmap dll=libglib-2.0-0.dll target=libglib-2.0.so / dllmap dll=libgobject-2.0-0.dll target=libgobject-2.0.so / dllmap dll=libpango-1.0-0.dll target=libpango-1.0.so / dllmap dll=libatk-1.0-0.dll target=libatk-1.0.so / dllmap dll=libgdk-win32-2.0-0.dll target=libgdk-x11-2.0.so / dllmap dll=libgdk_pixbuf-2.0-0.dll target=libgdk-pixbuf-2.0.so / dllmap dll=libgtk-win32-2.0-0.dll target=libgtk-x11-2.0.so / /configuration Any ideas as to what to do here to get this to work? Any suggestions would be greatly appreciated! Thanks, Rob. __ Robert A. Wlodarczyk [EMAIL PROTECTED] Windows Messenger: [EMAIL PROTECTED] (cell) 516.446.3319 - (home) 631.265.0609 - (fax) 631.724.5528 ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Running Windows.Forms app under mono?
The short answer: Don't bother yet. The (slightly) longer answer: There are unresolved issues between mono, wine, threading, and garbage collection. There may be other issues. They haven't been solved, and I'm not sure when they will be solved. I can say that people are working on it, but that's about it. - Jon On Mon, 2003-02-03 at 19:50, Robert A. Wlodarczyk wrote: Hi, I have a fresh installation of RedHat 8.0 with the latest build of mono and wine installed. I also have Windows 2000 installed on drive c, and have setup both wine and mono correctly. I have a simple .net forms test app that I'd like to run under mono. I have tried a number of things, but seem to be pulling me hair out at this stage. 1) Tried 'wine mono SimpleWindow.exe' == returned wine: cannot find 'mono' 2) Tried mono SimpleWindow.exe == returned (just a small snippet of the errors Ive removed a lot of lines since they kept repeating.) ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libcomctl32.dll.so (comctl32.dll): libcomctl32.dll.so: cannot open shared object file: No such file or directory ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libuser32.dll.so (user32.dll): libuser32.dll.so: cannot open shared object file: No such file or directory ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libkernel32.dll.so (kernel32.dll): libkernel32.dll.so: cannot open shared object file: No such file or directory Unhandled Exception: System.MissingMethodException: A missing method exception has occurred. in 0x00046 06 System.Windows.Forms.Win32:RegisterClass (System.Windows.Forms.WNDCLASS) in 0x00127 00 System.Windows.Forms.ScrollableControl:get_CreateParams () in 0x00012 00 System.Windows.Forms.ContainerControl:get_CreateParams () in 0x00012 00 System.Windows.Forms.Form:get_CreateParams () in 0x00062 00 System.Windows.Forms.Control:CreateHandle () in 0x00012 00 System.Windows.Forms.Form:CreateHandle () in 0x003db 00 System.Windows.Forms.Control:.ctor () in 0x00015 00 System.Windows.Forms.ScrollableControl:.ctor () in 0x00014 00 System.Windows.Forms.ContainerControl:.ctor () in 0x00043 00 System.Windows.Forms.Form:.ctor () in 0x00043 00 SimpleWindow.frmMain:.ctor () in 0x00024 00 SimpleWindow.frmMain:Main () 3) Looked at my /etc/mono/config file and it's like this: configuration dllmap dll=cygwin1.dll target=libc.so.6 / dllmap dll=libc target=libc.so.6 / dllmap dll=libxslt.dll target=libxslt.so / dllmap dll=libmySQL.dll target=libmysqlclient.so / dllmap dll=odbc32.dll target=libodbc.so / dllmap dll=libglib-2.0-0.dll target=libglib-2.0.so / dllmap dll=libgobject-2.0-0.dll target=libgobject-2.0.so / dllmap dll=libpango-1.0-0.dll target=libpango-1.0.so / dllmap dll=libatk-1.0-0.dll target=libatk-1.0.so / dllmap dll=libgdk-win32-2.0-0.dll target=libgdk-x11-2.0.so / dllmap dll=libgdk_pixbuf-2.0-0.dll target=libgdk-pixbuf-2.0.so / dllmap dll=libgtk-win32-2.0-0.dll target=libgtk-x11-2.0.so / /configuration Any ideas as to what to do here to get this to work? Any suggestions would be greatly appreciated! Thanks, Rob. __ Robert A. Wlodarczyk [EMAIL PROTECTED] Windows Messenger: [EMAIL PROTECTED] (cell) 516.446.3319 - (home) 631.265.0609 - (fax) 631.724.5528 ___ 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
Re: [Mono-list] Running Windows.Forms app under mono?
Please look at the README in the mcs/class/System.Windows.Forms directory. You will need to use the monostub WineLib application to start your Windows.Forms application, make some changes to the etc/mono/config file, and build Mono with garbage collection disabled. I just checked in some changes recently to run with the latest Mono and Wine releases. I have to warn you though at this point there is still a lot of work to do in the System.Windows.Forms namespace. John On Mon, 2003-02-03 at 19:50, Robert A. Wlodarczyk wrote: Hi, I have a fresh installation of RedHat 8.0 with the latest build of mono and wine installed. I also have Windows 2000 installed on drive c, and have setup both wine and mono correctly. I have a simple .net forms test app that I'd like to run under mono. I have tried a number of things, but seem to be pulling me hair out at this stage. 1) Tried 'wine mono SimpleWindow.exe' == returned wine: cannot find 'mono' 2) Tried mono SimpleWindow.exe == returned (just a small snippet of the errors Ive removed a lot of lines since they kept repeating.) ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libcomctl32.dll.so (comctl32.dll): libcomctl32.dll.so: cannot open shared object file: No such file or directory ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libuser32.dll.so (user32.dll): libuser32.dll.so: cannot open shared object file: No such file or directory ** (SimpleWindow.exe:1530): WARNING **: Failed to load library libkernel32.dll.so (kernel32.dll): libkernel32.dll.so: cannot open shared object file: No such file or directory Unhandled Exception: System.MissingMethodException: A missing method exception has occurred. in 0x00046 06 System.Windows.Forms.Win32:RegisterClass (System.Windows.Forms.WNDCLASS) in 0x00127 00 System.Windows.Forms.ScrollableControl:get_CreateParams () in 0x00012 00 System.Windows.Forms.ContainerControl:get_CreateParams () in 0x00012 00 System.Windows.Forms.Form:get_CreateParams () in 0x00062 00 System.Windows.Forms.Control:CreateHandle () in 0x00012 00 System.Windows.Forms.Form:CreateHandle () in 0x003db 00 System.Windows.Forms.Control:.ctor () in 0x00015 00 System.Windows.Forms.ScrollableControl:.ctor () in 0x00014 00 System.Windows.Forms.ContainerControl:.ctor () in 0x00043 00 System.Windows.Forms.Form:.ctor () in 0x00043 00 SimpleWindow.frmMain:.ctor () in 0x00024 00 SimpleWindow.frmMain:Main () 3) Looked at my /etc/mono/config file and it's like this: configuration dllmap dll=cygwin1.dll target=libc.so.6 / dllmap dll=libc target=libc.so.6 / dllmap dll=libxslt.dll target=libxslt.so / dllmap dll=libmySQL.dll target=libmysqlclient.so / dllmap dll=odbc32.dll target=libodbc.so / dllmap dll=libglib-2.0-0.dll target=libglib-2.0.so / dllmap dll=libgobject-2.0-0.dll target=libgobject-2.0.so / dllmap dll=libpango-1.0-0.dll target=libpango-1.0.so / dllmap dll=libatk-1.0-0.dll target=libatk-1.0.so / dllmap dll=libgdk-win32-2.0-0.dll target=libgdk-x11-2.0.so / dllmap dll=libgdk_pixbuf-2.0-0.dll target=libgdk-pixbuf-2.0.so / dllmap dll=libgtk-win32-2.0-0.dll target=libgtk-x11-2.0.so / /configuration Any ideas as to what to do here to get this to work? Any suggestions would be greatly appreciated! Thanks, Rob. __ Robert A. Wlodarczyk [EMAIL PROTECTED] Windows Messenger: [EMAIL PROTECTED] (cell) 516.446.3319 - (home) 631.265.0609 - (fax) 631.724.5528 ___ 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
Re: [Mono-list] Starting xsp at bootup
That worked perfectly, thanks. I'm using a reverse http proxy in lieu of
mod_mono to server up aspx contents. So
/svn/repos/.* comes from subversion httpd
/mono/.* comes from xsp server.exe
Everything else comes from my stock httpd.
-fawad
Miguel de Icaza wrote:
Hello,
If I run the same script as the ${RUNAS} user, the site loads up perfectly.
Any suggestions about what I'm doing wrong?
Try passing a -l flag to su (login shell), that way the whole
environment will be correctly setup to the one of the user.
Miguel
___
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
[Mono-list] RegistrationException
Hi, I am working on RegistrationException class in System.EnterpriseServices namepace. the method i am working on is GetObjectData(). I am trying to figure out how .net serializes the Errors in GetObjectData() method in this class. There is one hitch. It serializes a whole array of RegistrationErrorInfo classes. I am using serializer.cs. how should i modify serializer.cs to have it find out serialize all this data. i have attached the xml file that was created so far. thanks to duncan for helping me so far. all the best, -- Alexander Chan [EMAIL PROTECTED] SOAP-ENV:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:clr=http://schemas.microsoft.com/soap/encoding/clr/1.0; SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; SOAP-ENV:Body a1:RegistrationException id=ref-1 xmlns:a1=http://schemas.microsoft.com/clr/nsassem/System.EnterpriseServices/System.EnterpriseServices%2C%20Version%3D1.0.3300.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Db03f5f7f11d50a3a; ClassName id=ref-3System.EnterpriseServices.RegistrationException/ClassName Message id=ref-4test/Message InnerException xsi:null=1/ HelpURL xsi:null=1/ StackTraceString xsi:null=1/ RemoteStackTraceString xsi:null=1/ RemoteStackIndex0/RemoteStackIndex ExceptionMethod xsi:null=1/ HResult-2146233087/HResult Source xsi:null=1/ /a1:RegistrationException /SOAP-ENV:Body /SOAP-ENV:Envelope
