Control persistence/ custom properties. Active-X functionality.

Question

Hi I am making some general .NET window controls. I wish to implement persistence so that it is used if the parent allows it so the control can be used both in my application and outside it (but when outside it may not support persistence for the control). In ActiveX this was solved by retrieving property bag from the parent. What options are there to implement such persistence using dotnet in general window controls? Are there ways of querying the parent for known property names? Can the control send/receive properties for persistent storage with the parent in other ways without stopping being a general dotnet control? Also wonder if my application can implement general persistence/serialization for third party controls somehow. I'm currently thinking of using attributes to mark some properties for serialization and then serialize the controls using reflection. Sounds a bit tedious when it's just one or two strings which shall be preserved by the server. Thank you for your help.

tormods · Answer

System API you mean? My problem is not to store information in registry or files. It is to store information that finds its way back to the correct instance of my control. I can create a proprietary querying interface in my application so that all instanciated user controls are queried for a particular interface and then transmit the information. In active-X however this container/control relationship was standardized using property bags. I could instantiate foreign active-X controls in my application and persistent storage of control configuration. Is there such a common technology thought used with .NET user controls? I spent most of yesterday reading MSDN and enjoy digging. However some words on what interface is both suited for this purpose and can be expected from foreign controls will be appreciated. It's not like I object to read or search MSDN but it helps knowing that what you look for actually exists.

Mykonine · Answer

First you should do some research in the MSDN articles; they often contain the answers you need in the API specifications.