Hi folks,
Has anyone encountered the wierd SEHException when using
Application.EnableVisualStyles();
Application.DoEvents();
at the start of an app and then using the PropertyGrid control?
I've Googled and found many threads making the link between these two, but no real solution.
If I have to use a manifest file instead, will that still cause the error?
Any additional info would be welcome.
Dr Herbie
-
Follow
Oops, something didn't work.
Sign In to be begin to follow this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.Getting "follow" information
Start following this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.Removing your "follow"
Setting up your "follow"
Did you know you can
sign up for email notifications?
-
Dr Herbie
Horses for courses
-
Sven Groot
Don't worry... I'm a doctor.
I'm not so sure about that particular error, but I've found EnableVisualStyles to be very buggy in general. I've had much more luck just using a manifest file.
-
You will probably have better luck using the manifest approach. There are a number of different issues that arise when using Application.EnableVisualStyles that often aren't seen when using the manifest file.
One other nice thing about the manifest approach is that if you have any future problems (and let's hope you don't) you can always just delete the manifest file and you wouldn't have to recompile your application. -
Where are you calling those functions? I've seen this problem go away when I call them in Main, just before Application.Run
-
harumscarum
out of memory
We just went through this yesterday. We were getting an error with EnableVisualStyles so we went with the manifest. So far we have not had any problems.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.