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 ;-)
> 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.
[quoted text clipped - 9 lines]
> If you stop the debugger and restart it you will not see the problem.
> Anyone got any ideas ????