D
Donald Hess
Guest
We have an out of process COM Automation server that we use for debugging our code. When we debug the code, it registers itself into the registry. The automation server then finishes starting up with no errors and goes into "wait" state waiting for the app to call it.
We can see the Automation server load up CWinAppEx::InitInstance and dump the appropriate debug messages. However when we try to hook the process for debugging it's loading up the release version of the dll instead. The registry IS pointing to the proper location for the clsid\localserver32.
When I go to "Attach to Process" there's two copies of the COM Automation server in memory. However one is marked as "Managed (v2.0.50727), x86" This is really odd because it's pure C++.
We have no such issues under windows 7.
UPDATE: Kind of figured it out. To register dll's/exes we have to run Dev Studio with administrator privileges, while the local app hooks into it is non admin privilege. So they exist in two separate execution spaces.
Running the local app with admin privs gets the hook to happen. However I'm having directory errors now. At least I'm a step closer.
Is there a way to debug with non-admin rights even though visual studio is running in admin mode?
Continue reading...
We can see the Automation server load up CWinAppEx::InitInstance and dump the appropriate debug messages. However when we try to hook the process for debugging it's loading up the release version of the dll instead. The registry IS pointing to the proper location for the clsid\localserver32.
When I go to "Attach to Process" there's two copies of the COM Automation server in memory. However one is marked as "Managed (v2.0.50727), x86" This is really odd because it's pure C++.
We have no such issues under windows 7.
UPDATE: Kind of figured it out. To register dll's/exes we have to run Dev Studio with administrator privileges, while the local app hooks into it is non admin privilege. So they exist in two separate execution spaces.
Running the local app with admin privs gets the hook to happen. However I'm having directory errors now. At least I'm a step closer.
Is there a way to debug with non-admin rights even though visual studio is running in admin mode?
Continue reading...