I haven't really been following this, so if I've misunderstood what you're asking for, please forgive me.
In my recent work, I've found the following two - fairly minor - issues. 1. Use: AppDomain.CurrentDomain.SetupInformation.ConfigurationFile to discover the location of application configuration files. This avoids the use of the Windows-specific WINNT/Windows sub-directory, system32. 2. If developing service hosts for remote objects on Windows with the intention of deploying to Linux, specify the LocalSystem built-in account for the service user id. This value will be ignored under Linux. Under Windows, the username and password can be changed, if necessary, once the service is installed by configuring it in the Services explorer. Setting the user to other values causes the service to fail under Linux. I haven't looked at these again since April, so it may be that the information is out-of-date, especially for the second of the two. HTH Peter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miguel de Icaza Sent: 30 July 2006 17:52 To: mono-devel-list@lists.ximian.com; Frank Rego; mono-list@lists.ximian.com Subject: [Mono-list] Application Portability Guidelines. Hello, I have created a new page on the Wiki to serve as a tutorial to help people who want to port their applications from Windows to Linux to have a central location to look for information, the page is: http://www.mono-project.com/Guidelines:Application_Portability Feel free to augment the page with your experiences or with tools, tricks and tips that might be useful to others. Miguel. _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list