Custom Controls Design Time Support Part 15: Debugging Design Time

Comments

7 responses to “Custom Controls Design Time Support Part 15: Debugging Design Time”

1. 

   Chris Pietschmann

   February 16, 2008

   This was an awesome series of articles! I can’t wait to see what you post next. Keep it up.

   Reply
2. 

   Dhananjaya

   March 13, 2008

   Hello Amr,

   Nice set of articles…. I would like to know how the Control Properties are mapped to an HTML attribute in case of Web controls and how i can add my own properties to HTML tags and map them on Designer properties window rather than to ASP.Net custom controls.

   Thanks again for gr8 series.

   Cheers
   DJ

   Reply
3. 

   Fatih ÖZTÜRK

   April 30, 2008

   Hi
   Thanks for this good articles. I want to build a custom controldesigner for my component (named oztBN) that derived from the bindingnavigator class. But the toolstripmenuitems (for example mymovefirstbutton) that I created does not be serialized in the form’s designer code. So when I close the form and open it again bindingnavigator.items collection is cleared. My code is in a Method of myBindingNavigatorActionList class.

   //this will use in DesignerActionMethodItem("CreateStandartButtons",….
   public void CreateStandartButtons()
   {
   ToolStripButton abc = new ToolStripButton("mymovefirstbutton");
   this.oztBN.Items.Add(abc);
   }

   I need your help urgently. thanks! Microsoft can do so I can do it 🙂

   Reply
4. 

   Asif Ashraf

   July 8, 2008

   hi, Amr! these are Gr8 articles. i loved to read them. i kept opening MSDN side by side where i thought i were not getting your points. anyhow its been one whole day since im constantly reading your stuff. this series is gr8 for component designers. anyhow many questions are still in my mind but you have solved all the problems i was having in my own component.

   Thanks
   Asif Ashraf
   MCAD.NET, MCP

   Reply
5. 

   Suresh

   August 11, 2008

   cool! Thanks

   Reply
6. 

   Doug Simpson

   September 8, 2008

   This method doesn’t seem to work with debugging custom TypeConverters. I read all over the Internet for various solutions… nothing’s working for me. I have Visual Studio 2005 SP1, tried Tools > Options > Debugging > "Enable Just My Code" (on and off), deleted .pdb files, set revision to "*" to ensure I’m not using a cached copy of the DLL, tried with Windows Forms and Console test applications, and various other permutations of building, debugging, etc. Still the symbols refuse to load. Any suggestions as to how I might debug a custom TypeConverter?

   Reply
7. 

   Doug Simpson

   September 8, 2008

   Your articles are, well… glorious to say the least. Thanks so much.

   Do you have any idea why I can’t seem to debug my custom TypeConverter in a new instance of Visual Studio? I’ve looked all over the Internet for a solution. I have VS 2005 SP1, tried Tools > Options > Debugging > General > Enable Just My Code (Managed only) (on and off), deleted and recompiled DLLs and pdb’s in obj and debug folders, used "*" for DLL revision (to ensure that a cached copy is not being used), compiled and debugged using various console and windows forms test applications, tried on XP 32-bit box (I’m using 64-bit Vista), tried the System.Diagnostics.Debugger.Break() method (which, by the way, works great for debugging custom installers), and various permutations of inheriting from TypeConverter/ExpandableObjectConverter, overriding few/many methods, implementing converter interfaces, etc.

   Still the symbols for debugging refuse to load… and yes, am running in DEBUG mode with the DEBUG compilation symbols checked.

   Any help would be greatly appreciated.

   Reply