> > On Jun 6, 9:28 am, Chris Dunaway <dunaw@gmail.com> wrote:

> > > On Jun 6, 8:05 am, gregarican <greg.kuj@gmail.com> wrote:

> > > > There is a C# CTI app I'm working on using Visual Studio 2005 at
> > > > revision level 8.0.50727-7600. I need a couple of Windows Form Button
> > > > controls to emulate line buttons on a telephone. So I went to create a
> > > > class file for the user control to subclass this out. Something basic
> > > > for a start, just initializing things. When I drag this custom control
> > > > from the Toolbox to my form then Visual Studio just abruptly exits
> > > > without warning.

> > > > So I tried to create a custom button control as part of a custom
> > > > Control Library DLL file. When I add this reference to a new project
> > > > and then try to drag in the custom control the same thing happens.
> > > > Visual Studio just vanishes.

> > > > I have tried subclassing the Button class, the UserControl class, the
> > > > Control class, etc. All with the same result. I have tried each time
> > > > with just a new project with nothing else in it other than the default
> > > > elements. When I try this out on another PC using Visual C# 2005
> > > > Express it works fine and I can drop in the custom button control
> > > > without incident.

> > > > Has anyone else experienced something similar?

> > > When you say you want to emulate line buttons on a telephone, what do
> > > you mean?  Do you mean buttons that select the particular phone line
> > > to use?  Have you tried using a RadioButton with its appearance set to
> > > Button?

> > > I'm sorry I don't have a solution for your crashing VS problem.

> > > Chris- Hide quoted text -

> > >

> > There are several different states of a LineButton control that I
> > wanted to use. It is either ringing, idle, or holding a call. I
> > figured I could subclass a Button control and then add Property gets
> > and sets for these states. A RadioButton control wouldn't offer me the
> > same clean feature set since I want to conditionally change the
> > BackColor, Image, and other things as well.

> > I will read up some more on the recommended steps of subclassing an
> > existing Windows Form control and ensure I'm going through the steps
> > correctly as the other poster suggested. We'll see...

> Hi,

> What do you mean by subclassing? Inheritance?

> There shouldn't be a problem inheriting a windows forms control (that
> is inheritable).

> Moty- Hide quoted text -

>