You can use a global settting and use naming to find it (http://krompaco.nu/2010/07/retrieving-an-episerver-6-global-setting-value/) in your Dynamic Content-control and then apply the settings "by hand" in your Dynamic Content code.
Good input, but I should perhaps elaborate by saying that I use the settings to provide some different renderings of the custom property in edit mode - afaik, there isn't any way for the custom property to know what type of dynamic content it is being rendered on (in edit mode, that is)?
What I meant by naming is that you could have the dynamic content type.ToString() or something else matched to a specific global setting name.
Yeah, I understood that, but the code where I need to access the settings is run in the CreateEditControls-method of the custom property, and not in the dynamic content code ;-)
I see. If you need to stick with it that way I'm not sure on the event order but it might work to add something smart to HttpContext.Current.Items as early as you can in the DC and hopefully find it in the CreateEditControls-method.
Is this even possible? Suggested workarounds would be much appreciated...