Below you will find pages that utilize the taxonomy term “DotNetNuke”
This tutorial will walk you through the creation of a basic Windows Forms application to test remote authentication and authorization when communicating with a DNN CMS web portal using its web services framework / Web API. This is for development and educational purposes only running locally. You will at least want to make sure that you have SSL enabled for your DNN Web Services in a real world scenario.
This tutorial will guide you through the steps necessary to add a session timeout timer and alert dialog within a DotNetNuke (DNN) Module using AngularJS. Key concepts: Using DNN server objects to create AngularJS client-side objects; Using DNN jQuery and jQuery UI registration; Using DNN Client Resource Management; Using DNN Form Patterns Requirements: DotNetNuke 7; AngularJS; An understanding of how to develop and install DotNetNuke modules.
When building the DotNetNuke Web Services API controllers, I want to use this REST convention for the endpoints to access a resource such as the Chinook database. Note: My DotNetNuke website is running under IIS 7.5 with “dnn7” as the host name binding. Only the request method, url, protocol, content-type and content-body are included in request examples below. Return all Tracks: GET http://dnn7/DesktopModules/Services/API/Tracks HTTP/1.1 Return a Track where ID = 1:
I wanted to stick with the environment setup I have been using which is a host name of dnn7 or dnndev. Working in IIS and modifying my host file is not an issue for me. If you are looking for a way to create a new module directly within the DotNetNuke CMS environment, you could give this extension a try: DNN Module Creator. Download Source Code for Christoc’s DotNetNuke Module Development Template at http://christoctemplate.
A few days ago I installed DotNetNuke (DNN) 7.0.0 to mainly test the new version of it’s Services Framework that is based on the Web API stack. Installation You can download the DotNetNuke 7 Community Edition installation archive here. Unblock the archive and extract it to a new directory under your IIS inetpub folder. For example, c:\inetpub\dnn7. icacls c:\inetpub\dnn7 /t /Grant NetworkService:F OPEN Internet Information Services Manager and create a new IIS application that is rooted at the DNN path.
Task 1, create a jQuery UI dialog to confirm a postback action invoked by a ASP.NET button control. In your module’s ascx file, add a button control and a div to contain you dialog. <asp:Button ID="btnDelete" runat="server" AutoPostBack="false" ButtonType="LinkButton" CssClass="main_button" OnClick="btnDelete_Click" Text="Delete" UseSubmitBehavior="false"> </asp:Button> <div id="dlgDeleteConfirm" title="Confirm"> <div class="confirmDialog">Are you sure you want to delete this?</div> </div> In you ascx code behind, create a method to create a client script block, you call can call on page load.
During module development, to see all of the js and css files in firebug or your favorite client debugging tool of choice, turn off the file combination provider. In this section at or near the bottom of your web.config, set the provider enableCompositeFiles attributes from true to false as shown in the example below. <clientDependency version="2" fileDependencyExtensions=".js,.css"> <fileRegistration defaultProvider="LoaderControlProvider"> <providers> <add name="DnnBodyProvider" type="DotNetNuke.Web.Client.Providers.DnnBodyProvider, DotNetNuke.Web.Client" enableCompositeFiles="false" /> <add name="DnnFormBottomProvider" type="DotNetNuke.
You could use a Multi-View inside of your Edit.ascx to create a dynamic way to toggle visible form/content objects and their code within a single Web User Control ascx and it’s ascx.cs code file. This is a popular approach when working inside the Edit control since dynamically loaded sub-controls will not have persisted postback data. You could also add a new parent ascx file all together: Add a New Web User Control References: Copy Edit.