[Mono-docs-list] RE: Mono-docs-list digest, Vol 1 #250 - 1 msg
Hi duncan,
I think I also alerted about a same problem at
http://lists.ximian.com/archives/public/mono-docs-list/2004-March/001011
.html
take a look at
$monodoc\class\System.Data\en\System.Data\ConstraintCollection.xml
and you can see that the member Item, appear without parameters.
MemberSignature Language=C# Value=public virtual Constraint Item {
get; }; /
--
Mizrahi Rafael
Dev/QA Team Leader
[EMAIL PROTECTED]
Mainsoft Corporation. - Cross Platform Software Development Company
Ofek 2 Bld., North Industrial Area
Lod 71293, Israel
Direct: (+972) 8 9781300 ext. 381 Fax: (+972) 8 9219389
Mobile: (+972) 0507-296305
--
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 1:31 PM
To: [EMAIL PROTECTED]
Subject: Mono-docs-list digest, Vol 1 #250 - 1 msg
Send Mono-docs-list mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ximian.com/mailman/listinfo/mono-docs-list
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of Mono-docs-list digest...
Today's Topics:
1. Indexer signatures in the docs. (Miguel de Icaza)
--__--__--
Message: 1
From: Miguel de Icaza [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Organization: Novell, Inc.
Date: Tue, 13 Jul 2004 22:57:42 -0400
Subject: [Mono-docs-list] Indexer signatures in the docs.
Hey Folks,
I think we have miss-generated the Item [...] signature on the docs,
for example, we show:
public Gtk.Widget Item { get; }
In Glade.XML, instead of:
public Gtk.Widget Item [string index] { get; }
This is not too bad, but we are going to do another pass at fixing
things ;-(
--__--__--
___
Mono-docs-list mailing list
[EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-docs-list
End of Mono-docs-list Digest
___
Mono-docs-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-docs-list
Re: [Mono-list] mod_mono and swapping out web application
Jim Erwin wrote: works is to run killall mono from a root prompt. At this point, the server processes are restarted and on the next page hit, the JIT compilation takes place. All is well. The down side of this as I see it is that this will kill ALL mono applications on the box. So if I'm running multiple web applications, or other non-web mono applications on the server, all of them get killed at this point. ps -G apache | grep mono - use that in a script I wrote a little shell script at home that kills all mono instances running as children of apache. This allows other mono processes to continue working and also allows httpd to carry on serving other non-asp.net websites. (Unfortunately this will still kill all ASP.NET apps, but it's better than doing killall mono and monodevelop vanishes :-)) If you want it just drop me a mail and I'll send it to you tonight. Willem Smit SL IT *** Any views expressed in this message are those of the individual sender, and Sanlam accepts no liability for such views, except where the sender specifically states them to be those of Sanlam. Enige sienswyses of stellings wat in hierdie boodskap uitgedruk word is dié van die individuele afsender, en Sanlam aanvaar geen aanspreeklikheid daarvoor nie, behalwe waar die afsender uitdruklik vermeld dat dit dié van Sanlam is. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] mod_mono strange behavior
Apache/2.0.50 (Unix) mod_ssl/2.0.50 OpenSSL/0.9.7d PHP/4.3.7 mod_mono/1.0 mod_mono builded from cvs (present time Wed Jul 14 11:18:52 EEST 2004) --- from httpd.conf MonoUnixSocket /tmp/mono/mod_mono_server MonoRunXSP True MonoExecutablePath /usr/local/mono/bin/mono MonoPath /usr/local/mono/bin MonoServerPath /usr/local/mono/bin/mod-mono-server.exe MonoWapiDir /tmp/mono --- from apache error.log [Wed Jul 14 11:09:58 2004] [error] Not running mod-mono-server.exe because MonoListenAddress is present and there is no MonoListenPort. --- from mod_mono man MonoUnixSocket It accepts a file name as argument. That file will be a named pipe used to send/receive data from/to mod_mono to/from mod-mono-server. !!! You cannot use MonoListenPort and MonoUnixSocket at the same time. !!! Default value: /tmp/mod_mono_server. MonoListenPort TCP port on which mod-mono-server should listen/is listening on. Mutually exclusive with MonoUnixSocket. When this options is specified, mod-mono-server and mod_mono will use a TCP socket for communication. Default value: none MonoListenAddress IP address where mod-mono-server should listen/is listening on. Can only be used when MonoListenPort is specified. Default value: 127.0.0.1 My question is why mod_mono uses default MonoListenAddress when is not set and instead MonoUnixSocket is set ??? Maybe quick fix in cvs needed :)) GLHF --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.719 / Virus Database: 475 - Release Date: 12.07.2004 ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] WebServices and Mono
Hi,
I'm new in Mono and WebServices technology.
Could anybody write me a simple web service cliente example (web application) of
TestService.asmx (in /usr/share/doc/xsp/test).
TestService.asmx
-
%@ WebService Language=c# Codebehind=TestService.asmx.cs
Class=WebServiceTests.TestService %
using System;
using System.Web.Services;
using System.Web.Services.Protocols;
namespace WebServiceTests
{
public class TestService : System.Web.Services.WebService
{
[WebMethod]
public string Echo (string a)
{
return a;
}
[WebMethod]
public int Add (int a, int b)
{
return a + b;
}
}
}
---
And...Which are the steps for creating and compiling the proxy class?
Thanks a lot,
vale.
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mod_mono strange behavior
El mié, 14-07-2004 a las 10:08, Igor Georgiev escribió: Apache/2.0.50 (Unix) mod_ssl/2.0.50 OpenSSL/0.9.7d PHP/4.3.7 mod_mono/1.0 mod_mono builded from cvs (present time Wed Jul 14 11:18:52 EEST 2004) --- from httpd.conf MonoUnixSocket /tmp/mono/mod_mono_server MonoRunXSP True MonoExecutablePath /usr/local/mono/bin/mono MonoPath /usr/local/mono/bin MonoServerPath /usr/local/mono/bin/mod-mono-server.exe MonoWapiDir /tmp/mono --- from apache error.log [Wed Jul 14 11:09:58 2004] [error] Not running mod-mono-server.exe because MonoListenAddress is present and there is no MonoListenPort. That was a buglet. It's fixed now in CVS. If you update ensure you have this entry in the ChangeLog file: * src/mod_mono.c: set filename and listen_address defaults in the post_config hook. -Gonzalo ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] WebServices and Mono
El mié, 14-07-2004 a las 12:38, [EMAIL PROTECTED] escribió: Hi, I'm new in Mono and WebServices technology. Could anybody write me a simple web service cliente example (web application) of TestService.asmx (in /usr/share/doc/xsp/test). [...] And...Which are the steps for creating and compiling the proxy class? The simplest way is running xsp in the test directory and then: wsdl http://127.0.0.1:8080/TestService.asmx (the actual ip/port may vary). Also check 'wsdl --help' for more parameters. -Gonzalo ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] Remaining S/390 JIT issues
Hi,
I know nothing about S390, but maybe this stuff can be
handled
by adding more arch specific macros/functions, like
MONO_ARCH_IP_IN_CLAUSE(ctx,clause).
Zoltan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of ext
Sent: Tuesday, July 13, 2004 7:47 PM
To: [EMAIL PROTECTED]
Subject: RE: [Mono-list] Remaining S/390 JIT issues
There's a couple of idiosycracies with S390. For example, in
the exception8 test:
using System;
public class TryTest {
public static void ThrowException() {
throw new Exception();
}
public static int Main() {
int state = 0;
try {
ThrowException();
try {
Console.WriteLine(In try
block);
} catch (Exception e) {
state = 1;
Console.WriteLine();
Console.WriteLine(e);
Console.WriteLine();
}
} catch {
state = 2;
}
if (state != 2)
return 1;
Console.WriteLine(OK);
return 0;
}
}
The result of the ThrowException() is that the IP is
pointing at the first instruction of the try {
Console.WriteLine (In try Block); block so that the test
in mono_handle_exception()
if (ei-try_start = MONO_CONTEXT_GET_IP (ctx)
would result in the wrong catch being used to field the
exception.
-Original Message-
Hi,
Great work ! You might want to try modifying the S390 port
to use the
arch-independent exception handling
___
Mono-list maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Bug in String.Replace / StringBuilder.Replace
Title: Bug in String.Replace / StringBuilder.Replace Hi! There is a problem in Mono 1.0 when replacing in a string or stringbuilder object. Try 'Dim myBuffer As New System.Text.StringBuilder Dim mybuffer As String Dim myReader As New System.IO.StreamReader(WindowsFile, System.Text.Encoding.Default, False) Dim myWriter As New System.IO.StreamWriter(UnixFile, False, System.Text.Encoding.Default) Console.WriteLine(Reading file...) 'myBuffer.Append(myReader.ReadToEnd) mybuffer = myReader.ReadToEnd() myReader.Close() Console.WriteLine(Converting data...) myBuffer.Replace(vbCrLf, vbLf) Console.WriteLine(Writing file...) myWriter.Write(myBuffer.ToString) myWriter.Close() Console.WriteLine(File successfully converted) Catch ex As Exception System.Console.WriteLine(ex.ToString) System.Console.ReadLine() End Try The myBuffer variable contains a string of 7 MB. For small strings, it seems to work. But with larger ones as my 7 MB string, the line myBuffer.Replace(vbCrLf, vbLf) runs more than half an hour before finishing. Can somebody please fix this asap? Thanks!!! Regards Jochen CompuMaster GmbH Agentur für moderne Kommunikation Jochen Wezel, Multimedia-Programmierung Rhein-Mosel-Straße 69, 56281 Emmelshausen, GERMANY Fon: +49 6747 95084-12 / Fax: +49 6747 95084-50 http://www.compumaster.de eMail: [EMAIL PROTECTED] +++ Mitglied im DEUTSCHEN MULTIMEDIA VERBAND d m m v, http://www.dmmv.de +++ Unsere aktuellen AGBs befinden sich auf unserer Website im Bereich Rechtliches Diese eMail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: [Mono-list] Bug in String.Replace / StringBuilder.Replace
On Wed, 2004-07-14 at 15:36, Jochen Wezel wrote: Hi! There is a problem in Mono 1.0 when replacing in a string or stringbuilder object. The myBuffer variable contains a string of 7 MB. For small strings, it seems to work. But with larger ones as my 7 MB string, the line myBuffer.Replace(vbCrLf, vbLf) runs more than half an hour before finishing. This sounds like bug 61167, which I fixed last week. Can somebody please fix this asap? Thanks!!! Already done :) We will be releasing an updated 1.0 release soon. Before then you can check out the mono-1-0 branch of mono and mcs to get the fixes. - Dick ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] DiaCanvas# 0.4.0 released
Hello! For more information about the release of DiaCanvas# 0.4.0, see: http://mwh.sysrq.dk/programs/announcements/diacanvas-sharp-0.4.0.html Happy hacking! -- Martin Willemoes Hansen ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] OT: A good java book
hi guys, i'm not sure if any of you guys are java developer as well, and if you are, i just like to know which book you guys recommend if you're starting on learning the java language. thanks much for your time. Jonel ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] OT: A good java book
Thinking in Java by Bruce Eckel (sp?) or Java in a Nutshell at O'Reilly Erik On Jul 14, 2004, at 2:56 PM, Jonel Rienton wrote: hi guys, i'm not sure if any of you guys are java developer as well, and if you are, i just like to know which book you guys recommend if you're starting on learning the java language. thanks much for your time. Jonel ___ 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] Mono: Post 1.0 plans and development update.
Hello, Well, this release was fairly intense, thanks to everyone that contributed, the time has come to plan for the new features in Mono. * Releases Mono has been branched on the CVS repository and today we have two development tracks: the mono-1-0 branches and the HEAD branch. The mono-1-0 is only getting bug fixes and no new developments are happening there. The HEAD branch is where all the new features are being developed and where we are landing many of the patches that we did not get into the 1.0 release for various reasons. We will follow the Linux kernel model for release numbering, which means that we will release bug fixes and updates to the Mono 1.0 distribution, and those will be named 1.0.1, 1.0.2 and so on. The development versions of Mono will be released as well and will be named Mono 1.1.0, 1.1.1 and so on. * Updated Mono Roadmap. I am working on an updated version of the Mono roadmap to plan our upcoming releases, at this point we are completing the feature list of the things that my team inside Novell will be working on. Since Mono is developed by a large community outside of Novell the release will likely contain more than what my team is commited to do, purely based on external contributors, but the roadmap will try to be as conservative as possible in our time and feature estimates. I would like to make a release of Mono 1.2 (the next stable release) by February of next year, which means that we have roughly six months of development before we go into pure bug fixing mode. * Focus of the Novell team. There are a number of areas in which we are focusing for the Mono 1.2 release: * C# 2.1 implementation * AMD64 JIT port. * Visual Basic compiler. * Improved IO-Layer and Internationalization framework. * Gtk# improvement and GUI designer. * Mono Debugger. * Windows.Forms support. * JIT performance work. * Integration of patches that were too big to make it into the 1.0 release. * Code Access Security Framework. * Continued bug fixing of major and critical bugs. Those are the areas that people have expressed their most interest. Notice also that the above is still pretty much work aimed at the .NET 1.1 framework. Only a couple of developers are working on new features from the .NET 2.0 platform, but we do not believe that we can complete the .NET 2.0 API in time for the 1.2 release, so it is best to only deliver the bits listed above. As usual, a preview of the .NET 2.0 API will be available, but wont be complete. * .NET 2.0 work The Framework almost doubled in size in some parts of the framework. A handful of the Novell developers (Atsushi, Gonzalo and Lluis) will be working on the .NET 2.0 APIs in parallel, hopefully we can release some of the .NET 2.0 features a few months after the 1.2 release comes out. If you want to help, this is an area where we could use your contributions. Details about the large areas that need work are available on the CVS module called `release', look in the directory called mono_2_0. If enough people want, we can transform that list into something Web-browsable. An early ran of the API difference is available here: http://primates.ximian.com/~jackson/net_2_0/class-status.html We will automate this process and upload to mono-project.com on a constant basis. * Tinderbox setup Duncan has setup a tinderbox setup that keeps a close eye on both the stable and unstable branches of Mono, you can see the state of the build here: http://www.go-mono.com:8008/ * Some recent developments A few interesting developments have happened recently on the HEAD version of Mono: * A new, more robust, more complete, more aggressive Arrays Bounds Check Elimination. * Many x86 code generation peephole optimizations. * A new mechanism that removes static roots from the GC to scan, and it already gave some nice performance improvements to mcs and specially small applications. This work is part of an ongoing effort to implement a
Re: [Mono-list] Mono: Post 1.0 plans and development update.
Hello I've read all the new feature and i think that is a very promissing work you have ahead. I think that WinForms is important and must be a goal if you can implement it. I use mono essencially to make WebApplications, and i can't seen new good features in that area. For example the XSP sucks. We cannot use this kind of server in a production environment and i think this component should evolute for this server work as iqual as IIS. Hope you can insert this feature in next release of Mono. Continues the good work. (()) Paulo Aboim Pinto Odivelas - Portugal Miguel de Icaza wrote: Hello, Well, this release was fairly intense, thanks to everyone that contributed, the time has come to plan for the new features in Mono. * Releases Mono has been branched on the CVS repository and today we have two development tracks: the mono-1-0 branches and the HEAD branch. The mono-1-0 is only getting bug fixes and no new developments are happening there. The HEAD branch is where all the new features are being developed and where we are landing many of the patches that we did not get into the 1.0 release for various reasons. We will follow the Linux kernel model for release numbering, which means that we will release bug fixes and updates to the Mono 1.0 distribution, and those will be named 1.0.1, 1.0.2 and so on. The development versions of Mono will be released as well and will be named Mono 1.1.0, 1.1.1 and so on. * Updated Mono Roadmap. I am working on an updated version of the Mono roadmap to plan our upcoming releases, at this point we are completing the feature list of the things that my team inside Novell will be working on. Since Mono is developed by a large community outside of Novell the release will likely contain more than what my team is commited to do, purely based on external contributors, but the roadmap will try to be as conservative as possible in our time and feature estimates. I would like to make a release of Mono 1.2 (the next stable release) by February of next year, which means that we have roughly six months of development before we go into pure bug fixing mode. * Focus of the Novell team. There are a number of areas in which we are focusing for the Mono 1.2 release: * C# 2.1 implementation * AMD64 JIT port. * Visual Basic compiler. * Improved IO-Layer and Internationalization framework. * Gtk# improvement and GUI designer. * Mono Debugger. * Windows.Forms support. * JIT performance work. * Integration of patches that were too big to make it into the 1.0 release. * Code Access Security Framework. * Continued bug fixing of major and critical bugs. Those are the areas that people have expressed their most interest. Notice also that the above is still pretty much work aimed at the .NET 1.1 framework. Only a couple of developers are working on new features from the .NET 2.0 platform, but we do not believe that we can complete the .NET 2.0 API in time for the 1.2 release, so it is best to only deliver the bits listed above. As usual, a preview of the .NET 2.0 API will be available, but wont be complete. * .NET 2.0 work The Framework almost doubled in size in some parts of the framework. A handful of the Novell developers (Atsushi, Gonzalo and Lluis) will be working on the .NET 2.0 APIs in parallel, hopefully we can release some of the .NET 2.0 features a few months after the 1.2 release comes out. If you want to help, this is an area where we could use your contributions. Details about the large areas that need work are available on the CVS module called `release', look in the directory called mono_2_0. If enough people want, we can transform that list into something Web-browsable. An early ran of the API difference is available here: http://primates.ximian.com/~jackson/net_2_0/class-status.html We will automate this process and upload to mono-project.com on a constant basis. * Tinderbox setup Duncan has setup a tinderbox setup that keeps a close eye on both the stable and unstable branches of Mono, you can see the state of the build here: http://www.go-mono.com:8008/ * Some recent developments A few interesting developments have happened recently on the HEAD version of Mono: * A new, more robust, more complete, more aggressive
