By Charles Thomas Blankenship - 9/13/2015
Just converted to 4.5.2 and received the following problem:
If MicroFour.StrataFrame.UI.Windows.Forms.ApplicationTheme.Theme <> System.Windows.Forms.ApplicationThemeName.NoTheme Then lblTitle.ForeColor = MicroFour.StrataFrame.UI.Windows.Forms.ApplicationTheme.ThemeProperties.BorderColor lblMessage.ForeColor = MicroFour.StrataFrame.UI.Windows.Forms.ApplicationTheme.ThemeProperties.BorderColor End If
It is located in the class FromLockPanel within the MicroFour StrataFrame Security solution. The error is 'ApplicationThemeName' is not a member of 'Forms' Evidently my Google foo is not what is should be as I searched rather ardently for a solution.
Finally, I simply commented it out as it appears to be an area of code my implementations rarely visit. Still, I'd like to know what is going on. |
By StrataFrame Team - 9/17/2015
CT, when we switched to 4.5.2, I had to change a bunch of places that said Windows.Forms.DialogResult.OK/Cancel to System.Windows.Forms.DialogResult.OK/Cancel. For some reason, maybe because of a new Windows.Forms namespace, you have to qualify Windows.Forms with System. I think your code used to say "MicroFour.StrataFrame.UI.Windows.Forms.ApplicationTheme.Theme <> Windows.Forms.ApplicationThemeName.NoTheme" and you might have used some sort of automated method to upgrade to 4.5.2. Maybe VS even did it for you, I don't know. That automated method probably saw Windows.Forms with nothing in front of it and added System to it. That enum is in the MicroFour.StrataFrame.UI.Windows.Forms namespace, not System.Windows.Forms. So, if you change the If test to "MicroFour.StrataFrame.UI.Windows.Forms.ApplicationTheme.Theme <> MicroFour.StrataFrame.UI.Windows.Forms.ApplicationThemeName.NoTheme", then you will be fixed.
|
By Charles Thomas Blankenship - 9/17/2015
Yawp ... that did it Ben ... thanks!
|
|