Exactly. I mean, I'm running a grid of 30 machines that are very much considered "old". We're talking 2.4GHz P4s and 1GHz P3s. These guys would go for $40 at a garage sale. And they all run XP and Alchemi just fine. A machine that can run Windows 2000 but can't run XP is really starting to get into the fringe cases. I guess I don't feel bad cutting off that last <1% of the user base....
2008/3/27 Jonathan Mitchem <[EMAIL PROTECTED]>: > By the way, since I don't think it was obvious, I am pro-WCF, and I'm > glad the codebase moved in that direction. > > It's just that practical matter of matching what we like and want (as > developers and administrators) with the business reality of what makes > sense for Alchemi's "customers", right now. > > > 2008/3/27 Frank Lynch <[EMAIL PROTECTED]>: > > Jonathan raises a good point. We just upgraded the last of our 2k > machines in January. We couldn't have been the last ones. A quick Google of > the subject showed that as of 2005 half of the business pc were still > running win2k and MS has extended support until 2010. > > > > > http://www.news.com/The-slow-road-to-Windows-XP/2100-1016_3-5746046.html > > > > On the other hand, Jure has done a lot of good work on WCF. Cheers > Jure. I can live with XP sp2 and higher but I think that making a .net > remoting version (binaries and source) easily accessible might provide > benefit to the win2k folks. > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Jonathan > Mitchem > > Sent: Thursday, March 27, 2008 11:57 AM > > To: Jure Subara > > Cc: [email protected] > > > > > > Subject: 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"? > > > > > > On Tue, Mar 18, 2008 at 4:35 PM, Jure Subara <[EMAIL PROTECTED]> > wrote: > > > I am making changes to add support for WCF communication > > in Alchemi. > > > > > > You need to install .NET Framework 3.0 (Microsoft .NET Framework 3.0 > > > Redistributable > > > Package< > http://www.microsoft.com/downloads/info.aspx?na=47&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=f54f5537-cc86-4bf5-ae44-f5a1e805680d&u=details.aspx%3ffamilyid%3d10CC340B-F857-4A14-83F5-25634C3BF043%26displaylang%3den > >) > > > to build or use the new version of alchemi. > > > > > > SDK (Microsoft Windows SDK for .NET Framework > > > 3.0< > http://www.microsoft.com/downloads/info.aspx?na=40&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=10cc340b-f857-4a14-83f5-25634c3bf043&u=http%3a%2f%2fgo.microsoft.com%2ffwlink%2f%3fLinkId%3d74726 > >) > > > or special Visual Studio Extensions (Microsoft Visual Studio 2005 > CTP > > > Extensions for .NET Framework 3.0 (WCF & > > > WPF)< > http://www.microsoft.com/downloads/info.aspx?na=40&p=2&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=10cc340b-f857-4a14-83f5-25634c3bf043&u=http%3a%2f%2fgo.microsoft.com%2ffwlink%2f%3fLinkId%3d74725 > >) > > > are not needed. > > > > > > Jure Šubara > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > Alchemi-developers mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/alchemi-developers > > > > > > > > > > ------------------------------------------------------------------------- > > 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 > > This transmittal from AlphaLit is for the sole use of the intended > recipient and > > may contain confidential and privileged information. Any unauthorized > review or use, > > including disclosure or distribution is prohibited. If you are not the > intended recipient, > > please contact the sender and destroy all copies of the transmittal. > > > > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
