Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDotNetNuke Module Development with JSON Output ...DotNetNuke Module Development with JSON Output ...
Previous
 
Next
New Post
3/13/2013 10:00 PM
 

Hello,

I am wondering what's the best way to incorporate json into a module; I have seen the RESTful JSON example but that seems to be a little dated considering that the example came out in 2010.

What I was hoping to find was a simple way to add a single Web User Control that could be used for JSON instead of being added to a page.  I am already familiar with the JavascriptSerializer object within the System.Web.Script.Serialization and I have a stand-alone project that works great with it.

How are others achieving DotNetNuke module intergration with JSON or using it?

Thanks.


Regards,
Christopher Koeber
 
New Post
3/14/2013 5:48 AM
 
A DNN site is an asp.net web site.

I don't see how a Usercontrol could work - it wants to be on a page.

Last time I just created a WCF service, and added the attribute AspNetCompatibilityRequirements(RequirementsMode=AspNetCompatibilityRequirementsMode.Required) so that I could use security and identity in the service.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
3/14/2013 1:27 PM
 
Richard Howells wrote:
A DNN site is an asp.net web site.

I don't see how a Usercontrol could work - it wants to be on a page.

Last time I just created a WCF service, and added the attribute AspNetCompatibilityRequirements(RequirementsMode=AspNetCompatibilityRequirementsMode.Required) so that I could use security and identity in the service.

 

Thanks, were all of the classes from DotNetNuke available to you even with creating the standard WCF service? I assume they should be because you are referencing the base dll...


Regards,
Christopher Koeber
 
New Post
3/14/2013 3:54 PM
 
If you don't need backward compatibility, I would suggest using the WebAPI functionality included in DNN 7.

It is fairly straight forward to use and well documented in the DNN wiki.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDotNetNuke Module Development with JSON Output ...DotNetNuke Module Development with JSON Output ...


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out