It looks like 'winetricks dotnet20' and current wine is good enough that .net support isn't quite the limiting factor anymore! See http://bugs.winehq.org/show_bug.cgi?id=8499 http://bugs.winehq.org/show_bug.cgi?id=12457 http://bugs.winehq.org/show_bug.cgi?id=12458 for three sizeable apps that actually put up their GUIs, at least briefly. MySQL Workbench actually runs well enough to explore the GUI.
On Wed, Apr 9, 2008 at 2:56 AM, Dan Kegel dank@kegel.com wrote:
It looks like 'winetricks dotnet20' and current wine is good enough that .net support isn't quite the limiting factor anymore! See http://bugs.winehq.org/show_bug.cgi?id=8499 http://bugs.winehq.org/show_bug.cgi?id=12457 http://bugs.winehq.org/show_bug.cgi?id=12458 for three sizeable apps that actually put up their GUIs, at least briefly. MySQL Workbench actually runs well enough to explore the GUI.
Hm, looks like we'll have to begin to get used to "System.NotImplementedException"s :). Do crashing .net apps still print the full wine stack trace as well?
On Wed, Apr 9, 2008 at 9:25 AM, Zachary Goldberg zgs@seas.upenn.edu wrote:
Hm, looks like we'll have to begin to get used to "System.NotImplementedException"s :). Do crashing .net apps still print the full wine stack trace as well?
Not usefully, that I could see, anyway. Maybe if run inside winedbg.
-
Dan Kegel -
Zachary Goldberg