I do use .net 3.5 Beta, and it is nice. Nevertheless, I think we should wait migrating to it until it is released, which should be this year in any case. And that for a simple reason: Once migrated you keep out anyone from development who doesn't want to install beta, and I don't think that would be appropriate.
I had a long look at the whole peer2peer technology stack from MS lately. In theory it looks very, very nice. In particular, if you look at the data store and the distributed record storing capability, it all sounds awesome (although there aren't any .Net wrappers for that stuff, not even in 3.5). But in practice, at least for my setup, which is VERY standard, connectivity is awful. It just hardly ever works. And if you look at the p2p blog at msdn, you will find pages of pages of pages of "debug" steps, on how to find out why things don't work. Quite frankly, the whole technology to me seems just too brittle to work with... Another very promising idea are Biztalk services. I actually had a experimental version of Alchemi running that used it for communication, and it worked wonderful :) If I find time I'll write up a longer email on how I would go forward with Alchemi, I have thought a lot about it lately. I am a great fan in incremental improvements and am quite optimistic that we might be able to do some significant improvements without starting from scratch. Best, David -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Matt Valerio Gesendet: Dienstag, 4. September 2007 23:58 An: Anton Melser Cc: [email protected] Betreff: Re: [Alchemi-developers] Time for a release or move on to .net 3.5? I too would love to move to WCF for communication, WF for data flow, and *linq for data access. Integrating the PeerChannel into things would be awesome as well. However, this is a huge undertaking and (I think) the resulting code would probably be so different that to pull it off we may need to start from scratch :) -Matt On 9/4/07, Anton Melser <[EMAIL PROTECTED]> wrote: > > XAML for the interfaces, dlinq and xlinq for data, WCF for > communication... I am also pretty keen to work on an interface that > allows you to graphically send packages (dlls + data probably zipped) > for submitting to the manager, and that is a great candidate for WWF > :-). > But I agree that cleaning up existing code is a priority. I will bring > home the MS code guidelines book and do some refactoring. 2008 > *finally* has usable refactoring (maybe just me, but I have 2005 > taking 3 minutes to refactor a method local variable...) so it should > be pretty smooth. I'll upgrade all the projects to 2005 first, clean > up what I can and then repose the question, shall I? > Cheers > Anton > > On 04/09/07, Matt Valerio <[EMAIL PROTECTED]> wrote: > > Hey Anton, > > > > Well after poking around in the Alchemi.Core stuff today, perhaps we > should > > look into migrating the stuff from 1.1 to 2.0 before moving to 3.5:P There > > is quite a bit of code that uses non-typesafe ArrayLists that need to be > > migrated to List<>s. > > > > What exactly in .NET 3.5 do you think we can take advantage of? > > > > -Matt > > > > > > On 9/4/07, Anton Melser <[EMAIL PROTECTED]> wrote: > > > > > > Hi all, > > > I am using the 2008 beta 2 now, and of course that starts putting lots > > > of dependencies in places and updates web.configs and the like. How > > > are people about upgrading to 2008/3.5? There are quite a few cool > > > things, that admittedly can be used in 2005 but if we aren't going to > > > do a release soon and there aren't any objections, I would like to > > > update... > > > There haven't been any incompatibilities that I have noticed so far > > > (there were a couple of bugs but I tried to compile in 2005 and got > > > the same errors), and the main thing is the configs I guess. Anyway, I > > > won't commit anything 2008-specific until I get some word from you > > > guys, but it would be nice to be able to commit everything without > > > having to deselect 10000 files in tortoise! > > > Cheers > > > Anton > > > > > > -- > > > echo > > '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc > > > This will help you for 99.9% of your problems ... > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a > browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > _______________________________________________ > > > Alchemi-developers mailing list > > > [email protected] > > > > > https://lists.sourceforge.net/lists/listinfo/alchemi-developers > > > > > > > > > > -- > echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc > This will help you for 99.9% of your problems ... > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers
