|
|
|
DNN Blog
Looking for a specific blog?
|
In this blog post I intend to explore the potential of DNN Social. This is an umbrella term for the bits and pieces in the framework that allow users to interact with each other reminiscent of Facebook....
|
|
As most of you are aware, DotNetNuke has rolled out with 5 extra languages over the past year: German, Spanish, French, Italian and Dutch. These translations are done by trusted partners under contract...
|
Hi there again. Today’s topic for some deep exploration is how to manage your module’s settings in code. As I stated in my previous posts (here and here), most examples of DotNetNuke module development out in the wild are fine for a first shot at a module, but won’t hack it when you begin to get serious with module development. And if you don’t believe me: come to a DNN event and ask any one of the more experienced DNN Store vendors. It’s not that the Hello World examples suck. It’s just not sustainable when you’re building your module for world domination.
|
In my previous post I offloaded some of my ideas about setting up one’s module development project. In this instalment...
|
|
For all the marketing hype positioning DotNetNuke as a world class CMS (Content Management System), to me it’ll always be the ultimate .net Web Application Framework (WAF?). DNN began as a web app framework...
|
Last Wednesday we had a Swiss DotNetNuke Usergroup get-together in Zurich around DNN 6. It’s not that we are somewhat slow in Switzerland (although...
|
|
This blogpost is about disk permissions and asp.net applications like DotNetNuke. Although there are probably many posts like this I write this because permissions, or more precisely the lack of them,...
|
|
Murphy’s law has it that real issues in DotNetNuke (core. modules, skins) don’t manifest themselves until you’ve rolled out in production. We can test all we want, but the fact of the matter is that this...
|
I’ve been playing around with the new DNN Service Framework a little since the CTP 1 came out. As a module developer this is a very interesting addition to the framework (and one I’ve been asking for, for a while). In fact, I think it is the most significant change in 6.2. But then, I’ve always been into DNN because of the power of the framework.
As so many new additions to the framework, this starts out as a request from the community that then gets specced, scoped and what have you. Then we see it appear in the CTP/Beta with a note “by the way, we added feature XYZ”. Great. How does it work? And a demo comes soon after to show how it should work. Now, explaining what a new button does in the UI is one thing. Explaining how a completely new “framework” addition does is quite another. As always we begin with a “Hello World” example (as in the linked post above). But as a professional module developer you very quickly have to move beyond that. And my first stop is always: security. How does this feature open up the possibility to provide controlled access to my module’s resources? So in this post I want to move beyond the hello word example.
Goal I’d like to build a RESTful service that allows you to retrieve the contents of Text/Html modules throughout the site. This means accessing contents as it were a tree of tabs (pages) and then modules. So “GET …/23/345” will get the module’s contents for module 345 on tab 23. If I omit the module id I should be returned a list of Text/Html modules (i.e. a list of subnodes). So “GET …/23” should get a list of Text/Html modules on tab 23. Finally if I omit the tab ID I’d like to see a list of tabs. So the base “GET” to my service should get a list of tabs. Now I’d also like this to be fully protected. So I don’t see tabs I’m not entitled to see, nor modules I’m not entitled to see.
Step 1: Create controller and first route The first step is to open our project (in this case the Html module) and add a service controller which will do the magic. The snippet below I’ve added as “ServiceController.cs” to the Html module project.
using System;...
|
To our second installment on this two part series on handlers and modules in ASP.NET web applications, their significance and...
|
|
|
|
|