New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Services Framework Makes Its Debut in CTP2 of DotNetNuke 6.2

On Friday, March 16th, we released an updated CTP version of the new DotNetNuke Services Framework. This is truly exciting!

For developers who are experienced with the DotNetNuke APIs, they may not care much. On the other hand, if they're wanting to expose module services externally in a standardized way, then the Service Framework and coming Service Layer API's will be a major boon. Indeed, we're taking that approach with some of our own modules in DotNetNuke v6.2, examples being messaging, the new journal, and notifications. 

Equally important is what the Service Framework portends beyond the aforementioned items. Today, we address AJAX-based module development. In future releases, we intend to make available various DotNetNuke administrative and management functions, leading to easier access to key platform functionality. It excites me to think what may be done with mobile devices, for example, in effectively administering, monitoring, and managing DotNetNuke deployments and web sites. Or, consider how conveniently third party services may integrate with DotNetNuke via Service Layer API's.

What was made available in CTP2 is the first step forward; it provides an idea of what's to come. Today's implementation is built on top of ASP.Net MVC 2 which provides a simple way of writing both RPC and RESTful web services. Ultimately, our service framework is not so much about the MVC pattern but about easily responding to the various HTTP verbs with some text in a desired format. It’s also worthwhile noting that our Service Framework implementation is closely related to Microsoft’s new WebAPI feature, now in beta test. (We are currently reviewing the beta code to see if it would be beneficial to move the Service Framework foundation from ASP.Net MVC2 to WebAPI.)

So what do we want today from the community? To achieve our vision we need help. We need the community to review specs and test the Service Framework. Tell us if we're on the right path or if you think we're off the mark. We need the Service Framework to be reliable and we want the Service Layer APIs to have a long, useful life. We need to know that the security and authentication model is sufficiently robust and flexible for module and generalized usage. 

For more details, please see Scott Schlesier's blog on how to use the Service Framework, how to produce an AJAX module, directionally where the Service Layer is headed and how to take that into account today.  

The Service Framework is a major step forward in the advancement of DotNetNuke technology!  Please help us to ensure it has a long, useful life. 


Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Daniels (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out