Mono is one of those nasty yes no answers. No you should not need two different binarys. But due to glitchs it might be a requirment for your program to detect mono and not attempt to use some funtions until they are fixed. http://www.mono-project.com/Gui_Toolkits Winforms coveres everything .NET 1.1 when you move to .NET 2.0 some functions exist others don't. This can cause problems. So with correct selection of functions no reason why Nlite cannot run on many platforms. As you can see GTK# is classed as stable not change. #Winforms is under development so not. Even if you say it only works with X version of Mono. I have no problem with that. At least I know what one is going to work. Sections of mono are 2.0 .net as well. Not exactly pritty. The other thing is the installer. There might be a requirement for same binary with different installers. Ie Windows installer. Linux installer ... Mainly so correct menu entrys and the like are added. I will run it and see how baddly it goes bang if really lucky it will run now. It was a few versions back in mono and nlite since I tried it last. A full Win32 api is not accessable in mono either running on non windows platforms. It will all depend on what nlite is using. If you are using Winapi features outside normal .Net features there could be problems. Some places Mono.net extends outside Microsoft .Net too. Basicly building on one and testing on one you cannot be sure that it will work on the other. If it does not work on MS.Net you can always add Mono extentions to MS .Net. Other way is not possiable quickly. Built on one test on both. When working on both one binary goes everywhere. Someone will need to test on something not Windows(somehow I guess that will be me). Reason if mono.net has the windows api avaible it will use it over its own. So winforms works pefectly on Windows with mono but functions are missing on everything else. Stayed tuned I will be back with the current resaults.
