AW: [mono-vb] Microsoft.VisualBasic namespace

Jochen Wezel jwezel@compumaster.de
Mon, 7 Jun 2004 15:42:42 +0200


> I've been working on this bug and resolved the most part of it,=20
> but I could not make it work for this specific case when the=20
> method is just semi-qualified with just the namespace. That=20
> is why the corresponding bugzilla case is still open.=20
Ahh, okay, then nothing can happen unexpectedly. I only wanted to ensure =
that this scenario gets also an eye on it. Fine, fine :)


-----Urspr=FCngliche Nachricht-----
Von: A Rafael D Teixeira [mailto:rafael.teixeirabr@terra.com.br]=20
Gesendet: Montag, 7. Juni 2004 15:32
An: Jochen Wezel
Cc: MonoVB
Betreff: Re: [mono-vb] Microsoft.VisualBasic namespace

On Mon, 2004-06-07 at 07:12, Jochen Wezel wrote:
> Hi Rafael/Anirban,
>=20
> Here is a small test file which can compile with VBC but not with=20
> MBAS.
> Priority: low
>=20
> imports System
>=20
> class ebbes
> shared sub Main()
>=20
>         Console.WriteLine(Microsoft.VisualBasic.Strings.ChrW(89))
> 'works fine :)
>         Console.WriteLine(Microsoft.VisualBasic.ChrW(89)) 'how MS did=20
> it??? Is it a just-in-time-wrapping in the compiler of a defined list=20
> of methods to another namespace/module, in this case Strings.ChrW?

In truth as Strings is a vb "Module" it is normally ommited, because all =
methods/properties/fields defined in them are static and given global =
visibility where the namespace is available. I've been working on this =
bug and resolved the most part of it, but I could not make it work for =
this specific case when the method is just semi-qualified with just the =
namespace. That is why the corresponding bugzilla case is still open.
Most people won't experience the problem because normally they would =
write just

        Console.WriteLine(ChrW(89))=20

This also works fine and is how people see it in VisualStudio, because =
Microsoft.VisualBasic assembly and namespace are automatically =
referenced and imported through command-line options.

In mono your makefile have to do what VS.NET does when calling vbc.

mbas /r:Microsoft.VisualBasic /imports:Microsoft.VisualBasic *.vb

I'm working on it, but I'm not sure if it will make for 1.0...

--
Rafael "Monoman" Teixeira
Mono Hacker since 16 Jul 2001 - http://www.go-mono.org/ Mono Brasil =
Founding Member - http://monobrasil.redesolbrasil.org/
English Blog: http://monoblog.blogspot.com/ Brazilian Portuguese Blog: =
http://monoblog.weblogger.terra.com.br/