CodePudding user response:
http://bbs.csdn.net/topics/240047468CodePudding user response:
Try project attribute set to "in a Shared DLL using MFC", or a try/CLR or/MT to remove a
CodePudding user response:
Question 1: VS2010 c + + made a DLL library, and through the Labview calls, developed new applications, packaged in other Labview and not have been installed. Net platform of computer use, prompted "not find msvcr100D. DLL library,"Solution: system can't find msvcr100D. DLL library is a classic mistake, in this case is mainly dependent on the. Net platform, so appear such mistakes, the solution has three, the first method is to install. Net platform, 2.0 and above, the shortcomings of this method is to install the application must be installed first..net, brought trouble to install, the second method is to directly copy a msvcr100D. DLL to "c:/Windows/system32", the second method is relatively simple, but not to install a device and copy once, also is not the king, so there will be a third solution, let it completely out of the. Net platform, as work as a vc + + 6.0, actually very simple, only need to set up the compiler options, the first choice to Release, then choose the configuration properties in engineering properties - "routine -" the common language runtime support - "no common language runtime supports, and then select configuration properties -" c/c + + - & gt; Code generation - "the runtime -" multi-threaded (MT), then compile, if all goes well, it's OK, but most of the time there will be a "error D8016:"/MT "and"/CLR: pure "command line option is not compatible with the" wrong such as
Question 2: the error D8016: "/MT" and "/CLR" command line option is not compatible with
Solution, to build a project, start don't compile, set the compiler options in question 1 a third solution, compile again with respect to OK,
CodePudding user response: