[Mono-dev] Microsoft.Build.* API fixes
marek.sieradzki at gmail.com
Sat Oct 21 02:51:44 EDT 2006
On 10/20/06, Leszek Ciesielski <skolima at gmail.com> wrote:
> On 10/20/06, Marek Sieradzki <marek.sieradzki at gmail.com> wrote:
> > On 10/20/06, Leszek Ciesielski <skolima at gmail.com> wrote:
> > > On 10/20/06, Marek Sieradzki <marek.sieradzki at gmail.com> wrote:
> > > > On 10/20/06, Leszek Ciesielski <skolima at gmail.com> wrote:
> > > > > Hi,
> > > > >
> > > > > attached is a patch fixing minor attribute differences between mono
> > > > > and ms.net, and containing stubs for (some of) missing classes.
> > > > > Permission to commit?
> > > > >
> > > > Hi,
> > > >
> > > > AssemblyInfo.cs changes are questionable. If there's a good reason for
> > > > them please specify it.
> > >
> > > Those attributes are present in MS.Net assembly ( consult eg. mono
> > > class status). Other that that - none, I dubt mono supports them at
> > > this time (meaning "pays any heed to them", I know compiler generates
> > > them properly). It's just a small increase in compatibility, when I
> > > could see no problems on our side. I do not want to argue, but if you
> > > are against applying them, please specify a reason :-)
> > >
> > I asked Miguel some time ago about that. Mono is based on msdn + ecma
> > docs. If specific attribute isn't obvious/needed nor documented it shouldn't
> > be added. Or at least it's the way I understood it.
> Patch with the class stubs again. This time without changes to
> assembly attributes and with correct (consistent with module style)
> formatting. Also, this one contains two more stubs. Permission to
More information about the Mono-devel-list