Here are my links. If you produce your own dlls, my advice is not to bother
trying to convert them to MC++ as there is a lot more work to do.
1) Manually edit project files setting BasicRuntimeChecks="0"
http://www.groupsrv.com/dotnet/viewtopic.php?p=7922
2) Declare Empty Definitions for tree controls:
struct _IMAGELIST { };
struct _TREEITEM { };
http://www.winterdom.com/mcppfaq/archives/000262.html
3) Debugging
1. Download latest Windows XP SP2 symbols for system dlls from
http://www.microsoft.com/whdc/devtoo...symbolpkg.mspx
2. Put these in a folder
3. Link to these in the solution properties under Common Properties, Debug
Symbol Files.
Error: exceptions in mscorwks.dll, whenever a breakpoint is reached.
Link: search for “.net 1.1 service pack 1 debug symbols” at
http://communities2.microsoft.com/co...s/default.aspx
ps- expect debugging to be much slower in MC++, release builds seems OK
speed though.
"gowharjan" wrote:
Hi...
However you normally have a bit of manual work to do.
We had to work through several microsoft articles before suceeding.
Could u give some references to the microsoft articles u're talkin abt here.
I'm workin on movin an MFC application to managed C++.
Thanks.
"James" wrote:
In theory you can just turn on managed extension in the project.
However you normally have a bit of manual work to do.
We had to work through several microsoft articles before suceeding.
Just out of interest, what are you hoping to achieve under MC++? Are you
writing all new stuff from now on in c#?
"Bredal Jensen" wrote: