Re: [Mono-dev] Class status pages are empty
Hello, > class status pages linked from > http://www.mono-project.com/Class_Status are all empty, did something > break? Those are sadly left overs; We have moved most of our efforts to use gui-compare, a GUI tool that will compare APIs locally instead of the Web version. gui-compare is part of mono-tools. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Class status pages are empty
Miguel, What was the reason for discontinuing the (online) class status pages? Gert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miguel de Icaza Sent: zondag 21 september 2008 18:42 To: Leszek Ciesielski Cc: mono-devel-list Subject: Re: [Mono-dev] Class status pages are empty Hello, > class status pages linked from > http://www.mono-project.com/Class_Status are all empty, did something > break? Those are sadly left overs; We have moved most of our efforts to use gui-compare, a GUI tool that will compare APIs locally instead of the Web version. gui-compare is part of mono-tools. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Class status pages are empty
Hello, > What was the reason for discontinuing the (online) class status pages? We never really discontinued it, at least in my case, I stopped caring. They were just difficult to maintain, and doing quick changes were not reflected quickly (we had to wait a few hours for either the process to run, or setup a local system which was never well documented and was messy). Chris Toshok wrote gui-compare, which was very useful to quickly iterate over an API and have since then barely used the Web UI. I am not sure if others have done it, but I think some of us just stopped using it. I agree that a web version has a lot of value, and would love to keep it around, but in its current form its painful to deal with. The other bit that is important to point out is that it has not been upgraded to deal with the various new profiles, that is something that would have to be done as well. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] GCC-CLI Project
Hi, I'm interested in taking over this project, how do I start? Where do I find some guidance etc? http://gcc-cil.blogspot.com/ Kind Regards, Lennie De Villiers ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Class status pages are empty
Miguel, Perhaps some members of the Mono team use gui-compare, but I think end-users / third-party developers appreciate an easy way to consult the API compatibility level of certain types/members. The only painful part of the online class status pages (that I see) is that the masterinfo files are not automatically updated (after changes to mono-api-info). This could be scheduled as part of the win32 buildbot though. Does gui-compare use the same "masterinfo" input files (for .NET) as corcompare? Gert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miguel de Icaza Sent: zondag 21 september 2008 19:32 To: Gert Driesen Cc: 'mono-devel-list' Subject: Re: [Mono-dev] Class status pages are empty Hello, > What was the reason for discontinuing the (online) class status pages? We never really discontinued it, at least in my case, I stopped caring. They were just difficult to maintain, and doing quick changes were not reflected quickly (we had to wait a few hours for either the process to run, or setup a local system which was never well documented and was messy). Chris Toshok wrote gui-compare, which was very useful to quickly iterate over an API and have since then barely used the Web UI. I am not sure if others have done it, but I think some of us just stopped using it. I agree that a web version has a lot of value, and would love to keep it around, but in its current form its painful to deal with. The other bit that is important to point out is that it has not been upgraded to deal with the various new profiles, that is something that would have to be done as well. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Bug 414209] Mono 1.9.1 - Windows Installer needs admin rights
Hi, > This should be discussed on the mailing list and once the reason is tracked > down, this bug reopened The installer does the following things that require adminsitrative privileges: Copy files to "Program Files": other path can be chosen Write to some registry keys in HKEY_LOCAL_MACHINE: don't know if used by other applications but could be done in HKEY_CURRENT_USER when non-admin or just skipped. So there is no good reason to require adminstrative privileges altough extra functionality can be provided. Kornél > > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Class status pages are empty
Hello, > Perhaps some members of the Mono team use gui-compare, but I think end-users > / third-party developers appreciate an easy way to consult the API > compatibility level of certain types/members. > > The only painful part of the online class status pages (that I see) is that > the masterinfo files are not automatically updated (after changes to > mono-api-info). This could be scheduled as part of the win32 buildbot > though. Well, the masterinfo files are really static. Every time there is a new release, someone goes scavenging for all the files, and runs mono-api-info on the given assemblies and then we version the result. The actual masterinfos that we have are all listed in mono-tools/gui-compare/InfoManager.cs. Just grep for "Uri" there. So its merely an issue of fixing the build, and running more mono-api-diffs and generate more web pages for each of the profiles we want to compare. I think those should be: 1.1 2.0 3.5 SP1 On a side note: the generation of the masterinfo files is less that stellar. We have used a mix of the Reflection-based tools, and the Cecil tools to extract the information, and they are *slightly* different. In the last batch (done for 3.5SP1) I used the Cecil tools for half the assemblies (those that lived under Windows/) and reflection ones for the ones that live under "Reference Assemblies" because the Cecil ones required an assembly resolver that did not work. So the result is mixed. > Does gui-compare use the same "masterinfo" input files (for .NET) as > corcompare? Yes. > Gert > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Miguel de > Icaza > Sent: zondag 21 september 2008 19:32 > To: Gert Driesen > Cc: 'mono-devel-list' > Subject: Re: [Mono-dev] Class status pages are empty > > Hello, > > > What was the reason for discontinuing the (online) class status pages? > > We never really discontinued it, at least in my case, I stopped caring. > > They were just difficult to maintain, and doing quick changes were not > reflected quickly (we had to wait a few hours for either the process to > run, or setup a local system which was never well documented and was > messy). > > Chris Toshok wrote gui-compare, which was very useful to quickly iterate > over an API and have since then barely used the Web UI. I am not sure > if others have done it, but I think some of us just stopped using it. > > I agree that a web version has a lot of value, and would love to keep it > around, but in its current form its painful to deal with. The other > bit that is important to point out is that it has not been upgraded to > deal with the various new profiles, that is something that would have to > be done as well. > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] GCC-CLI Project
Hello, The GCC CIL backend was entirely redone by ST Microelectronics, and as far as I know the code has now been commited to a CIL branch on the GCC. If you want to contribute, you should check http://gcc.gnu.org/projects/cli.html > Hi, > > I'm interested in taking over this project, how do I start? Where do I > find some guidance etc? > > http://gcc-cil.blogspot.com/ > > Kind Regards, > > Lennie De Villiers > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] patch for dataset binary deserialization bugs
Hello, > I found 2 bugs while trying to deserialize binary datasets > from .NET: > > 1. A column with a DefaultValue set to anything other than DBNull > would throw an exception. > > 2. A table with zero rows would throw an exception. > > I have attached the patch I used to solve these issues. Let me know > if I'm out of my mind. This is my first foray into debugging Mono. Could you please provide NUnit tests for these two issues. Currently we do not know what scenario is causing this problem, and without Unit tests, we would not have a way of avoiding a regression in the future. Miguel. > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 2.0 RC2 Delayed
Hey Andy! On 9/16/08, Andy Hume <[EMAIL PROTECTED]> wrote: > Don't know whether you're already aware of these which affect 2.0... > Fixed, not backported: > .. 414146, WinForms, WebBrowser UriFormatException crash in basic usage > I'm about to go and try to test that fix here. Just FYI, this one has been backported. :) andreia gaita ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] patch for dataset binary deserialization bugs
On Sun, Sep 21, 2008 at 2:43 PM, Miguel de Icaza <[EMAIL PROTECTED]> wrote: > Hello, > > > I found 2 bugs while trying to deserialize binary datasets > > from .NET: > > > > 1. A column with a DefaultValue set to anything other than DBNull > > would throw an exception. > > > > 2. A table with zero rows would throw an exception. > > > > I have attached the patch I used to solve these issues. Let me know > > if I'm out of my mind. This is my first foray into debugging Mono. > > Could you please provide NUnit tests for these two issues. Currently > we do not know what scenario is causing this problem, and without Unit > tests, we would not have a way of avoiding a regression in the future. > > Tests were committed, along with a similar patch: http://anonsvn.mono-project.com/viewvc?view=rev&revision=113148 http://anonsvn.mono-project.com/viewvc/trunk/mcs/class/System.Data/Test/System.Data/BinarySerializationTest.cs?r1=76776&r2=113148&pathrev=113148 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
