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

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:


IWeb 02.00.00 release candidate is now being tested
By Michael Washington on 2/11/2007 4:18 PM

We just released IWeb release candidate 02.00.00 to the development team. We are still on track for a major IWeb release sometime in March.

The major changes in this version are:



Sneak Peek at the next IWeb Admin
By Michael Washington on 2/8/2007 10:37 PM

Here is a sneak Peek at the next IWeb Admin screen. This is already coded for a March release. The 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.

Then it allows you to indicate the role that will have access to each method.

You will be able to use C# or VB for your IWeb methods
By Michael Washington on 2/8/2007 10:12 PM

I was finally able to create a method to allow you to code your IWeb extensions in VB or C# and still have a single point of entry (the webservice at: /DesktopModules/IWeb/webservice.asmx)

In the next version of IWeb there will be a directory that you will be able to add C# methods to and a directory tree that you will be able to add VB methods to.

This works because the C# class inherits from the VB class. The .asmx file is pointing to the C# class.


Deleting IWEB Methods and using C#
By Michael Washington on 1/28/2007 3:33 PM

There are advantages of using partial classes for IWEB

The benefits of using partial classes:

  • Single entry point allows people to automatically know what address to use to connect to web services
  • Web services methods behave normally and you can use tools like visual studio to consume the methods
  • No need for reflection when calling a web method
  • Partial classes automatically resolve any conflicts on compiling

However, there are disadvantages:

  1. There is no way to delete the web method once it is installed

IWEB Method Grouping
By Michael Washington on 1/27/2007 7:19 AM

With IWEB we realize that there will eventually be thousands of web methods. To administer security we will need to have a way to group and sort the multitude of methods.

Developers will be able to add an attribute to their methods like this:

<WebMethod(Description:=" Retrieves Portals on Server *DotNetNuke* |IWEB Core| #General# !Portal! ")> _

The key is:


The latest on IWEB Security
By Michael Washington on 1/25/2007 6:22 AM

The latest enhancements for the IWEB core will be focused on security. The expected release date is March.

  • Each method and each portal will have it's own security setting so you will be able to indicate which role has access by portal and by individual method in that portal.
  • Make a Host only security configuration where the Host has to indicate which Portals have access to the web method. Obviously for some web methods the host will NEVER allow a portal to have access (this would be VERY important). Host only would be the default setting for all web methods.
  • Make a admin security configuration that only allows the Admin to configure the web methods that they have been given permission to configure by the Host

Security setting needed for each web method
By Michael Washington on 1/7/2007 3:28 PM

I have gotten feedback from others using IWeb and I realize that I need to provide a security level setting  for each individual web method.

Right now you can set the "Security Group" for all the web methods....

What we need is a screen that shows all the web methods and allows you to set the security for each web method. This frees the programmer of the web method from having to do much (just insert objIWebAuthendication.ValidAndAuthorized() at the top of the web me ...


IWEB and Partial Classes
By Michael Washington on 1/7/2007 11:39 AM

IWEB uses partial classes to allow you to create additional web services methods without replacing or re-installing IWEB.

In the App_Code/IWeb/IWebMethods folder,

all the class files are partial classes of the DotNetNuke.Modules.IWeb.WebService class.

All the class files will be compiled into a single DotNetNuke.Modules.IWeb.WebService class.

The methods will then be available through the /DesktopModules/IWeb/webservice.asmx< ...


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