Gooddogs Development Blog
Author: Created: 2/13/2011 4:29 PM RssIcon
Code, Concepts and Ramblings about software development, programming and DotNetNuke module development.
By Steve Fabian on 2/13/2011 4:49 PM

Introduced in the 3.5.1 Beta build, dated 11-16-2010, item-level security has been introduced to the Repository module. When uploading an item to the module, you now have the option of designating one or more security roles that are required for someone to view/download the item. This new option allows the possibility of using a single Repository module instance to support different types of users.

By Steve Fabian on 2/13/2011 4:47 PM

WCF is a highly configurable technology/framework from Microsoft. You can configure various deployment and security scenarious by simply editing your web.config file without have to make any code changes to your service contract or code. That is incredibly powerful. It is also incredibly complex. Most of the examples you will find if you search the internet for “WCF Security” will talk about transport and message security, federation, WIF, ACS, etc…. and you will spend hours and hours reading whitepapers and blog posts about all of the options for implementing security for your WCF service.

By Steve Fabian on 2/13/2011 4:46 PM

In this section of the “DotNetNuke and WCF” series, we will use the WCF service methods we built in Part #6 to do some offline data management. We defined a couple of OperationContracts to enable offline moderation of Repository module uploads. Now, we’ll build a desktop application that will monitor our portal for new uploads requiring moderation and allow us to review/approve them from our application without having to browse to our website.

By Steve Fabian on 2/13/2011 4:45 PM

In this section of the “DotNetNuke and WCF” series, I will show how you can use everything you’ve learned to expose some Module “functionality”. So far, we’ve used WCF to expose some Data about our web site. But hopefully you can see that we are not limited to just exposing data, but that we can also expose module functionality using the same methods.

By Steve Fabian on 2/13/2011 4:44 PM

Ok, so all the groundwork is set. You should now understand how to add a WCF service to your DotNetNuke web site and how to expose both a SOAP-based and REST-based endpoint to your service. In this section, we’ll talk a little about DataContracts and show you how to expose some data about your DotNetNuke web site to external clients. We’ll add an OperationContract to expose some Metrics about our site, and write a Windows Forms application that will use the service and allow you to monitor your site’s activity without have to browse to your web site.

By Steve Fabian on 2/13/2011 4:42 PM

In Part#3, we created our WCF Service, defined a ServiceContract, wrote the Implementation code, and finally, a unit test verify that our new Service was working. Now in this section, we’ll take a look at the Configuration part of the service add a REST endpoint to our service which will allow us to use IE as our test client and make a RESTful call to our DNNService.

By Steve Fabian on 2/13/2011 4:40 PM

OK, so now let’s take a quick look at WCF and talk about the components of a WCF service.

By Steve Fabian on 2/13/2011 4:39 PM

Why use WCF with DotNetNuke

Why would I want to use WCF with DotNetNuke? Well, for the same reason you would have used Web Services in the past, to expose Data and/or Functionality to applications or web sites outside your application boundaries.

By Steve Fabian on 2/13/2011 4:31 PM
So, I just finished up my sessions here at OpenForce Vegas, and the feedback I received on it, plus my earlier session on using WCF with DotNetNuke was very encouraging! For those of you who were unable to attend either OpenForce Europe or OpenForce North America this year, I thought it would be nice to show you all some love :)
Privacy Statement | Terms Of Use | Copyright 2007-2009 by