It appears that Luts Roeder have decided to leave development and maintenance of .NET reflector…
If you have ever used Reflector, you probably already know how cool a tool it is…
Creator and Inventor has left it to Red Gate to continue the further development…
Check it out…
http://www.simple-talk.com/opinion/opinion-pieces/the-future-of-reflector-/
There were two CTP releases recently of technology that don’t directly focus on web services but you might find that they make developing services easier.
The first technology is called Velocity. Velocity is a platform for building distributed caches to make it easier to develop highly-scalable applications. There are some included samples for using Velocity with ASP.NET applications but you can reuse the platform in a variety of ways.
Microsoft Project Code Named “Velocity” Community Technology Preview 1 (CTP1)
The second technology is called Task Parallel Library and PLINQ. There are a set of parallel extensions for writing query and iteration expressions that automatically take advantage of the data and task parallelism present in high-level programming constructs.
Microsoft Parallel Extensions to .NET Framework 3.5, June 2008 Community Technology Preview
You can get several videos about these parallel extensions on Channel 9 as well.
* Joe Duffy and Igor Ostrovsky: Parallel LINQ under the hood
* Joe Duffy, Huseyin Yildiz, Daan Leijen, Stephen Toub – Parallel Extensions: Inside the Task Parallel
* Inside Parallel Extensions for .NET 2008 CTP Part 1
* Inside Parallel Extensions for .NET 2008 CTP Part 2
Microsoft has published the featurelist for Visual Studio 2008 and .NET “Orcas”.
They ask us (the development community) which features to prioritize high… exciting stuff 
Check it out:
http://msdn2.microsoft.com/en-us/vstudio/aa948851.aspx
When using the Weborb communication server from MidnightCoders there is a shortcoming in regards to supporting serverside deserialization of ArrayCollections. It supports Arrays but when trying to send complex types containing a reference to a ArrayCollection it is necessary to add a classmapping manually.
If one tries to pass an ArrayCollection to the server it will throw an error and the client will handle it without explaining exactly what went wrong. Recieving lists and collections and have them deserialized on the client into an ArrayCollection is no problem, its just the other way around that is more complex.
You need to map the flex.messaging.io.ArrayCollection (ClientClass) to the omnipresent Weborb.Util.ObjectProxy (ServerClass).
This can be done wither through the management console (Typically the default webpage of the server) or via the weborb.config residing in the “bin” directory of the server.
Why they have ommitted this classmapping from the default configuration beats me, but the operation is very simple, so it should not pose a significant problem once acknowledged.
Most AJAX developers have at some point damned the lack of browser support for browser history and bookmarking. A large subset of these developers have eventually attempted to solve the problem by implementing support for browser support, needless to say: with varying degrees of success.
As some of the major cornerstones in this latest frontier on the RIA front it should be noted that Yahoo have shared their current project on the topic with its developer community (Browser History Manager: http://developer.yahoo.com/yui/history/) based on the initial initiative by Brad Neuburg (Really Simple History: http://codinginparadise.org/projects/dhtml_history/).
However… browsing the RIA communities I found a general lack of seamless integration to the serverside written in dotNET when the state has to be restored, either from history navigation or bookmarking. I decided to do this based on the AJAX.NET framework (http://ajax.asp.net/) and to extend the functionality of the UpdatePanel to register and restore states.
I have it up and running now on and it works eminently for the IExplorer and Firefox people, sad I am using the IFrame approach I still need to provide the workaround for Safari so that it will be suitable to send into production systems.
When I have completed this task I will post the system here…
