Friday, January 19, 2018   Login
You are here: Project » Blog  
Author: Michael Washington Created: 1/1/2007 12:48 PM
The IWeb Project

One more enhancement before the proposal to the DotNetNuke Core
By Michael Washington on 6/21/2007 4:20 AM
I have updated the roadmap so there is now only one item to be completed before the proposal to the DotNetNuke Core in October. We had hoped to have other items such as the authentication enhancements but we were not able to recruit enough people to work on these issues. If you are interested in helping out please see the contact page.

IWeb 02.30.00 Posted - C# version of IWeb client
By Michael Washington on 5/20/2007 8:57 AM

IWeb 02.30.00 has been posted. It contains a C# version of the IWeb connector client. We plan to release a C# version of the IWeb Core with the next major release hopefully in July. We will continue to maintain a VB and a C# version of IWeb

C# Conversion of IWeb Client provided by:
HyperLink HyperLink

Future IWeb secure communication enhancements
By Michael Washington on 5/20/2007 4:17 AM

Currently IWeb allows you to encrypt the password, but it can be intercepted by a packet sniffer and “replayed”. To prevent this we have discussed it among the team and come up with two possible solutions. We would like to implement both of them and give developers a choice.

1) The client makes a call to IWeb and IWeb returns the current server time in minutes.
2) The client uses the pre-determined Security Key to encrypt the time and passes that value back to the IWeb when making a request
3) IWeb will attempt to unencrypted the value using the current time (and try one minute before and one minute after to account for slight differences).
4) The client can continue to make requests as it will change the value passed as each minute passes

Another method:

1) Client encrypts the user name/password pair using a shared encryption key
2) Client sends (possi ...


IWeb 02.20.00 Released
By Michael Washington on 5/5/2007 6:05 AM

We just discovered a bug with IWeb 02.10.00. The secure AJAX method described here: created a random encrypted password that sometimes created a value that threw a JavaScript syntax error every 10-20 times it was called.



The Spirit of IWeb
By Michael Washington on 4/26/2007 2:21 AM

What I learned from the DAL Project proposal was that it is not necessarily important for the DotNetNuke Core to adopt the code from a proposal as it is to adopt the “spirit” of the proposal. In the case of the DAL proposal, none of the proposed code was used, however the final implementation (the


I think I got it!
By Michael Washington on 3/25/2007 12:13 PM

During my jog this morning I thought on the problem with IWeb that has been bugging me for months.

The problem is we need an easy way to create IWeb extensions. Currently you have to create a partial class and place it in the IWeb folder. I am sure many module developers would rather create methods in their own modules and have it somehow just work with IWeb.

My idea, is to have an interface that your class would implement. This interface is just a marker, because when the "Refresh Web Methods" link is clicked in the IWeb configuration, IWeb will look for any classes that implement this interface and make "wrapper methods" for all the methods in that class.

IWeb will actually create a physical file in the IWeb directory that will be compiled as a partial class into the IWeb web service. This way the methods will behave just like normal web servic ...


Creating Secure DotNetNuke ASP.NET AJAX Web Services
By Michael Washington on 3/25/2007 10:08 AM

I just added a tutorial for Creating Secure Web Services for use with ASP.NET AJAX and the DotNetNuke framework. When I finished the tutorial I noticed that there is a lot of code that you would need to be implemented over and over again. The next version of IWEB will address this.

Basically, we need IWeb Core shared/static methods that can be called to place the encryption key into the personalization settings, and IWeb Core methods to unencrypt the password and determine if it is still valid.

Of course any code using the current example will still work with the next version of IWeb.

What I am working on
By Michael Washington on 3/10/2007 9:56 AM

Well the latest IWEB Core seems to be very stable. I plan to have a little fun over the next 2 months and work on:

"client program and web methods that allow visitors to click a button on their web browser and automatically register themselves with a DotNetNuke site"

This will require me to create IWEB methods that register a user with the site and also work with CAPTCHA (displaying a image to prevent web bots from registering users) if it is enabled.

I really want to make a program that people can install in their web browser tool bar but the first release will probably be an .exe program that you will launch. You enter your information into the program only once and when ever you want to register with a DotNetNuke site (that has the web service installed), you just enter it's address in the program and click register.

As you can imagine it will be more pract ...


IWeb 02.00.00 Released
By Michael Washington on 2/17/2007 8:49 AM

We have just release IWeb 02.00.00

It is a major upgrade over the previous version. Changes in this release:

  • Authentication is now passed in the SOAP header so your method signature will only need to contain the parameters needed for the method
  • You can configure security for each method separately by method and by portal
    • The configuration page automatically looks for IWeb methods and adds or deletes them in the database.
    • It also looks in the attributes for each method to see if any grouping has been indicated and enters the grouping into the database (to be used later when the administration is enhanced)

**** IWeb 02.00.00 only works with DotNetNuke 4.4.0 or higher ****

C# version of IWeb
By Michael Washington on 2/16/2007 5:52 AM

The next version of IWeb was to include the ability to create IWeb extensions in VB or C# (yet there is still just one webservice.asmx entry point). The problem is that while it worked it required two DotNetNuke modules to be installed at the same time. This caused errors to throw on installation. Also, the uninstall of either module caused the portal to crash because one module would then not have the classes that it was looking for in the other module.

Due to this I decided that while it will be part of the final proposal to the Core, (because if it is part of the Core it wont have these problems) it is too unstable and would threaten the project to release it as an official release.

However you can download it here:


Home  |  Screen Shots  |  Example Code  |  Installing  |  Download  |  Project
Copyright 2006-2009 by   |  Privacy Statement  |  Terms Of Use