>In the file settings for one of the .cpp files in a Win32 unmanaged DLL project, the runtime library it is using by default is Multithreaded Debug. Is there any point in using multithreaded library if it isn't multithreaded DLL? Or does it need this to support multiple clients at once?
>There isn't any COM involved.
> >In the file settings for one of the .cpp files in a Win32 unmanaged DLL project, the runtime library it is using by default is Multithreaded Debug.
Is there any point in using multithreaded library if it isn't multithreaded
DLL? Or does it need this to support multiple clients at once?
> >There isn't any COM involved.
>
> If your application doesn't use multiple threads, there's no need for
> it to use the multi-threaded library. However, unless you have any
> strict performance requirements, you might as well stick with the
> multi-threaded library.
What if your DLL is ever going to be used by an MFC application via the
DLL's lib file?
Thanks,
Jeff F
songie D - 11 May 2004 22:11 GMT
It's never going to be used by anything other than the exported function.
And probably only ever by one app.
> > >In the file settings for one of the .cpp files in a Win32 unmanaged DLL
> project, the runtime library it is using by default is Multithreaded Debug.
[quoted text clipped - 13 lines]
>
> Jeff F
David Lowndes - 11 May 2004 23:42 GMT
>What if your DLL is ever going to be used by an MFC application via the
>DLL's lib file?
MFC apps have needed to use the MT library for some versions now, but
the basic rule of thumb is that if the DLL will be used in a MT
situation, then it's wise to use the MT run-time.
Dave

Signature
MVP VC++ FAQ: http://www.mvps.org/vcfaq