Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So, there is a legacy code that has to be imported into .NET projects.
Which one do you preffer, and why:
or
There is third option of exporting the functions in the DLL, but let’s say that we want classes here.
Myself, I would rather chew my leg of then go with COM. There are numerous times when my setup & deployment project collects wrong version of COM .dll (debug instead of release) and smoke-testing EACH build is just bit of an overkill for me.
Once written and tested, managed c++ wrapper never broke. At least for me.