Hello, this problem does not happen to me however I let someone else use my application for testing purposes and whenever he opens up a window containing the ColorPicker, the application would stop responding.
I have isolated the issue to be related to the ColorPicker only as when I commented out the XAML for it, it was no longer a problem.
I use the ColorPicker in a dialog window which is shown. Everything works fine without the ColorPicker.
System specs of user:
CPU - Intel Core i3-2310M @ 2.10GHz
RAM - 2.00 GB
Type - 64-bit
OS - Windows 7 SP1
Running .NET Framework 4.5
My application is compiled with .NET Framework 4.5 however I am using 4.5.1, unlikely to be the problem.
Comments: ** Comment from web user: BoucherS **
I have isolated the issue to be related to the ColorPicker only as when I commented out the XAML for it, it was no longer a problem.
I use the ColorPicker in a dialog window which is shown. Everything works fine without the ColorPicker.
System specs of user:
CPU - Intel Core i3-2310M @ 2.10GHz
RAM - 2.00 GB
Type - 64-bit
OS - Windows 7 SP1
Running .NET Framework 4.5
My application is compiled with .NET Framework 4.5 however I am using 4.5.1, unlikely to be the problem.
Comments: ** Comment from web user: BoucherS **
Hi,
Yes, that can explain the crash. As soon as the application tries to use the ColorPicker from Xceed.Wpf.Toolkit.dll and can't find it, it crashes.
Can you share your Xceed.Wpf.Toolkit.dll with this user ?
Normally, when compiling the Xceed.Wpf.Toolkit, the Xceed.Wpf.Toolkit.dll should be put in the output folder. If not, there is a problem when compiling, or the output folder is somewhere else.
In conclusion, the Xceed.Wpf.Toolkit.dll is necessary in order to use the ColorPicker.