My setup: I have a C # application (.NET 3.5) in Visual Studio 2008. There is no chance to switch to WPF or in general :).
My application contains a custom control (a button class derived from Windows.Forms.Button) that acts as a replacement for Windows.Forms.TabControl. I can associate these buttons with each other, and each button can be associated with one control with which it deals (usually it is a kind of Windows.Forms.Panel). It looks something like this:
public class TabButton : System.Windows.Forms.Button {
Basically, itβs just a click on a button showing its associated control, and the controls attached to the buttons associated with them disappear - like TabControl, but the approach can be easily identified and I can place the buttons far from my content panels.
Problem: This works very well at runtime, but use at development time is probably odd: use the mouse to find the control that belongs to the group and run the <Send To Back> series until the visible control appears.
Question: Is there a way to tell the VS designer to evaluate button clicks during development, how does this happen with TabControl, so that I can switch to the tabs just by clicking on them, like at runtime?
I have been looking for quite some time. There are some articles in SO, but they seem to cover the addition of additional attributes to the property constructor.
source share