Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / May 2004

Tip: Looking for answers? Try searching our database.

MT runtime library

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
songie D - 11 May 2004 14:11 GMT
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

Thanks.
David Lowndes - 11 May 2004 17:03 GMT
>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.

Dave
Jeff F - 11 May 2004 20:04 GMT
> >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


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.