Quickpart vs smartpart

Currently, I know that there are three user control wrappers available for MOSS:

Delegatecontrol ------ built-in in Moss
Quickpart ----------- developed by kaneboy, supports Custom Attributes
Smartpart ----------- developed by Jan tielens, does not support Custom Attributes

The following compares the installation, deployment, and performance differences between quickpart and smartpart for your convenience.

(I will describe the same part of the two wrappers in a uniform way, and the different parts will be particularly described, because the qucikpart deployment instructions kaneboy has done a lot of detail, and here I will mainly refer to smartpart as the main screenshot)

After the download, decompress the package to the moss server,Quickpart: Run installsolution. BAT; smartpart: Run addanddeploysolution. bat,

(This is the status when addanddeploysolution. bat is run for smartpart deployment)

After the deployment is complete, open the site in IE. Here is http: // oss. populate gallery is performed on smartpart. smartpart in site setting \ Web Part Gallery.

After the operation is complete, enter the site, open the Edit page mode, add a webpart, and find smartpart in the miscellaneous column,

Select and insert

Open the smartpart settings panel.

If an error occurs, the user control directory is not found in smartpart, this directory should be the usercontrols directory under the root directory of the site (quickpart is to put the user control in the wpresources directory under the root directory), if not, create one, put a user control for testing. I put a user control for iframewebpart that was written a few days ago, place the DLL corresponding to the control in the bin directory under the root directory of the site (this is the same as the deployment of quickpart)

Open the smartpart settings panel again and you will see that the iframewebpart user control has been found.

The following compares different settings of iframewebpart in smartpart and quickpart.

(Smartpart)

(Quickpart)

After the test, it is obvious that smartpart does not recognize the custom attributes of the user control as quickpart does, which will definitely cause inconvenience to development and use. In addition, quickpart supports the webpart connection, smartpart does not take this part into consideration. I personally think there is a big gap between smartpart and quickpart. We recommend using quickpart in practical applications.