Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Charlie Poole
Hi Brian, > Charlie Poole wrote: > > Oddly enough, loading our NUnit 2.4 test assemblies under a single > > domain causes it to fail. We're making it work under Mono by using > > Multiple AppDomains. So I assume the problem is more subtle than > > "never create more than one" I'll be intereste

Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Brian Crowell
Charlie Poole wrote: > Oddly enough, loading our NUnit 2.4 test assemblies under a single domain > causes it to fail. We're making it work under Mono by using Multiple > AppDomains. So I assume the problem is more subtle than "never create more > than one" I'll be interested in reading what the iss

Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Brian Crowell
Miguel de Icaza wrote: > I will add the semantics of our current AppDomain behavior. Thank you. Sorry for the caustic attitude. --Brian ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel

Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Alex Chudnovsky
Miguel de Icaza wrote: >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 >

Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Miguel de Icaza
Hello, > You don't understand what I wrote. *Every* bugs could block people. > IF we write notes that "your code might not work if you use ..." > with related to *every* bugs (EVEN IF it is possible), that > web info becomes pretty useless because of such flood of extraneous > information. > > Yo

Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Miguel de Icaza
Hello, > > Feel free to augment the page with your experiences or with tools, > > tricks and tips that might be useful to others. > > Probably add a suggestion to never create more than one AppDomain under Mono. I will add the semantics of our current AppDomain behavior. Miguel. ___

Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Atsushi Eno
You don't understand what I wrote. *Every* bugs could block people. IF we write notes that "your code might not work if you use ..." with related to *every* bugs (EVEN IF it is possible), that web info becomes pretty useless because of such flood of extraneous information. You could have just sear

Re: [Mono-dev] Application Portability Guidelines.

2006-07-31 Thread Brian Crowell
Atsushi Eno wrote: > We do support multi AppDomain. Your complaints on bug #76757 is > too tiny to be taken care on this general information. Or are you > saying that we should say "we don't support generics because there > are some bugs" ? All I know is that I'm tired of patching every copy of Mo

Re: [Mono-dev] Application Portability Guidelines.

2006-07-30 Thread Atsushi Eno
We do support multi AppDomain. Your complaints on bug #76757 is too tiny to be taken care on this general information. Or are you saying that we should say "we don't support generics because there are some bugs" ? Atsushi Eno Brian Crowell wrote: > Miguel de Icaza wrote: >> Feel free to augme

Re: [Mono-dev] Application Portability Guidelines.

2006-07-30 Thread Brian Crowell
Miguel de Icaza wrote: > Feel free to augment the page with your experiences or with tools, > tricks and tips that might be useful to others. Probably add a suggestion to never create more than one AppDomain under Mono. --Brian ___ Mono-devel-list m

[Mono-dev] Application Portability Guidelines.

2006-07-30 Thread Miguel de Icaza
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 t