What do I need to do to have a wpf custom control load itself into the visual studio toolbox
-
I have created a WPF Custom Control (NOT a user control). I would now like to properly install this control into end users machines such that when they select a wpf project in visual studio it is automatically loaded. I have searched high and low through Code Project, Stack Overflow and of course google, but nowhere can I find anything that explains simply what (if any ) attributes I might need to add to this custom control and what I may need to set in the registry in order to achieve this result. Most articles and tutotials now seem to suggest going down the visx route and using the WPF Toolbox control template as the base for ones control, but that is based on User Control and by doing that I'd lose the additional benefits I've gained from creating a custom control from scratch (although I do like the idea of using a visx, but cannot see how to add an already complete custom control to one and achieve the result I'm after). So has anyone here faced this issue and can tell me what it is that I need to do with a finished wpf custom control in order to get it successfully installed into an end users machine. Ideally I would like to target visual studio 2010 upwards, but fot the time being I'd be happy just figuring out where to start.
-
I have created a WPF Custom Control (NOT a user control). I would now like to properly install this control into end users machines such that when they select a wpf project in visual studio it is automatically loaded. I have searched high and low through Code Project, Stack Overflow and of course google, but nowhere can I find anything that explains simply what (if any ) attributes I might need to add to this custom control and what I may need to set in the registry in order to achieve this result. Most articles and tutotials now seem to suggest going down the visx route and using the WPF Toolbox control template as the base for ones control, but that is based on User Control and by doing that I'd lose the additional benefits I've gained from creating a custom control from scratch (although I do like the idea of using a visx, but cannot see how to add an already complete custom control to one and achieve the result I'm after). So has anyone here faced this issue and can tell me what it is that I need to do with a finished wpf custom control in order to get it successfully installed into an end users machine. Ideally I would like to target visual studio 2010 upwards, but fot the time being I'd be happy just figuring out where to start.