Then don't using system.windows.forms.dll because it is also a part of the
framework just like microsoft.visualbasic.dll. Maybe you mix it up with
umm, let me say it like this that windows.forms.dll is the default thing
that every language will use for windows apps, right, may it be cobol, perl,
C#, c++, vb etc etc. But the functions that r specific to VB.net r not the
defualt functions that all languages use. This is the point. I'm one of
those developers who switch between .net languages in there projects.
Basically I need everything from .net which can be used from every language.
Ofcourse the microsoft.visualbasic.dll is managed and can be refernced from
any other language and its functions called, but I dont want it this way,
for example if I 'm used to using cobol's native functions which r inside
say somecompany.cobol.dll, I dont want to refernce it in C# and use them.
So the solution is that I'm going to use, say for this thread, encoding
class which is a part of .net which all language developers can use without
thinking that its inside the C# dll or vb dll or cobol etc,, its just going
to be there whenever whichever language u need it from. So again, I wanna be
more close to .net instead of any language so I'll feel more comfortable
using different langauges. And by the way, havnt you heard this, that to be
and good developer in .net you need to be good at .net base class library
than knowing the language..