NOTE: Updated 11/22/2009 - Added "Part 5: Exposing Data From Your DotNetNuke Web Site"

Over the coming weeks I will be posting the slides and code samples that I used in my OpenForce09 presentations. As sections are published, I will update this blog with hyperlinks to my blog on Gooddogs.com where this series is being published.

SESSION: DotNetNuke and WCF

Agenda/Intro: 
•Why use WCF with DotNetNuke?
•Quick Look at WCF
•Demos / code examples
    –Monitoring your web site
    –Offline management of your content
•Questions

So, I just finished up my Workflow session 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 :)   I am going to start a series of blog articles to present those sessions to all of you.  A kind of virtual conference session. Over the series, I will present the slides, source code and present the same guidance and demonstrations that I did at my sessions on how to use these technologies in your custom DotNetNuke modules.

The 3.01.15 release of the core Repository module has officially passed through the Release Tracker process and is available to download and install. 3.01.15 contains a security fix

After quite a LOT of time spent getting through the Release process, version 3.01.14 of the core Repository Module has officially been released.

Please see the post in the Announcements Forum for details on the release http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/112/threadid/241739/scope/posts/Default.aspx

This release fixes quite a few Gemini issues, and adds...

Read More »

Sometime, being on the bleeding edge is not always the frolicking good time it promises to be :)

So, I recently uploaded an early-early-early-pre-pre-ctp build of the Repository module version 4.0 to my personal web site, http://www.gooddogs.com/dotnetnuke for some testing and to give you all in the community a glance at the module in full working order, and as I expected, the first attempt was less than successful. My default repository application is...

Read More »

Previously, I blogged on the new template engine that will be included as part of version 04.00.00 of the Repository module. Now, I would like to talk about the new token architecture.

Background: In the current version of the Repository module and all previous versions, I designed the tokens to look and work like the DotNetNuke skinning tokens, square bracketed token names intermingled in with static text. Token settings were stored in matching .XML files establishing settings and values, then at runtime...

Read More »

As part of the total re-write of the Repository module, I am rewriting the template engine to be more powerful, more flexible and more useful than ever. A lot of the enhancement requests could be addressed through a more flexible and extensible template engine, so I have taken a more traditional approach to the engine as opposed to the current 'token replace' technology.

I have also refactored the template engine into a reusable public class in case you would like to take advantage of templating within...

Read More »

 Here is a short video demonstration of Repository Applications in action ... :)

One of the really cool things that you will be able to do with version 4.0 of the Repository module is add entire new functionality without ever laying eyes on the code. The 4.0 template engine supports the dynamic loading of custom controls which enables you to extend the module to your heart's content :)

Currently, if there is some missing functionality from the module, you would have to edit the module's source code itself, adding support for a brand new token, then rebuild the module and upgrade your...

Read More »

As you all read the various project forums and look forward to new releases of your favorite modules, you have no doubt seen references to a 'release process' or 'release tracker' .. and I'm sure you've all wondered .. 'what the *&%$ is that?

A little history: Back in July of 2006, after the modules had been split into their own projects, it became evident that we needed a formal release process in order to ensure high-quality releases of official DotNetNuke Projects. There are a lot of stakeholders in a DotNetNuke Project. There’s the Project Team, the Project Lead, the Project Chair ( a core team member who acts as mentor and liason between the project team and the core team ), and most importantly, the DotNetNuke Community as a whole. A documented, clearly defined release process was necessary to allow all of those stakeholders to not only understand the steps involved in releasing a Project, but be able to follow a release as it moves through the various stages of the process.

...

Read More »