Avoid Application.EnableVisualStyles()?

[Mike Hildner]

I recently read this

In version 1.1 of the .NET Framework, Microsoft provided a Application.EnableVisualStyles() method that supposedly replaced the need for the above changes (.manifest file). Unfortunately, using this approach causes many run time exceptions and should be avoided!

Anyone run into trouble using .EnableVisualStyles()?

[Aaron Young]

I've been using it for quite a while with no exceptions, the only thing I did run into was a glitch that caused all graphics loaded into an ImageList at design time to not display on controls at runtime. Although that was easily resolved by calling DoEvents after EnableVisualStyles call.

[Asgorath]

I had to disable it in my app because it was causing a vb6 activex control named Voloview that i use to display Autocad drawings, to cause an exception.

Regards
Jorge

[Mike Hildner]

Interesting. I haven't had problems myself, but yet to deploy a serious win form app. The quoted person above, I'm told, does his research thoroughly, just that I hadn't heard anything negative about it.

[VBnetFan]

here's a tip that worked for me.

Go to your forms Windows generated code region and open it.

Below Public Sub New(), MyBase.New() paste
Application.EnableVisualStyles()

and set Flat property of your controls to System.