There is a managed c++ project, which is used to wrapper one Native c++ project. And then I will use it in ASP.Net.
When I call the method of one ref class of ÃÂ this managed C++ project, I will get the followed log in call stack.
ÃÂ msvcm90d.dll!<CrtImplementationDetails>::GetDefaultDomain() Line 390 + 0x8 bytesÃÂ C++
ÃÂ ÃÂ msvcm90d.dll!<CrtImplementationDetails>::DoCallBackInDefaultDomain(int* function = 0x10F92EA0, bool cookie = false) Line 442 + 0x6 bytesÃÂ C++
ÃÂ ÃÂ msvcm90d.dll!<CrtImplementationDetails>::DefaultDomain::Initialize() Line 284ÃÂ C++
ÃÂ ÃÂ msvcm90d.dll!<CrtImplementationDetails>::LanguageSupport::InitializeDefaultAppDomain() Line 519ÃÂ C++
And when call "MANAGED_ASSERT(pDomain->IsDefaultAppDomain(), "Expecting default appdomain")", I will get one error:
"An exception of type 'System.Runtime.Serialization.SerializationException' occurred in mscorlib.dll but was not handled in user code"
I try to research something for this kind of issue, and find there are some thoughts that this issue is caused by the difference ofÃÂ AppDomain used by ASP and the native dll--Asp.net runs on non-default Appdomain, but the native dll runs on defautl Appdomain
In order to verify it, I create a little example to test, and at an AppDomain check co
View Complete Post