Re: .Net languages

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Jon Skeet [C# MVP] (skeet_at_pobox.com)
Date: 12/16/04


Date: Thu, 16 Dec 2004 08:03:37 -0000

Robby <edmund@not.my.email.com> wrote:
>
> VB.Net and C# have equal portability. Remember, these are based on the .Net
> Framework so any system that has the .Net Framework installed can use your
> assemblies.
>
> However, for maximum cross-platform compatabilty do not use any platform
> specific namespaces, objects or features that are not fully Common
> Language Specification (CLS) compliant. I think only the Microsoft.Win32
> namespace is platform specific so avoid using any objects in that namespace.

No - there's also the Microsoft.VisualBasic namespace, which many
VB.NET programs will use without the developer really knowing. While
Mono has ported many of the classes within this namespace, I suspect
there are still a few gaps.

-- 
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too


Relevant Pages

  • Re: need traceback from "has encountered an error and must close"
    ... The Microsoft.VisualBasicCompatiblity.vb6 namespace is still suported and a part of all current Net framework 2.0 and its full compatible versions including 3.5. ... the OS loader can not find the COM control. ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.languages.vb)
  • Re: need traceback from "has encountered an error and must close"
    ... The Microsoft.VisualBasicCompatiblity.vb6 namespace is still suported and a part of all current Net framework 2.0 and its full compatible versions including 3.5. ... the OS loader can not find the COM control. ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.languages.vb)
  • Re: need traceback from "has encountered an error and must close"
    ... with the Collection class in the Microsoft.VisualBasic namespace although ... that is an official full part of the Net framework. ... the OS loader can not find the COM control. ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Converting Vb.net to C# issues
    ... the .NET Framework classes are language-independant. ... properties/methods you could use in VB.NET, you use exactly the same way in ... Framework Classes and their properties & methods. ... feel free to use the Microsoft.VisualBasic Namespace, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Converting Vb.net to C# issues
    ... there is no way to "remove" the built-in reference to the ... that do not use the Microsoft.VisualBasic Namespace at all when ... IS one of the Namespaces in the .NET Framework. ... This project used a lot of methods in the VisualBasic Namespace. ...
    (microsoft.public.dotnet.languages.csharp)