Just a quick note that will hopefully save a few of you early adopters some frustration. Between the initial unveiling of Services Framework back in March in CTP2, and the upcoming RTM there have been several tweaks made to the public API. The two biggest changes both affect route mapping.
IServiceRouteMapper.RegisterRoutes now takes an IMapRoute parameter. Simply change the type in your method declaration from ServicesRoutingManager to IMapRoute.
The next change is sneaky and has already tripped up several people at DNN Corp.. The name parameter has been removed from the MapRoute methods and all it’s overloads. In early versions name was the second parameter of all the MapRoute overloads. Because the various overloads all take a combination of string and object types, odds are your old code will compile without error. However your routes will no longer work because, for example, your old name parameter is now getting used as the url parameter. Generally deleting the name parameter from any calls to MapRoute will fix this problem.
I’m quite excited to see Services Framework is already getting some real traction in the community, and it’s not even officially released yet. If you are excited about Services Framework, it would be a good idea to make your way to Day of DotNetNuke in Charlotte on June 2, 2012. Both Brian Dukes and myself will be giving presentations with a major focus on Services Framework. And I know a few other presentations will include Services Framework to a lesser extent as well. Additionally many people who already have experience using Services Framework in production code as part of 6.2 and other DotNetNuke Corp. projects will be there including Joe Brinkman, Will Morgenweck, Charles Nurse, and Ian Robinson. There has never been so much Service Framework experience in one place before, I look forward to seeing you there.