This post is mostly for picking up by Google and information purposes.
The problem itself is solved for me.
Generally, debugging .Net COM dll should not pose any problems, but
you will be experiencing difficulties when debugging with VS2003 while
there is .Net 2.0 installed. .Net 2.0 execution engine (mscoree.dll)
will not allow VS2003 debbuger through, and problems which occur in
this scenario may range from IDE crash to "unable to attach to proccess"
error. The workaround is to force the framework use 1.xxx version
of the engine.
Here is how:
- include both projects in the solution
- create a config file with exactly the same name as your unmanaged
app executable name plus .config, e.g. MyMfcApp.exe.config and place it
along with the executable
- add the following lines to this config file:
<?xml version ="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
</startup>
</configuration>
(although MyMfcApp is not a .Net application, the framework will still
look for this file when it realizes that the application is going
to make a call to .Net dll)
- go to your unmanaged project properties and under Debugging change
Debugger Type to 'Mixed'
Now you should be able to put breakpoints in both managed and unmanaged code.
Here is the blog discussing the issue:
http://blogs.msdn.com/jmstall/archiv...with_2005.aspx
==============================================
debug between C++ C# MFC .Net COM dll interop
