<p>If I have .Net Form with a component/object such as a textbox that I need to access from a parent or other form I obviously need to "upgrade" the modifier to this component to an Internal or Public level variable.</p>

<p>Now, if I were providing a public variable of an int or string type etc. in my form class I wouldn't think twice about using Getters and (maybe) Setters around this, even if they didn't do anything other than provide direct access to the variable.</p>

<p>However, the VS designer doesn't seem to implement such Getters/Setters for those public objects that are components on a form (and therefore does not comply with good programming practice).</p>

<p>So, the question is; In order to do the "right thing" should I wrap such VS designer components or objects in a Getter and/or Setter?</p>

I always do that, and if you ARE following an MVP design creating getter/setters for your view components would be a design requirement.
I do not understand what you mean by "does not comply with good programming practice". Microsoft violates
a lot
of good programming practices to make it easier to create stuff on Visual Studio (for the sake of rapid app development) and I do not see the lack of getters/setters for controls as evidence of violating any such best practices.