That's great .I finally seeked the solution,which is the same as the DNN_Module Development.

OK,Let's move on

Hi Jeffrey,

Although very close, and the advice is good, the statements are not exactly true. 

A Module Inherits from PortalModuleBase and a SkinObject inherits from SkinObjectBase.

You eluded to it, but a very important distinction is that a module needs to be injected into the page so that it gets a ModuleId, whereas a SkinObject is not dynamically injected into a page and does not have the ability to get a ModuleId assigned to it.

I used to make all my SkinObjects inherit from PortalModuleBase just to give them a couple extra properties, but in the latest releases it won't work because a ModuleId is expected for some of the newer features in the ClientAPI.

In order to get a Module to work like a SkinObject you will need to trick it by assigning it a ModuleID.  What ModuleID you assign it can have other ramifications, but unless you want to do something like save settings for your SkinObject it is best to just let it inherit from SkinObjectBase so you don't have to set worry about it.