There is Patch fixes CreateControlStyle method of
System.Web.UI.WebControls.WebControl
and corresponding test.
Please review.
Igor.
WebControl.patch
Description: WebControl.patch
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
htt
Hi,
I never had a problem like this but now I keep getting error with SVN HEAD
when doing "make install".
Please help me resolving the problem.
Kornél
Some console output:
make install-local
make[7]: Entering directory `/mono/mcs/tools/resgen'
make[7]: Leaving directory `/mono/mcs/tools/resge
Hello Andrew,
On Tue, 2006-10-03 at 10:28 -0700, Andrew Skiba wrote:
> Hello Sebastien,
>
> > > Part of them is needed to omit TARGET_JVM, so code will be common.
> >
> > There are no TARGET_JVM in the two files.
> >
>
> As I said, these changes are needed to omit TARGET_JVM.
oops
> > > * Di
Hello,
We have always been thinking that the next release of Mono would be
"1.2" which would flag an incremental update to Mono 1.0, but this is a
relatively large update as it contains a lot of functionality that was
not in Mono 1.0.
I would even go as far as saying that we could feel co
Hi,
I'd agree that calling it 2.0 would confuse the issue with .net 2.0 support
My (unimportant) 2 cents ;p
Martin
On 10/4/06, Miguel de Icaza <[EMAIL PROTECTED]> wrote:
> Hello,
>
> We have always been thinking that the next release of Mono would be
> "1.2" which would flag an incremen
Miguel de Icaza wrote:
>So am thinking that maybe we could call this "Mono 1.5", or if we
>plan on keeping the even/odd release numbers from the kernel that we
>could call this Mono 1.6 or 1.8
>
v1.5 would get my vote, odd/even IMO is not ver applicable here as
"stable" versions seems to be p
Miguel de Icaza wrote:
> I would even go as far as saying that we could feel confident that
> this could be called "Mono 2.0", but 2.0 would have the unfortunate
> effect of confusing people regarding our .net 2.0 support.
Agreed!
> So am thinking that maybe we could call this "Mono 1.5
I'd go for 1.2. Skipping version numbers is a bad idea. So what there has been tons of progress from 1.1, the next release is still an incremental one. My two US pennies, - Matt
On 10/4/06, Michael Schurter <[EMAIL PROTECTED]> wrote:
Miguel de Icaza wrote:> I would even go as far as saying th
Hi Guys,I must apologize first coz these questions wuld have been asked like a Zillion times yet I am making the mistake of asking them again.The question is I just joined the community today with the idea of developing few
classes.BUT I DON'T KNOW WHERE TO START OF FROM,can someone please help m
> On the other hand - after reading other people's mail, it seems to me
> that all who experience the trimming have Oracle database setup as
> UTF8. Mine works in EEMSWIN1250 (you can check this with "SELECT value
> FROM nls_database_parameters WHERE parameter='NLS_CHARACTER_SET';").
No, you're wr
2006/10/4, David <[EMAIL PROTECTED]>:
> > On the other hand - after reading other people's mail, it seems to me
> > that all who experience the trimming have Oracle database setup as
> > UTF8. Mine works in EEMSWIN1250 (you can check this with "SELECT value
> > FROM nls_database_parameters WHERE pa
nagendra prasad wrote:
> Hi Guys,
> I must apologize first coz these questions wuld have been asked like a
> Zillion times yet I am making the mistake of asking them again.The
> question is I just joined the community today with the idea of
> developing few classes.BUT I DON'T KNOW WHERE TO STA
Michael Schurter escribió:
> Miguel de Icaza wrote:
>> I would even go as far as saying that we could feel confident that
>> this could be called "Mono 2.0", but 2.0 would have the unfortunate
>> effect of confusing people regarding our .net 2.0 support.
>
> Agreed!
I also agree.
>> So
Andrés G. Aragoneses [ knocte ] wrote:
> I agree with Michael. BTW, can we measure approximately, in a
> percentage, the current implementation of the 2.0 profile?
There's always the class status page:
http://mono.ximian.com/class-status/mono-HEAD-vs-fx-2/index.html
Doesn't have a total % compl
Michael Schurter escribió:
> First of all, the mono list is a better place to start as mono-devel is
> for developer's working *on* (not *with*) Mono.
According to [1], that's not strictly true. Citing the page:
> mono-devel-list: A mailing list specifically dedicated to discussions about
> dev
Andrés G. Aragoneses [ knocte ] wrote:
> Michael Schurter escribió:
>> First of all, the mono list is a better place to start as mono-devel is
>> for developer's working *on* (not *with*) Mono.
>
> According to [1], that's not strictly true. Citing the page:
>
>> mono-devel-list: A mailing list
Andrés G. Aragoneses [ knocte ] wrote:
> Michael Schurter escribió:
>> First of all, the mono list is a better place to start as mono-devel is
>> for developer's working *on* (not *with*) Mono.
>
> According to [1], that's not strictly true. Citing the page:
>
>> mono-devel-list: A mailing list
If I may suggest, there are a couple of good books you could use to get
going.
1 - if you have a MS.NET/Windows background, your best bet is
M.J.Easton's "Cross-Platform .NET Development: Using Mono, Portable.NET,
and Microsoft .NET";
2 - if you know C# E. Dumbill's "Mono (Developer's Notebo
[EMAIL PROTECTED] wrote on 10/04/2006 07:13:24 AM:
> I never had a problem like this but now I keep getting error with SVN
HEAD
> when doing "make install".
>
> Please help me resolving the problem.
...
> make install-local
> make[6]: Entering directory `/mono/mcs/jay'
> /bin/sh ../mkinstalldirs /
Hi,
I use the version in SVN:
http://svn.myrealbox.com/viewcvs/trunk/mcs/mkinstalldirs?rev=37686&view=markup
It is a working copy without any modifications. I've done "make clean",
"make" and "make install" using a previous (about two days old) revision.
Then I updated the working copy from SVN
Hi, JB.
This is a small fix to the Parse static method of AssemblyNameReference
where the value of PublicToken in the string is allowe to be "null".
Let me know if you have any comments before I commit this patch.
Eyal.Index: Mono.Cecil/AssemblyNameReference.cs
=
Hey Eyal,
You can commit, thanks!
Jb
Eyal Alaluf wrote:
> Hi, JB.
>
> This is a small fix to the Parse static method of AssemblyNameReference
> where the value of PublicToken in the string is allowe to be "null".
> Let me know if you have any comments before I commit this patch.
>
> Eyal.
>
>
Hi, JB.
In StructureReader.cs under the rare case when the assembly contains more then
1 module the module that is read should also be visited by the StructureReader
otherwise we get exceptions.
The DLL that showed this was either System.EnterpriseServices.dll or one
of the DLLs it uses.
Please l
Hey Eyal,
Good catch! Please just format the method call as it is everywhere
before commiting.
Thanks,
Jb
Eyal Alaluf wrote:
> Hi, JB.
>
> In StructureReader.cs under the rare case when the assembly contains
> more then
> 1 module the module that is read should also be visited by the
> Stru
Hi,
I found the soltion:
I had to change line endings to LF. But I don't really understand the
problem because I didn't update cygwin and the file has svn:eol-style=native
for a long time.
Kornél
- Original Message -
From: "Bill Seurer" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, Octobe
On 10/4/06, David <[EMAIL PROTECTED]> wrote:
> 2006/10/4, David <[EMAIL PROTECTED]>:
> > > On the other hand - after reading other people's mail, it seems to me
> > > that all who experience the trimming have Oracle database setup as
> > > UTF8. Mine works in EEMSWIN1250 (you can check this with "S
On Wed, 2006-10-04 at 01:32 -0700, Igor Zalmanovich wrote:
> There is Patch fixes CreateControlStyle method of
> System.Web.UI.WebControls.WebControl
> and corresponding test.
Please, commit.
Thanks.
-Gonzalo
___
Mono-devel-list mailing list
Mono-dev
Hi Sebastien,
Thanks for the feedback... I'm coming. :-)
Charlie
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Sebastien Pouliot
> Sent: Tuesday, October 03, 2006 4:55 AM
> To: Charlie Poole
> Cc: mono-devel-list@lists.ximian.com
> Subject: S
Hi Miguel,
OK, I worked things out and I'm attending the meeting.
I'd be happy to talk a bit about NUnit and where it is in terms of
running on Mono out of the box. It wouldn't be a deep-tech talk, just
an experience report of what kinds of things we ran into, what we're
doing about them and wha
Whoops... sorry to bother the list - that should have gone offline.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Charlie Poole
> Sent: Wednesday, October 04, 2006 4:38 PM
> To: 'Miguel de Icaza'; mono-list@lists.ximian.com;
> mono-devel-list
The roadmap has said 1.2 for years, so I would say stay with that.
It is not a strong opinon.
What will be the next major release? If the next release will be .NET 2.0 compatable, 1.5 could make sense.
So, I guess it should be either 1.2 or a new number that fits in to the latest roadmap.
Dennis
On Tue, 2006-10-03 at 07:54 -0400, Sebastien Pouliot wrote:
> Hello Charlie,
>
> On Mon, 2006-10-02 at 17:13 -0700, Charlie Poole wrote:
> > I'm still undecided about attending. I'd be curious to hear from
> > others to know whether there will be many mono application developers,
> > as opposed t
Hi,
I am doing a course on compiler. I am planning to choose a project based
on .NET Framework/Mono.
I am briefly describing the project below.
The project will aim to improve the execution of CIL image on multicore
processors. First step is to change the C# compiler to insert custom
instructi
33 matches
Mail list logo
