Download DOWNLOAD
Forums FORUMS
Blogs BLOGS
Forge FORGE
Help HELP
Marketplace MARKETPLACE
DotNetNuke Home
You are here >   Development > Forge > Component - Client API
Register  |  Login
Purchase

DotNetNuke® Project :: Client API

Introduction

The DotNetNuke Client API is composed of both server-side and client-side code that works together to enable a simple and reliable interface for the developer to provide a rich client-side experience.   The following diagram outlines the current consumers utilizing the DotNetNuke ClientAPI, along with the intended consumers of this functionality in the future.

ClientAPIOverview.jpg


Goals

  • Provide a consistent means of communicating information between the client-side script and server-side code.
  • Allow for functionality to easily be turned off and resort to the less-efficient way of responding to client-side events- post-backs.
  • Provide a uniform, cross-browser API that the developer can program against to provide a rich UI.  This includes but is not limited to accessing the Document Object Model (DOM), Dynamic HTML (DHTML), eXtensible Markup Language (XML).
  • Allow for the API to be enhanced and extended by both the DNN Core Team members and Third Party developers.
  • Provide ability to easily create Unit Tests to assist in development, testing, and troubleshooting of the API.  The tests should be easy to copy to any platform (windows, linux, Mac, etc.) and run, providing output that can then be sent to the developer for troubleshooting.

Client API Project Blog

Author: Jon Henning Created: Wednesday, August 24, 2005
My personal blog on DotNetNuke.

I mentioned in my last blog that I planned on publishing a video that would give an overview of how the Silverlight...

Read More »

I finally was able to get the multi-project template functionality working to enable the easy creation of a DotNetNuke Silverlight module.  The sample demonstrates how easy it is to have Silverlight interact with javascript, which in turn can talk directly to your server-side module code.  Unlike the other module templates, this one requires the creation two projects, one for your DNN module and one to host your Silverlight code.  Upon compilation, the Silverlight code gets zipped up into a file with a XAP extension. ...

Read More »

TemplateSkinMenu1I am pleased to announce the availability of a new DotNetNuke...

Read More »

Last post in this series we learned some basics of MSBuild, including the use of 3rd party tasks.  We saw that by simply importing some other targets file we can extend the functionality available to our scripting language.  The last two pieces to this puzzle happen to be solved by use of 3rd party plugins available on CodePlex:  Deployment and Automating our Build.

Deployment

...

Read More »

I've been working on a project for a client recently and was bitten by a bug recently.  It has to do with using the Microsoft AJAX Extensions, specifically, the JavascriptSerializer.  Our use of JSON is simply as an easy way to serialize our objects, whether it be to disk or across the wire.  What was happening is objects that contained dates would get their time shifted when they reached the other...

Read More »

Last post I went through the basics of what you do to set up your project on CodePlex along with how to hook into the source control.  This blog will explain what I did for my build script.  Specifically, how I handled versioning and packaging.

Most developers when confronted with a mundane task that is continually repeated will be compelled to automate it.  We are programmers after all, we enjoy making the computer making our lives easier.  One of these tasks is the creation of a software package to hand...

Read More »

I figured it may help some people to share my experience with getting my two projects (DotNetNuke ClientAPI and DotNetNuke WebControls) up on CodePlex and allowing them to be do automatic nightly builds.  The one thing I want to make clear before I start is that this is just one of many ways to do it. 

In order to successfully get nightly builds to work...

Read More »

Those of you who have been following my previous blog entries on Utilizing the Microsoft AJAX Framework and ClientAPI to Develop Rich Modules will be happy to learn that I have just posted the module templates on CodePlex. Unlike the previous version, this one utilizes the IWizard Template wizard framework...

Read More »

As mentioned in Part II of this series, this entry will focus on another advantage of writing rich client side objects representing our modules on the client side.  One very common use case that comes up again and again is how can one module talk to another on the same page.  For a long time DotNetNuke had this capability from the server side through something called...

Read More »

In part one of this series I mentioned that the Microsoft AJAX Framework along with the ClientAPI are different than a lot of other javascript frameworks since they allow for an end-to-end integration directly with .NET.  This entry will discuss how the this integration makes life easier for a DotNetNuke module developer by allowing communication to and from the server to be simple.  

The Microsoft AJAX Framework allows for server-side code to add a reference to the js file, initialize the client-side...

Read More »

Sponsors

DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation

Hosted by MaximumASP