BUG: designer force closure corrupts settings
Posted: Fri Jan 11, 2019 3:14 pm
Having encountered this in my own apps I bet it's the same issue here.
Micorosft in it's infinite wisdom decided to do updates when I left the designer open during the night.
When I tried to run the designer this morning it would run and appear in the taskbar but I could not get it to come forward.
It's as if the window was in an XY location that is invalid.
When I deleted Stimulsoft.Report.settings in AppData\Local\Stimulsoft this fixed the issue.
I saved copies of the bad config files if anyone would like to review them.
I saw nothing obvious in the file but I willing to bet that the forced closure caused a bad value to be written.
File not attached because there is some private information stored there in plain text.
Micorosft in it's infinite wisdom decided to do updates when I left the designer open during the night.
When I tried to run the designer this morning it would run and appear in the taskbar but I could not get it to come forward.
It's as if the window was in an XY location that is invalid.
When I deleted Stimulsoft.Report.settings in AppData\Local\Stimulsoft this fixed the issue.
I saved copies of the bad config files if anyone would like to review them.
I saw nothing obvious in the file but I willing to bet that the forced closure caused a bad value to be written.
File not attached because there is some private information stored there in plain text.