Boy, this is an annoying error
I am consuming an older vb6 dll in my asp.net application
When I first started using the dll I had received this garbage error
Exception Details: System.Runtime.InteropServices.COMException: Some error in application progra
(brilliant error that one, and not documented at all
This was not caused by ASPNET permissions issues. The dll was originally registered to a directory where ASPNET had permissions to access it
I solved this error by rebuilding the dll into the /bin directory of my asp.net application
This has worked fine for two months now as I have been developing the new web application. The code consuming this dll has been stabalized and has not changed in over a month
Now, for no reason that I can figure out, I am receiving System.BadImageFormatException in mscorlib.dll. The exception is thrown after the successful build and before any of my app code is executed. If I Continue execution past the exception, the code works flawlessly, accessing the vb6 dll without any further issue
It seems to only occur in debug mode
It seems to be thrown after the first debug execution of changed code. A rerun after aborting execution, or a rerun after Continuing past the exception does not cause the exception to be thrown. This would point to some foozle magic happening during JIT, but my knowledge of that part of the process is scant
So, what are the causes of this arcane error (it also is not well documented (I know that documentation takes a long time to write, so I'm not complaining, just pointing out...))
Any ideas on what is happening here
Thanks for any help you can provide
-John
John Morales - 05 Mar 2004 13:56 GMT
c'mon there has to be some smart cominterop people out there. doesn't anybody have a clue as to why this could be happening?