Hi Dess,

Yes, the custom_colors.cfg file works well at the default location. But we want it stored in the same folder as all our other application settings files. The default location is as you pointed out in the AppData/Local folder. But that doesn't always work for users on a locked down network. We need it in the AppData/Roaming folder in our application folder.

Using the CustomColorsConfigLocationNeeded event we can easily change that location when the ColorDialog closes because the event actually fires at that time. So the custom_colors.cfg is saved to our desired folder. So far so good.

Private Sub _myColorSelector_CustomColorsConfigLocationNeeded(sender As Object, args As CustomColorsEventArgs) Handles _myColorSelector.CustomColorsConfigLocationNeeded

        args.ConfigLocation = FileUtilities.AcquireApplicationDataFolder(False)
End Sub

However, that event does not fire when the ColorDialog is opened again. So the dialog does not know that there is a new location for the custom_colors.cfg file and continues to look in the default location.

So how do we get the ColorDialog to recognize and use the new location?