I am creating a webparts solution for a customer. They will have the facility to create new webparts using web user controls. I want to be able to control the publishing of the new webpart so that they have to come to me before it can be published. They will have the source code on their server. I currently use WebPartsListUserControlPath to point to another web user control file that lists the available webparts. Is there a way that I can compile the list file so that they cannot add the new control to it. What I want is for the customer to ask me to add the new webpart and I would add it and recompile the file. Hope this makes sense. If there are any other alternatives I would be most grateful to hear them.

Many thanks

Hi,

Based on my understanding, you want to find a way to make your webparts commercialized and your customers have your source code of the program. If I have misunderstood you, please feel free to tell me, thanks.

As I know, even if we got a way to compile the list file, the file also could be decompile. So it might not be the most properly way.

I suggest that we can write a class or interface that each of our user controls could inherit from it.

Our class need have some special authentication mechanism.

For example, each derived user control has a unique 64-bit secuirty key property and when the customer first deploy it, it can connect to one WebService on our own website which can check the key and give a feedback. After the first check, we can unlock the user control on our customer's server.

Hope it's helpful for you.