You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If a custom user control inherit a FontAwesome.Sharp control (e.g IconButton), it will not show in the toolbox
This only seems to happen once you build the package and add the controls to the toolbox via the DLL (or NuGet)
It also only seems to occur on .NET Framework. This does not occur on .NET Core
To Reproduce
Steps to reproduce the behavior:
Create new UserControl
Set the UserControl to inherit from IconButton
Build
Create new WinForms Project using .NET Framework 4.8
Add the just-build DLL to the toolbox
You will notice you cannot find the controls
Expected behavior
All controls inherited from FontAwesome.Sharp should show in the toolbox
Screenshots
Here are all the Controls in the project, of which the following inherit from FontAwesome.Sharp controls:
PxButton
PxMenuButton
PxMenuIcon
Here you can see these controls will not get populated in the toolbox for some reason
Desktop (please complete the following information):
OS: Windows 11
Browser Vivaldi
Version 4.3
The text was updated successfully, but these errors were encountered:
Describe the bug
If a custom user control inherit a FontAwesome.Sharp control (e.g
IconButton
), it will not show in the toolboxThis only seems to happen once you build the package and add the controls to the toolbox via the DLL (or NuGet)
It also only seems to occur on .NET Framework. This does not occur on .NET Core
To Reproduce
Steps to reproduce the behavior:
IconButton
Expected behavior
All controls inherited from FontAwesome.Sharp should show in the toolbox
Screenshots
Here are all the Controls in the project, of which the following inherit from FontAwesome.Sharp controls:
Here you can see these controls will not get populated in the toolbox for some reason
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: