More on SEHException

I blogged a couple weeks ago about a SEHException we were getting in our Public Sub Main due to Application.EnableVisualStyles. Basically the solution was to insert an Application.DoEvents after the EnableVisualStyles call. Well, that has been working until today (which happens to be the day I have to demo this to our owner). So I made EnableVisualStyles an option in the application. So now the code looks like this:

   If AppOptions.EnableVisualStyles = True Then
      Application.EnableVisualStyles()
   End If
   Application.DoEvents()
   Application.Run(New frmMain)
Catch exSEH As System.Runtime.InteropServices.SEHException
   AppOptions.EnableVisualStyles = False
   AppOptions.ToXML(OptionsXMLLocation)
   Application.DoEvents()
   MsgBox("Critical XP Styles Error" & Environment.NewLine & "Please reboot GPS Control Room", MsgBoxStyle.Critical)
   End

New on Geeks with Blogs

Because of AI, You Need a New Development Team

Your existing team is buried in the complexity of your existing product. AI rewards the team with a blank slate. Most companies don't have one.

The Offshore Problem That Starts With a "Yes"

The stories about offshore "not working" are rarely about skill. They are about an invisible communication gap, and it starts the moment someone says yes.

The Focus Five: Five Questions to Know If Your Team Is Actually Making Progress

Almost nobody trains you to be an engineering manager. You were good at writing code, so you got handed more people and more meetings, and one day the job was leading a team instead of shipping fea…

Why Nobody Knows What Engineering Does

At VinSolutions, I was famous for one thing that had nothing to do with writing code. Every single time we shipped a release, I posted about it. On social media, to customers, inside the company, a…