Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual C++ 2008 Express, encapsulation of discrete GUI elements into separate files
    primarykey
    data
    text
    <p>I would like to make my own compenents using, and for, VC9 &amp; Visual Studio 2008 Express. Currently my top level Form classes contain too much code for my liking, and I want to grow them.</p> <p>I can safely get as far as Project->Add...->Component_Class.</p> <p>Next I name and populate the component with, say, a text box, submit button, and panel to represent tabs for the different channels the comment can be submitted to (all, team, opponent) with a rich text box below which I will update depending on the tab selected.</p> <p>Only trouble is I am breaking the</p> <pre><code>#pragma region Windows Form Designer generated code /// &lt;summary&gt; /// Required method for Designer support - do not modify /// the contents of this method with the code editor. /// &lt;/summary&gt; </code></pre> <p>When I come to setting positions for my sub-components.</p> <p>That and I can't get this new component into my toolbox.</p> <p>Is it possible with VC++2008 Express?</p> <p>_<strong><em>EDIT</em>_</strong></p> <p>So I followed this, <a href="http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=151764&amp;SiteID=1" rel="nofollow">http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=151764&amp;SiteID=1</a> advice and got the component in my toolbox.</p> <p>Problem now is it is just 'unvisual' as the image lists sitting in their own bar off of the Form design area :(</p> <p>Will try to extend a more substantial class than</p> <blockquote> <p>System::ComponentModel::Component</p> </blockquote> <p>_<strong><em>EDIT</em>_</strong></p> <p>I've since answered this myself and tidied up the title and tags for future reference.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload