System.Runtime.InteropServices.SEHException

[Dave Harris]

Using .NET 1.1 on XP, we are getting this exception under
certain circumstances. Can anybody describe in better
detail what this exception signifies and possibly give
any advice for tracking this down.

The most reproducable scenario happens when a modal
dialog (in managed C# code) is opened from another dialog
(also C#), closed, opened again, and then finally closed
a second time. It happens in all cases, and calling
empty dialog boxes with no more code than necessary
results in the same exception. The exception winds up
being caught in a C++ message loop. The application is
launched from unmanaged C++ code and makes calls to .NET
assemblies from places. Making the C++ code managed as
well does not make the exception go away. The problem
does not exist when using windows 2000. We also believe
that the problem might have started with the upgrade
to .NET 1.1, but we aren't sure.

Any help whatsoever would be appreciated at this point.

Thanks,

Dave.

[Jonas]

We are also experiencing the exact same problem.
Our app is running .Net Framework 1.1

We noticed this problem when we used
Application.EnableVisualStyles();

When we were using a .manifest it worked well. The problem with a
..manifest, it does not work well with dynamic properties.

If someone finds a solution for this, that would be awesome

Jonas

"Dave Harris" <DB******@xactware.comNOSPAM> wrote in message >news:<00****************************@phx.gbl>.. .
Using .NET 1.1 on XP, we are getting this exception under
certain circumstances. Can anybody describe in better
detail what this exception signifies and possibly give
any advice for tracking this down.

The most reproducable scenario happens when a modal
dialog (in managed C# code) is opened from another dialog
(also C#), closed, opened again, and then finally closed
a second time. It happens in all cases, and calling
empty dialog boxes with no more code than necessary
results in the same exception. The exception winds up
being caught in a C++ message loop. The application is
launched from unmanaged C++ code and makes calls to .NET
assemblies from places. Making the C++ code managed as
well does not make the exception go away. The problem
does not exist when using windows 2000. We also believe
that the problem might have started with the upgrade
to .NET 1.1, but we aren't sure.

Any help whatsoever would be appreciated at this point.

Thanks,

Dave.