Here is a vote for "XP SP2 and higher only". Cheers, David
> -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:alchemi- > [EMAIL PROTECTED] Im Auftrag von Jonathan > Mitchem > Gesendet: Donnerstag, 27. März 2008 16:57 > An: Jure Subara > Cc: [email protected] > Betreff: Re: [Alchemi-developers] Microsoft .NET Framework 3.0 > > As far as I understand, .NET 3.0 isn't supported on Windows 2000. > > Personally, I have a 2000 machine and an XP machine. While, for me, > it's simply an annoyance, I'm pretty sure I'm not the only person out > there still using a 2000 machine. > > If we branch the project to create a Remoting version, and a WCF > version, they won't [by default] be compatible with each other... I > can see that leading to even more headaches in terms of deployment. > Granted, I'm sure we could create some sort of middleman to maintain > compatibility, but that's more of a hack than a solution. > > Then again, this might be kind of a naive view of the situation, > because it looks like if we moved from .NET Remoting in the Executor > to something using MSMQ or Enterprise Services, then we should be able > to maintain compatibility with a WCF Manager. > > Any better solutions or feedback? or should we just say "Only runs on > XP SP2 and Higher"? ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers
