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: JLT93 **
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: JLT93 **
I was looking in my debug folder, and I seen the Xceed.Wpf.Toolkit.dll file. I had a lightbulb shining above my head and now I know what the problem is. I have a copy of the .dll so it works fine, however the user that is having the crashing issue does not have the .dll file. That would be exactly why there is a problem.
Is there a way to compile the app without having the .dll show up in the output folder?