| T O P I C R E V I E W |
| jmatthias |
Posted - Jul 21 2007 : 8:23:01 PM
I have been using an older version of VAX (1544) and I have been getting a System.ExecutionEngineException in VANetObj.dll
So I renewed by license so I could get the latest build in the hopes that the problem is fixed. Unfortunately, the problem seems possibly worse now. When I load my solution and VAX parses all the files I get multiple exceptions.
I have reproduced the exception on two seperate machines.
Any ideas? |
| 4 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jul 24 2007 : 1:49:26 PM
brandonh414 I have emailed you about this |
| brandonh414 |
Posted - Jul 24 2007 : 12:26:16 PM
This morning I just updated to the latest VAX build (1559) and am now getting this exception while I'm in the C# (actually I'm debugging mixed-mode code, some in C# and come in C++/MC++ simultaneously) debugger in VS7.1. The exception attempts to invoke the JIT debugger while I'm debugging my application. Appears the best way to duplicate it is to click in the editor window while debugging...but moving the cursor around (i.e., navigating between symbols, via Go To Definition, etc.) causes it as well.
I have an active support contract...if this is not the appropriate channel to get this fixed...please direct me to where I can get this issue addressed.
Thanks,
Brandon
|
| jmatthias |
Posted - Jul 23 2007 : 11:20:55 AM
Hi,
I'm using VS.NET 2003 (C# + C++). |
| feline |
Posted - Jul 23 2007 : 06:54:13 AM
Which IDE and programming language are you using?
We have one other customer who is experiencing the same exception, using C# in VS2003, but so far we don't know the cause of this problem.
I have emailed you about this. |
