+ core = standard library, io/string/async/thread/etc/linq.
+ some bundled stack, like wcf for create service, wpf for ui, mef for plugin, xml serialization, json serialization, asp.net webforms, etc.
Mono try to reimplement all.
Runtime and standard library work very well on mono.
bundled stacks can work, work partially or not implemented, depends (on contribution, check mono website). Some stack are really old way to do things, deprecated, usefull only on windows.
Also Microsoft for new stacks (like asp.net MVC) try to open source, so mono need to compile source and fix bug/different behaviour, not rewrite
If you use a library who depends on a bundled stack, can or cannot work on mono.
Library who depends on open source or standard lib, should work
+ runtime
+ core = standard library, io/string/async/thread/etc/linq.
+ some bundled stack, like wcf for create service, wpf for ui, mef for plugin, xml serialization, json serialization, asp.net webforms, etc.
Mono try to reimplement all. Runtime and standard library work very well on mono.
bundled stacks can work, work partially or not implemented, depends (on contribution, check mono website). Some stack are really old way to do things, deprecated, usefull only on windows. Also Microsoft for new stacks (like asp.net MVC) try to open source, so mono need to compile source and fix bug/different behaviour, not rewrite
If you use a library who depends on a bundled stack, can or cannot work on mono. Library who depends on open source or standard lib, should work