It turns out that this behaviour was down to strong naming and its set up ....
When the managed dll had the following conditions
1) built as strong named
2) included in the GAC
3) copy local.Net IDE set as true
4) All the .Net caches cleaned out
The Result was :
1st Run : No Problem
Close the debugger
Open the debugger
Run : Thec# application calls into the managed code fine but when the
managed code calls the unmanaged code it bombs out.
The above happens also if the strong named dll isn't included in the gac and
copy local.Net IDE set as true
The only time it does work is if the strong named dll is included in the gac
and copy local.Net IDE set as false
I can't find anything on the web to support this , Does anyone have an
explaination for this behavior ... pretty please ;-)
"HMANG" wrote:
I have a c# application that calls a mixed code dll which in turn calls an
unmanaged dll that has an inline template class constructor.
The c# application runs fine until I use it on IIS
The problem only occurs the first time you run it in a debugger.
When it tries to enter into the unmanaged C++ inline template class it fails
saying that it can't find the specific code ... if you look at the
disassembly you will see that this template class does a jmp to an invalid
address.
If you stop the debugger and restart it you will not see the problem.
Anyone got any ideas ????
