The Gooddogs Technology Project Template for DotNetNuke module development is now available in an early form for you to download and try out. This Visual Studio 2010 project template is pre-configured to allow you to build DotNetNuke modules using the latest technologies like Entity Framework, WCF Data Serviced, popular open source frameworks like Knockout,js, AutoMapper and the Blueprint CSS Framework
I still get lots of questions about using WCF services within a custom DotNetNuke module. This 8 part series will step you through the basics of WCF and how to develop a service as part of your custom module, including securing the service via the DotNetNuke authentication and membership role system. Here is an index with links to each of the 8 part series…. enjoy
There are times when you’d like to make a call to an external web service from your DotNetNuke module to process or get some data. It’s a pretty straightforward process to do so….
Version 3.5.3 of the Repository Module was submitted today to the DotNetNuke Release Tracker for testing/certification. This marks the first official release of the module in quite some time.
I addition to moving the source code to .Net 3.5 SP1 and Visual Studio 2010, 3.5.3 includes some major enhancements that I hope will make the module even more useful
If you are using Custom Attributes in your Repository template, you may be slightly frustrated that you do not have much control over the format of the Attributes when displayed. Well with a little template tweaking and a little jQuery magic, you can alter the format of your attribute values.
A development build of the Repository module 3.5.2 (Beta) has been released on Gooddogs.com. If no issues are found within a reasonable timeframe, this is the version that will be submitted to the DotNetNuke release tracker as an official module release. This will be the first official release of the module in quite a long time.
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.
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.
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.
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.