http://lab.msdn.microsoft.com/Produc...2-c2a2e862c4d7
http://lab.msdn.microsoft.com/Produc...0-34167ec9d78e
http://lab.msdn.microsoft.com/Produc...8-7a67e3f6a518

Thank you
Urs

* Urs Eichmann <(E-Mail Removed)> scripsit:
> http://lab.msdn.microsoft.com/Produc...8-7a67e3f6a518

Mhm... You can select all controls on the form and change the
'Modifiers' "property" for all the controls in a single step.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

Herfried K. Wagner [MVP] wrote:
> * Urs Eichmann <(E-Mail Removed)> scripsit:
>
>>http://lab.msdn.microsoft.com/Produc...8-7a67e3f6a518
>
>
> Mhm... You can select all controls on the form and change the
> 'Modifiers' "property" for all the controls in a single step.
>
Yes, I'm aware of this. But if I add a control later, I have to do it
again.... and for the next form again... Sooner or later I forget about
it - but the problem is not really me, but our youngster programmers who
get used to bad practices because they don't remember to change all
modifiers, and then, while in the try-and-error process of programming,
see that the controls show up in the intellisense of the form and use
them from outside the form. If we could just set up a in the VS options
"let those controls be private for now and always" we could make life
easier for them (and us).