Not sure but the article looks quite clear to me.

What is not included are VB specific libraries that are providing
compatibility with earlier VB releases or a simplified experience in some
areas...

It means that you'll have just to use .NET libraries instead of VB specific
librairies (that are not included to save space and that anyway are
duplictaing existing capabilities)...

--
Patrice

The reference says the FileSystem namespace is not supported.  The FileSystem
namespace is fully quallified as Microsoft.VisualBasic.FileSystem.  I don't
think that could be used easily, if at all, from C#.  This just means you
need to use the System.IO.* classes and namespaces.

If you click on the link that takes you to the summary of the things that  
are not supported, you'll see that all of the items are  
language-specific.  That is, they are things that are defined by the  
language, rather than .NET.

The main difference is that the VB language includes built-in  
functionality that isn't supported on the CF.  C# doesn't have any of its  
own i/o features, but instead relies entirely on the .NET Framework.  So  
there's nothing in C# that would have been left out; C# didn't have the  
features that were left out of VB for the CF in the first place.

I would say that if anything, it appears to me that when using the CF,  
programming in VB is a lot _more_ like C#, since you are forced to use the  
.NET features rather than the language's built-in features.  This is a  
normal state of affairs in C#, even when not specifically targeting the CF.

For more specific help, you may want to post to the Compact Framework  
newsgroup, since that seems more directly applicable to your question.

Pete

Use the framework bits instead of the language specific training wheels and
you should be fine. VB has a lot of shortcuts that you cannot use. That is
what it is saying.

*************************************************