Thanks for the information - I tried it - but I want to be able to set the
attributes from the designer.
Essentially, I'd the property should be browsable in descendent objects but
not overriden when placing a descendent object on a container object.
Currently the browsable attributes are sometimes auto-overriden and set to
null.
> You could try marking the property with [ReadOnly(true)] - as far as
> most bindings are concerned this will make it read-only, but you can
> still set the value via code.
Marc Gravell - 15 Mar 2008 10:35 GMT
OK - I'm struggling to understand what you are describing - is it
possible to post something that demonstrates this?
Marc
Marc Zwillinger - 15 Mar 2008 16:45 GMT
Hi and Thanks for looking.
The problem is periodic thus difficult to debug or reproduce.
Essentially I've created browsable attributes on an object. The idea is to
create descendant objects then set the attributes using the designer (not
code).
When the objects are ultimately placed in a container object (drag over from
the toolbox) these browsable attributes are sometimes overridden with null
(generated code).
This ends up causing problems down-stream...