[Mono-dev] Porting Winforms Applications
Jonathan Pobst
monkey at jpobst.com
Wed May 30 16:24:05 EDT 2007
Yes, you are of course right in the general sense, as the next section
of the guide points out. I meant that the functionality this specific
application was going to be missing as a result of the MoMA report is
not too severe.
Thanks for pointing out that this is not clear, I will try to clean it
up a bit!
Jon
Andreas Nahr wrote:
> Hi,
>
> The guide to porting Winforms Applications is nice. However the imho the
> following sentences are just not true:
> "Most of the missing methods aren't too big of a problem either. We can
> expect that we will not have ToolTips in our TreeView, and we can't set our
> PrintDialog to use the Windows XP dialog. The missing event
> ListView.ItemSelectionChanged however will likely be a problem. Because that
> event does not exist, it will not get fired, so whatever code we are doing
> in the event handler will not get called. "
>
> In just about every case a missing element will just cause the program to
> throw an exception (e.g. MissingMethodException) and exit. It is extremely
> unlikely that such a program would run at all and if it does it will exit as
> soon as the relevant lines are called. It will NOT just not perform the
> requested action.
>
> P.S. I also attached an application that can be used to easily start a
> program on windows using mono without using the commandline and also offers
> debug/error output.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
More information about the Mono-devel-list
mailing list