[Mono-list] Mono Migration Analizer 2.4 - Lot of warnings

[Jonathan Pobst]

What happens is I generate the MoMA info for each release from one of 
the early previews (because we don't add/remove methods once we begin 
the preview process).

The early preview I used this time had a bug where Microsoft.VisualBasic 
was not being included in Mono.  Therefore, MoMA is going to report 
everything in Microsoft.VisualBasic as being missing.

I will try to get updated definition files posted today.  You should be 
able just use "Check for updated definitions" in MoMA, and it will 
download and use them.

Thank you for finding and reporting this, and I apologize for the 
inconvenience!

Jonathan


fedemi1977 wrote:
> hello Everybody,
> 
> I delveloped an Application Using MS Visual Basic Express Edition and I'd
> like to run my application in a Linux Environment soon. 
> So, everytime a new Mono version is released, I run Mono Migration Analizer
> to check for incompatible code between environments. 
> Until 2.2. version  warnings were very few (such as
> System.Security.WindowsIdentity class, marked as 'Not implemented jet').
> 
> When I run 2.4 version of migration tool analizer I found 438 methods still
> missing in Mono such as 
> Split, Ubound and Trim string functions.
> 
> Strings.Split (string, string, int, CompareMethod) 
> int Information.UBound (Array, int) 
> string Strings.Trim (string) 
>  
> I've never seen so many warnings before 2.4 version was released. So, what
> is the problem..
> 
> Was a lot of function dropped in 2.4 version or Mono Migration Analizer has
> some bugs that reports false positives?
> 
> I Can't still run my application on Linux because I've to correct some
> P/Invokes , so at the moment I can only use Mono Migration Analizer for my
> tests.
> 
> Regards
> Federico M.