|
|
Hi,
Given that iWeb seems to have been, for all practical purposes, sunsetted ... what is your recommendation for building webservices into a DotNetNuke installation? In particular, DotNetNuke 6.x?
Thanks!
|
|
Coordinator
Jan 23 at 5:16 PM
Edited Jan 23 at 5:34 PM
|
1) Still use IWeb
2) Just look at the source code and see how IWeb connects.
On Mon, Jan 23, 2012 at 9:59 AM, jncraig <notifications@codeplex.com> wrote:
From: jncraig
Hi,
Given that iWeb seems to have been, for all practical purposes, sunsetted ... what is your recommendation for building webservices into a DotNetNuke installation? In particular, DotNetNuke 6.x?
Thanks!
|
|
|
|
Thanks.
|
|
|
|
I'm interested in adding webservices to a DotNetNuke site that returns JSON objects rather than XML. Do you have any thoughts on that? I suppose that I could modify iWeb to do that.
Would it be possible (easily) to add a single service that returns JSON without needing to perform surgery on the whole module?
|
|
Coordinator
Jan 23 at 7:39 PM
|
In my opinion you would need to start over to implement JSON. While it is possible to create JSON manually in code, you really want to use WCF. The WCF we have in IWeb WCF is a much older version that does not have JSON.
|
|